Furthermore, the log4j2.xml file appears to be in good order, and the permissions for the log directory are such that the root user may read and write. Mango is set up to run as a service as per the instructions, which I believe results in it running as root.
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.
M
Posts made by Matthew
-
RE: ma.log not loggingposted in User help
-
RE: ma.log not loggingposted in User help
Thank you for your quick reply. The there were several instances of the word "log" in the console output, but none that seemed to indicate an error.
The full output is at:
https://pastebin.com/8H2wYpie -
ma.log not loggingposted in User help
I have a Mango installation that is not creating logfiles.
On a particular date, the database apparently became corrupted, according to ma.log, and logging ceased some time thereafter. Upon deleting the database and restoring from an earlier backup as per this thread, logging has not resumed, although everything else seems okay.
Does anyone have any suggestions for things I could check that could interfere with logging, or any information I could provide that might point to a possible cause?
The Mango version is v3.4.5 on a Raspberry Pi 3 running Raspbian 9.