Unable to connect to MangoES
-
I have a MangoES that was running very sluggish so I power cycled the device. Since I've power cycled it, the web interface cannot be displayed/connection reset. I can, however, get into the operating system normally.
I did notice before I reset it there were several thousand unacknowledged events. Could this be related?
Thank you for your help.
-
Hi Matt, If you have a lot of events it can cause the pages in Mango to be sluggish. Several thousand should not cause this though so you might have a lot more.
You look at the logs so you know for sure but a solution would be to start the H2 web console and then manually purge your events table. See here for more help: https://help.infiniteautomation.com/support/solutions/articles/14000022661-about-the-h2-database
You can run
select count(*) from events
to see how many events total you have.
You can then run
delete from events
to delete all the events
Try starting Mango again. Once it starts up look at the events to see what is generating so many events and resolve. You can also go to the system setting page under Purge settings click the Delete all events button.
Let me know if that helps.
-
Also, this is just a guess. You should really look at the log files and see if there are any errors during the startup sequence.
-
My MangoES was getting slow after big log files both in in the OS files /var/log and in Mango opt/mango/logs They where inGB size eventually the MangoES did not start up at all.
So many alerts and errors could create problems like this,
//Per -
Thank you for the responses. I finally got some time to work on it this morning. I edited the env.properties file to start the web interface for the database. After I restarted I couldn't get into the database, so I checked out the ma.log file. It looks unhappy. The log file is attached.
-
Hi Matt,
That looks like a corrupted database. You can find some steps to restore it here: http://help.infiniteautomation.com/support/solutions/articles/14000040833-how-to-restore-a-h2-database-backup
-
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.