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 Problem
-
Hi All,
I can not use MangoES Version 3.3.4. I went to see webmin found that CPU 100%. I'm not sure if this is a problem.I wanted to know what was going on and how to fix it to get back to normal.
Thank you.
-
hi JoHn-Beer,
CPU usage in the many hundreds usually means all the memory has been used and it's frantically trying to find some to free, but doesn't really say why. It could be there are some infinite loops in your configuration, such as two meta points updating one another's contexts or a single script in an infinite loop. Or, perhaps you have so many data sources / data points that it truly does exceed the machine. So,
To Resolve
- Start Mango in safe mode by creating a file at /opt/mango/SAFE so Mango will start without data sources enabled. If that doesn't work, check the size of your /opt/mango/databases/mah2.h2.db file. If it is >500MB it may be in your interest to move it, start on a clean database and restore a recent backup from /opt/mango/backup if one exists.
- Fix any infinite loops while things are disabled.
- Update Mango to the latest.
- It appears to have stopped at 88% so it's possibly loading swagger, which does take some extra memory. You could disable that in your /opt/mango/overrides/properties/env.properties file.
swagger.enabled=false - It appears the memory allocation is 1000m which you could consider raising to perhaps 1300m in the /opt/mango/bin/ext-enabled/memory-small.sh file. You would have to stop Mango and start it again (not restart it) for that change to apply.
For more information
- Are there any errors during startup in the log?
- What types are most of your data sources?
- How many points do you have?
-
@phildunlap MANGOES 16GB. How many datapoints are supported?
1.Are there any errors during startup in the log?
-I think there is no problem with booting because this system can work for 1-2 months. After about 1-2 months, this problem occurs.2.What types are most of your data sources?
- 50 data sources (Modbus tcp and meta data source)
3.How many points do you have?
- 2000 - 3000 datapoint
-
I would not expect 2000 - 3000 Modbus points polled perhaps every 5 seconds to overwhelm the ES from a data acquisition standpoint. Were you able to get it started and running again?
