Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

@zaaphod Mango has jetty embedded into it and will configure it when Mango starts. I'm not sure what you are implying here. If you start mango via it's startup script you should see Mango on port 8080 by default.

@ralf Thanks for your help

Enterprise has all the modules rather than the bare minimum. That would explain a lot.

@cwangv you can transfer the databases folder to the working instance.
As for the instance that is not working, @tpacker would need to comment on that.

@craigweb said in Mango crach after boot up:

OdroidXU4

Hi Swino

You are running in free mode so you will be limited to 300 data points and it will restart every 8 hours I think. You can put in a trail request by registering the GUID, I will grant you a 1-month trail.

Success!

Downloaded the abeip module (3.7.0) Placed the zip in the modules directory Did not delete the old abeip module folder Restarted Mango The data source config page is now loading without errors

Mango did an excellent job of reinstalling the module, Great work on that!

Thanks for your help!

@Shawn_H sorry for the delay, did you copy env.properties to the overrides directory? What is db.nosql.shardStreamType set to?

Hi @nathanRona sorry you are having such a torrid time getting Mango to upgrade. It seems that the issue is that you have started Mango directly using supervisorctl to launch the java process. Unfortunately this means that Mango cannot upgrade itself. It is the script that launches Mango (ma.sh -> ma-start.sh -> java) that does the unzipping of the new core upgrade file.

I recently created a new script (start-mango.sh) for starting Mango as the old ones were a bit fragile. This script is our new preferred way of launching Mango, we left the old ones so upgraded systems did not break.

I updated the help documentation here - https://help.infiniteautomation.com/linux-installation

What Linux distribution are you using? Does it use systemd?

Hello Terry,
Thank you for you response. This will let me continue with the upgrade. I am sure we can work with the unique email address point. It will just need to make sure I get a separate contact address for each user and explain to the customer it is for password recovery.

Thank you for your help and I hope you all had a happy Thanksgiving.

Cheers

Brian

The UI was being launched in IE, I knew it was something simple that I was missing. I installed the same downloads on a pi 3 b+ that I have and it ran without a hitch. Since windows 7 EOS is coming up I'm going to Change the OS on the desktop to Linux.

Thank you both for your help!

Certainly! Glad you got it figured out!

Glad you got it figured out!

@craigweb Hi!thank you very much ,this information was really helpful. Working now

Ah yes I forgot about that setting. Using the menu: Safari --> Preferences --> General then uncheck:

Open "safe" files after downloading

Craig's suggestion is the right course of action. While sending that email, please include details of things like,

Affected GUIDs, and your store.infiniteautomation.com account email if different from where you're sending from Are they MangoES devices? What kind of access do you have to the devices? Physical, SSH, Mango user, etc.

I'm not sure what the Persistent TCP publisher has to do with the error you are seeing. It seems to me that one of the system settings jwt.userAuth.publicKey or jwt.userAuth.privateKey were not imported correctly.

I checked the free bundle, it doesn't seem to have the NoSQL module so I'm not sure what happened there.

See ya in the emails!