@BG
Brian,

No worries at all, glad to help out. I look forward to seeing the solution.

@BG
Brian,

I've found that the documentation for v3 mentions Java 8, but has some very outdated links to recommendations for builds. For Mango versions 4 and 5, we recommend using Azul Zulu, so in this case I would recommend Azul Zulu JDK 8, which you can find here (I filled in the Java version, OS, and architecture for you): https://www.azul.com/downloads/?version=java-8-lts&os=rhel&architecture=x86-64-bit&package=jdk#zulu

I would recommend installing via RPM, instead of dropping a ZIP somewhere. Then, remove Java 21 to reduce confusion and the possibility that Mango still picks up 21.

Also, a heads up. We don't test with or support MariaDB, so I'm unsure if you could run into issues there. If it was working just fine for you before, then I'm sure it'll continue to work, but just letting you know.

Liv
Radix IoT

BG,

I've looked into the code on our end, and while I can't say for sure what is happening - I'm expecting that it may have something to do with your environment. We use some code to determine a unique machine identifier for licensing purposes, and the most likely issue seems like it's failing to either read or write to the HOME/.ma file.

What distribution and version of Linux were you using before? Also, how does Plesk play into this? Is MySQL hosted on your system, or is it a shared database cluster? When I used web hosts in the past with a control panel, sometimes they did some weird things with permissions. Or, it could potentially just be an incompatibility with Alma Linux 9. We have tested later versions with Alma, but I can't say I've tried Mango 3 with it. If I get a chance later, I'll try tossing Mango 3 onto a quick Alma Linux 9 container and seeing if I get an issue myself.

Liv
Radix IoT

@ryanlo In addition to what @MattFox is saying you should also see an Event / Alarm in the UI to correspond to the event being detected. The handler should be linked to that event and as Matt said, if you setup logging correctly you will also see it in the logs.

@ryanlo the other thing you could do, if you think its the SMS relay then add another reliable email address to the handler so it send the message to multiple addresses. If the SMS address is delayed but the other one (gmail or something) gets it almost immediately you will know its the relay and not Mango.

Hello,

Yes, the NoSQL license (General license not the Enterprise license) would be required to eliminate the restarts. In the ma.log file, when Mango starts, it mentions that it is running NoSQL in free mode and that it will restart in 8 hours. The documentation to convert an H2 database to MySQL is found here: Database Conversions. If you need further assistance, please let us know. Thanks!

Joe Miraglia
Service Application Engineer
Radix IoT

@tomatopi there is going to be 2 major parts to your solution:

A. Setting up the HTTP Retriever data source and points into a single request that gets the data into the desired points.

B. Retaining the history on the existing points so that new history is appended to it.

I'll focus on B here:

1. You could try modifying the points via the JSON import/export to move them onto a single data source.

• The general idea here is that if it is possible to reconfigure the points you would need to ensure that the seriesId in the database doesn't change. So use the XIDs to move the points and not create new ones.

2. You could create an entirely new set of points and migrate existing data into them.

• There are NoSQL tools in Mango for migrating data which you would need to explore.

3. You could create an entirely new set of points and then before you start them for the first time changing the series ID for them to point to the existing data.

• This would be done after you setup the new points by a Filestore Javascript.

All of this information hinges on the fact that you are on at least Mango 4. It can probably be done in Mango 3 but we didn't have the seriesId concept so the solution would be different. In Mango 3 the time series data is directly linked to the data point's id column in the database. In Mango 4 we added a column called seriesId to the dataPoints table to allows us to move the time series data between points if we needed to.

The caveat here is that you can only move data between points that have the same data type. For example Numeric time series can only be assigned to other Numeric points, not a Binary point.

@hayden_AUS we added permissions like this in Mango 4+, but there are only 2 levels for Event Handlers. View and Edit. If you wanted a user to be able to disable the event handler they would need to have the edit permission for that handler. Which would allow them to change any setting on it.

In Mango 3 Event Handlers are a superadmin thing only.

What @MattFox is suggesting is a common pattern that we use also, put your alarming logic inside Meta points and then set a basic event detector (State Detector) on the Meta point which can raise the event and handle it.

@tungthanh500 there are ways around this. In Mango 5 the default is to have HTTPS enabled on first start. This also enables HSTS which redirects from the HTTP port to HTTPS. You can change these settings by injecting mango properties into the container or modifying the mango.properties file you are loading.

Take a look at these properties:

# Note: Enabling SSL/TLS also turns on HSTS by default, see the ssl.hsts.enabled setting below
ssl.on=true
ssl.port=8443

...

# Configure HSTS (HTTP Strict Transport Security)
# Enabled by default when ssl.on=true
# Sets the Strict-Transport-Security header, web browsers will always connect using HTTPS when they
# see this header and they will cache the result for max-age seconds
ssl.hsts.enabled=true
ssl.hsts.maxAge=31536000
ssl.hsts.includeSubDomains=false

And how to inject them into the container as env variables: https://docs-v5.radixiot.com/configure-mango-properties

Just note that if you change the HSTS settings you will need to clear your browser cache since it will have cached the entry to always use HTTPS already.

We are looking for examples of how our Rate of Change event detector is being used. We have a list of features and changes for upcoming releases of Mango so I am investigating the use of this detector because it is on our list.

Please let us know the configuration you are using and why please.

Thanks!