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