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.
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.
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.
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.
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.