Where do i find the emoncms.log (it would be great if they was a button on the web interface that would zip up all of the log files and allow you to download them)
The interfaces that stopped Emonpi, emonth5, BMWi3, 2 x node-red (modbus) 1x node-red (weather).
Interfaces still working were openevse and IotaWatt
You have already shown us the emoncms.log, which is accessible/downloadable via the emoncms=>admin page, the emonhub.log is accessible and downloadable via the emoncms=>emonhub page (on an emonSD).
I assume you are running the latest emonSD on and emonPi? You say emoncms is the latest, have you updated via the âupdate emonpiâ button in emoncms=>admin?
At this point I have no idea how restarting emonHub could impact the â2 x node-red (modbus) 1x node-red (weather).â inputs directly, I assume they are posting direct to emoncms and not through emonHub, are they posting via MQTT or HTTP?
sudo systemctl status mqtt_input -n50 -l
â mqtt_input.service - Emoncms MQTT Input Script
Loaded: loaded (/etc/systemd/system/mqtt_input.service; enabled)
Active: active (running) since Tue 2017-12-19 21:31:16 GMT; 4 days ago
Docs: https://github.com/emoncms/emoncms/blob/master/docs/RaspberryPi/MQTT.md
Main PID: 3275 (php)
CGroup: /system.slice/mqtt_input.service
ââ3275 /usr/bin/php /var/www/emoncms/scripts/phpmqtt_input.php
Dec 24 01:44:26 emonpi mqtt_input[3275]: PHP Fatal error: Call to a member function fetch_object() on boolean in /var/www/emoncms/Modules/input/input_model.php on line 605
Dec 24 01:44:26 emonpi mqtt_input[3275]: Fatal error: Call to a member function fetch_object() on boolean in /var/www/emoncms/Modules/input/input_model.php on line 605
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I will leave it in a broken state for a few hours if you would like a remote session to have a look, just send me a PM
This release includes a significant fix to mqtt input script. The issue was the MYSQL connection was timing out after the mqtt input script had been working for a while. This has now been fixed.
It looks like the feedwriter scrip has stopped this can be restarted with
sudo service feedwriter restart
This question is why is stopped in the first place. This error is interesting, Iâve not seen this before:
What version emonSD are you running?
What are you running on the emonPi? What inputs are you posting? Anything non standard?
If you update to the latest version V9.8.28 (via emonPi update) you will be able to copy all the info admin info page. Please paste the full output here:
Thanks. From the logfile is seems that default.emonpi.settings.php and settings.php have been user modified. The change to default.emonpi.settings.php is causing emonPi update to not be able to pull in any new changes.
Ifâs possible to keep your custom settings in settings.php and just restore default.emonpi.settings.php to itâs default state. This file is is only used to store the default settings for reference, its not actually used by the application. You can reset default.emonpi.settings.php back to itâs default state by running
rpi-rw
cd /var/www/emoncms
git checkout default.emonpi.settings.php
git pull
The final git pull command should now pull in the latest changes and update you to 9.8.28. This wonât necessarily fix the issue you have reported but should enable us to debug on a common platform. Once updated to 9.8.28 please use the new copy to clipboard function to copy your Emoncms system info to clipboard and paste into the forum. It should look something like this:
Yes that sounds correct. It looks like itâs something to do with the MQTT /nodered service, as anything that is posting to that stops. But other services like openevse and iotawatt till post ok.
I am away at the moment so I am unable to post any log files
That is possible, I will review my logs again and see, but I didnât notice anything out of line the first run through. Just a reference to a broken pipe.
Iâve had a ton of issues with nodered right from the start. In fact this is my 3 try at keeping it going. The first two ran into all kinds of programming issues, and had to be wiped to clear all.
Itâs also possible that your issue is unrelated to mine, they just have similar outcomes.