[Implemented] release 3.10.1 *** Data input appears to have stopped
Posted: Wed 07 Apr 2021 5:54 pm
When communication between a weather station console and the original cumulus software stopped:
-> it showed a flashing red fault light on the main screen
-> the software halted further processing, for example no longer updating any files, no longer uploading to web server
-> optionally (by a setting), the software could be asked to close and restart, which generally cured the problem
MX works differently:
=> it logs *** Data input appears to have stopped to the current diagnostics logging file within MXdiags folder (if you bother to look at it)
=> the software continues to run
=> whilst today.ini no longer gets updated with new data, it and the other logging files are still showing as being accessed/modified, although nothing is changing
=> all processing of any files specified in extra web files continues, again although no data is changing
=> unless you look at that diagnostic file, or scroll down on the dashboard page of the admin interface, one could assume all is still working as normal
=> there is no option that closes MX, despite the fact it is obviously not doing anything useful
=>,there is no option to see if an automatic restart would clear the problem
This post is asking if MX can be changed to be more like the original Cumulus functionality.
My life is not about sitting still tied to watching a screen. I find it annoying, MX will read my weather station perfectly for days. From time to time, I can suddenly discover Cumulus has not received any information from my weather station for perhaps days, despite a casual inspection making me believe MX is still running properly.
A few facts about my implementation.... I am still using a Chas Olsen Fine Offset console/transmitter (with various non-standard old Maplin sensors), and I run MX on a RPi. I am wondering if it is possible that, at apparently random times, the RPi is somehow struggling to keep the USB link open. My RPi is left on, without me monitoring it.
I have also tried running as a service, and can confirm that no message is in service log nor (when not as a service) put out to the terminal session when this problem happens.
I have not investigated for any system messages.
EDITS: Minor changes for clarity to text and marking topic as implemented, despite some posts in this thread not being related to my post here
-> it showed a flashing red fault light on the main screen
-> the software halted further processing, for example no longer updating any files, no longer uploading to web server
-> optionally (by a setting), the software could be asked to close and restart, which generally cured the problem
MX works differently:
=> it logs *** Data input appears to have stopped to the current diagnostics logging file within MXdiags folder (if you bother to look at it)
=> the software continues to run
=> whilst today.ini no longer gets updated with new data, it and the other logging files are still showing as being accessed/modified, although nothing is changing
=> all processing of any files specified in extra web files continues, again although no data is changing
=> unless you look at that diagnostic file, or scroll down on the dashboard page of the admin interface, one could assume all is still working as normal
=> there is no option that closes MX, despite the fact it is obviously not doing anything useful
=>,there is no option to see if an automatic restart would clear the problem
This post is asking if MX can be changed to be more like the original Cumulus functionality.
My life is not about sitting still tied to watching a screen. I find it annoying, MX will read my weather station perfectly for days. From time to time, I can suddenly discover Cumulus has not received any information from my weather station for perhaps days, despite a casual inspection making me believe MX is still running properly.
A few facts about my implementation.... I am still using a Chas Olsen Fine Offset console/transmitter (with various non-standard old Maplin sensors), and I run MX on a RPi. I am wondering if it is possible that, at apparently random times, the RPi is somehow struggling to keep the USB link open. My RPi is left on, without me monitoring it.
I have also tried running as a service, and can confirm that no message is in service log nor (when not as a service) put out to the terminal session when this problem happens.
I have not investigated for any system messages.
EDITS: Minor changes for clarity to text and marking topic as implemented, despite some posts in this thread not being related to my post here