...
| Syslog | Description | Example |
|---|---|---|
| Thread stopped | Software failure or possible overload. (1) | thread=DiskLogger,state=8 |
| Thread safety system restart | Software failure or possible overload. (2) | no parameters |
| Unexpected disk removal | Error: only for Internal | |
| Battery level low at startup | Flat battery; battery is not charging. Let the logger charge the battery for a few hours. If the error still shows, send the logger back to MPEC for battery replacement. | 2.9V |
| Event receiver overflow | System is overloaded. (3) | |
| Could not delete folder | Happens during old file deletion. Usually indicates file system error. Logger restart may fix it, if it happens because of clashing file access. | \usbdisk\www\days\20140817 |
| Could not create file | Important for SA380: must have external disk installed. | |
| Modem command failed | Serial port error; modem error. It is not an error during modem baud-rate detection! Try to restart communication on the logger. | missing echo |
| M Tx File processing failed | Slow comms (file has been removed since), file system error. Logger had no connection to the server long enough to fill the message queue in the meantime. Check in the syslog if the GPRS communication was lost for a long time. | Could not build:type:EBE tick:395137049463 seqno:0 count:1 file:\usbdisk\www\Days\20120910\ebierr\2012-09-10_MMM TX_0_0.txt |
In case of system overload errors (1) (2) (3), it is a good idea to double-check the data collection settings. It is possible that the logger is collecting way too much data.
...