This is a repost from another thread as requested. The situation described below has occurred a couple of times now.
I have 9.31 installed via the raspi installation guide on Jessie Lite. This receives inputs from 3 sources;
Node 10: an attached rfm which is receiving data from my emonTX which is doing PV monitoring and diversion via emonhub once every 5 seconds.
Node 11: an esp based system that sends temperature readings via wifi monitoring my heat bank also via emonhub once every 15 seconds.
Data from these sources is sent to a local instance of emoncms and to emoncms.org.
Node 20: receives data from nodered - the outside temperature from wunderground using the emoncms node, so not using emonhub.This is updated every 15 minutes.
I can see that data from node 11 stopped being received by emoncms at 00:28:01 - this is the last datapoint on my dashboard for the temperatures.
When I look at the emonhub log it suddenly stops at 00:29:49 with a last packet received on node 10. I've copied the last entry below but the last receipt from node 11 was also acked fine by both the local emoncms and emoncms.org.
The input page on emoncms shows however that node 20 this is still being updated.
This is a disk based system and I can hear the disk ticking every 5 seconds or so which I always took to be the receipt of packets from the rfm module being saved. But of course it could be something else.
The rfm led is still flashing every 5 seconds or so, indicating it is receiving from the emonTX OK. And the esp system sending the temperatures from the heat bank via wifi is still functioning. It's using the socket interfacer on port 20100. (I will build some code into this to display an error code if this connection fails).
So it looks as though emonhub has stopped, or at least has stopped sending data to emoncms and also stopped logging. I'm not pointing fingers just drawing conclusions :-)
Although I've restarted the system now it would be great (Paul) if there were some series of commands I could use to ascertain what's going on, i.e. is emonhub still alive, etc.
Simon
Last log entry:
2016-04-27 00:29:49,617 DEBUG 10564 NEW FRAME : 1461713389.62 OK 10 98 0 0 0 0 0 0 0 69 95 137 0 0 0 0 0 0 0 0 0 (-42)
2016-04-27 00:29:49,621 DEBUG 10564 Timestamp : 1461713389.62
2016-04-27 00:29:49,623 DEBUG 10564 Node : 10
2016-04-27 00:29:49,624 DEBUG 10564 Values : [98, 0, 0, 0, 24389, 137, 0, 0, 0, 0]
2016-04-27 00:29:49,626 DEBUG 10564 RSSI : -42
2016-04-27 00:29:49,637 DEBUG 10564 Append to 'emonCMS' buffer => time: 1461713389.62, data: [10, 98, 0, 0, 0, 24389, 137, 0, 0, 0, 0, -42], ref: 10564
2016-04-27 00:29:49,710 DEBUG 10564 Append to 'emonCMSlocal' buffer => time: 1461713389.62, data: [10, 98, 0, 0, 0, 24389, 137, 0, 0, 0, 0, -42], ref: 10564
2016-04-27 00:29:49,740 INFO emonCMS sending: http://emoncms.org/input/bulk.json?apikey=E-M-O-N-C-M-S-A-P-I-K-E-Y&data=[[1461713389.62,10,98,0,0,0,24389,137,0,0,0,0,-42]]&sentat=1461713389
2016-04-27 00:29:49,813 INFO emonCMSlocal sending: http://localhost/emoncms/input/bulk.json?apikey=E-M-O-N-C-M-S-A-P-I-K-E-Y&data=[[1461713389.62,10,98,0,0,0,24389,137,0,0,0,0,-42]]&sentat=1461713389
2016-04-27 00:29:49,926 DEBUG emonCMSlocal acknowledged receipt with 'ok' from http://localhost/emoncms
2016-04-27 00:29:49,964 DEBUG emonCMS acknowledged receipt with 'ok' from http://emoncms.org
Re: Emonhub stopped??
If it happens again start with trying to establish if emonhub is dead or just quiet.
sudo service emonhub status
should tell you if there is an issue with the daemon. I have seen instances where emonhub has stopped logging errors because the other log files (emonhub is capped to 2x5mb files) growing so big they prevent further writes, so just to be sure run
df -h
This should confirm you still have lots of disc space and if you are using a read only filesystem the status of the /var/log partition.
If at this point the status says emonhub is running and there is still room (on the disk or ram partition depending on read-only or not) for logging, you could try opening a second ssh window and watch the emonhub.log in one
tail -f /var/log/emonhub/emonhub.log
whilst in the other ssh window edit the emonhub.conf, doesn't really matter what you change as you can put it back immediately, just go for something that creates a log entry, eg try changing the log level to INFO, save and then back to DEBUG and save again. both these actions should cause a log entry to be written in the other window.
You could also check the other log files for system or network issues and while you are there see if anything else is still logging, ie are there any resent timestamps when you run
ls -la /var/log
I take it that node-red is on this Pi too? is it using MQTT or HTTP to sent to emoncms ? is the mosquitto server ok?
sudo service mosquitto status
Some pointers for you to try isf it reoccurs, I'm sorry I cannot be more specific at this point but there isn't really any strong clues as to what might be happening.
Paul