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.
Mango Crashes
-
I have an installation on 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
This is the last entry that I see in the log file:
INFO 2016-02-24 00:05:00,004 (com.serotonin.m2m2.rt.maint.work.DatabaseBackupWorkItem.execute:94) - Starting database backup WorkItem.
INFO 2016-02-24 00:05:00,005 (com.serotonin.m2m2.rt.maint.work.DatabaseBackupWorkItem.createLogOutputStream:179) - Writing upgrade log to /opt/mango/logs/com.serotonin.m2m2.rt.maint.work.DatabaseBackupWorkItem.log
INFO 2016-02-24 00:05:02,631 (com.serotonin.m2m2.rt.maint.work.BackupWorkItem.execute:102) - Starting backup WorkItem.About 6 hours hereafter I noticed that it is down. How can I debug further what happened, before I start it again? I has run fine for the past 6 months.
-
It would be worth sending in your full ma.log file to support@infiniteautomation.com but a few other things is to check system messages. If you are low on Memory your system might kill the largest process using memory which could be Mango. You can use the dmesg command in your linux terminal to look for out of memory errors.
In Mango you can check your Internal Metrics Page to see what your internal memory usage looks like and share that here:
-
On first look it doesn't look like your logs have anything significant about this issue. I think looking at your CPU and memory usage on the server.
One thing I would highly recommend upgrading to the latest version. We just released version 2.7.4, there have been quite a few performance enhancements and bug fixes.
-
I looked at system log dmesg | tail
Nothing seems off
I looked at memory using free -m
1.2GB free.What is the proper ways to determine if Mango is running or not, other than accessing the web interface? I tried ps ax | grep ma
but I dont see anything running.
I looked at the current open ports with netstat -atn, but do not see webserver listening on port 80
-
You can do a top and look for a java process. The PID should match the the one in the MA_HOME/bin/ma.pid file.
You can check to see if that PID file is there. If Mango crashed that file could still be there even though Mango isn't running. If the file isn't there then it probably means something shut Mango down or killed it's process and the ma.pid file was removed.
