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.

I'll try to check tomorrow when I'm back there

any fanless hardware on the horizon?

Thanks, again, for the assistance Phil. I found that article and had been putting off trying that method. I will get on it right away. Have you had any success with using a netboot feature set. I may try to install one once I get it bootable again. Thank you

Have you tried clearing your browser's cache? There may be more to that log in your Mango/logs/ma.log file.

Thanks Phil

No problem and glad to hear you got it resolved!

Also, have you tried using the ES configuration module's network tools on the system settings page? If you can log into the Mango as admin, you can change the network settings if that module is installed.

Thanks, the change of the type of C worked.

Yes. Now it's OK! Your link is really valuable! Thanks again! Fabio

Hi Desmond, An UnknownHostException means it could not resolve the URL. It means either the DNS is not configured or not working properly. You can resolve the problem by ensuring your gateway is resolving URLs and that you have internet access from the computer running Mango (i.e. at the command line does ping www.google.com work?)

I'm not really sure what your first question is here? The backup zip files are only needed if you want to restore your database from a backup. The actual NoSQL database (Historical Data) is stored in the databases/mangoNoSQL/ folder. 331 seems pretty large for the H2 Database and I'm guessing you have a lot of events that could be purged still. Even with 113 data points if you are logging frequently it could amount to a lot of data. I would check your logging settings and make sure analog points that change a lot are set to something like a 1 minute average log and set points and binary data points for valves and pumps are on a log on change.

I believe for the openvpn all you will need to do is copy over the configuration files from /etc/openvpn/ The license file is named m2m2.license.xml Have you added other things into the opt directory? If not, I would advice only migrating /opt/mango to the new device from /opt

The MangoES uses a standard RS-485 driver so normal rules would apply. Because of this a star configuration is not recommended for a RS-485 network and proper termination / biasing should be used.

A quick suggestion is to provide the Power or Amperage(at the given voltages of 12 & 24) specs for the MangoES, since it doesn't come with one, I had an issue where I used an under-powered supply and was having problems booting it up, requiring me to send in a ticket. The problem was alleviated when I used an appropriately powerful supply.

We have 70 points in the list but only 18 are active. This is the env.properties 0_1475654024425_env.properties Following your suggestion I have updated Java without any problem and after rebooting MangoES I wait ... The next step it will be reinstall Mango. I keep you informed. Thanks.

Thanks again, everyone. I ended up having to restore the database from a backup then clean out the events from the H2 console. It's back up and running.

Hi Andrew, You should definitely be able to get into design mode as user "admin" (not just any user with admin privileges!). Unless you have changed the settings or deleted your userdb folder in Mango/web/modules/dglux/web/ One way to alleviate this would be to reinstall the DGLux module after deleting the existing module folder. I am guessing you do not have dashboards yet? Alternatively, you could... Move your Mango/web/modules/dglux directory up a level (so that it doesn't load), Download it again, Open up DGLux, Log in. Shut mango down. Displace the userdb directory in your original DGLux module, and move the userdb directory from the new DGLux directory to the old. Move the old DGLux directory back into the Mango/web/modules directory (overwriting the new one).

For a V3 MangoES, the RS485 and ttymUSB ports are symlinks based on the device port, so you can rely on that name being given to the device in a particular port. A full disk can definitely prevent many things from functioning... it doesn't even have enough memory for the TAB button to function on the command line!

If what Phillip says doesn't help you can try replacing all the files in the lib folder. It seems like you might have a corrupt library.