@tomatopi We are still working on documentation. I know it has been a very slow process but we are adding what we can to the doc sites (v4 and v5) as well as adding scripts to our script-examples in GitHub.

We have an internal ticket to review this issue. I will update with findings, no need to send an additional ticket. Thank you.

Hello @jcaballeroa, sorry for the delay on this topic but could you please open a support request at Radix IoT - Support? I would like to better assist on this topic but access to the files have expired. Also, have you tried to start a clean Mango v5 to see if you have any issue starting up Mango before upgrading?

@jcaballeroa You mentioned that you are testing Mango 5 in free mode. Could you please tell me how many data points you are using, and send the complete ma.log file again?

Additionally, assuming the server writes logs to /var/log/syslog, you might find more log entries related to Mango’s issues there. I often find the information I need in the syslog when Mango fails to start up correctly.

Thank you.

@jcaballeroa It appears the issue is related to this property:

pki.monitor.expiringSoonThreshold=25%

The problem may stem from unusual locale settings on your computer that do not properly recognize the percentage symbol (%). To address this, follow these steps in order:

Step 1: Modify the property

1. Edit the configuration file containing pki.monitor.expiringSoonThreshold=25%. Change this setting to the decimal format (0.25) instead of using a percentage, pki.monitor.expiringSoonThreshold=0.25.

2. Restart the Mango service to apply the new settings.

If the issue persists, proceed with Step 2:

Step 2: Check your locale settings

1. Ensure your system uses a standard locale, such as en_US, where the percentage symbol (%) is recognized correctly. Adjust your locale settings if necessary.

2. Restart the Mango service again to apply these changes.

Please implement these steps and let us know on the forum whether this resolves the issue. Your feedback is invaluable and can assist others experiencing similar issues.

Hello @jcaballeroa, I'm sorry to hear you're experiencing issues. To better understand the problem, I will need you to provide more details.

• Which Mango version are you using in v3, v3.7.12?
• Did this error start after upgrading to v5.2.1, or did you start with a clean install and your overrides added?
• Please share your SSL properties settings (those you feel comfortable sharing).
• Also, can you confirm that you are running Java 17 for the v5 Mango?

Sharing your ma.log file would greatly help in diagnosing the issue. Thank you.

BR,

Joe Miraglia
SAE/Radix IoT

Hello @vishalcapri,

Thanks for letting us know. We will have those updated.

Best regards,

Joe Miraglia
SAE
Radix IoT

Hello @hayden_AUS,

These are all default values, so it is intentional that they are all commented out. This allows users to see the current settings and make changes if necessary by removing the hashtag and adjusting the settings accordingly for their system.

Best regards,

Joe Miraglia
SAE Radix IoT

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

@ryanlo To answer your initial question, the default login is still admin : admin. The easiest way to do a reset would be to stop Mango, move the database (move it to root ~/) from the /opt/mango/databases/ directory (from directory use, mv mah2.200.* ~/ command), then restart Mango. Similar direction could be found on our document site, you will not need to do the restore since this is a new unit. Thank you!

@ryanlo This can happen if your browser has a cached version of the page. Try opening the page in incognito or private mode to see if that resolves the issue.

@tomatopi We are still working on documentation. I know it has been a very slow process but we are adding what we can to the doc sites (v4 and v5) as well as adding scripts to our script-examples in GitHub.