Services
emonhub Failed Failed
emoncms_mqtt Active Running
feedwriter Active Running - sleep 60s 0 feed points pending write
service-runner Activating Auto-restart
emonPiLCD Active Exited
redis-server Active Running
mosquitto Active Running Emoncms Version low-write 9.9.8
Modules Administration App v1.2.1 Backup v1.1.6 EmonHub Config v1.1.0 Dashboard v1.3.3 Device v1.2.1 EventProcesses Feed Graph v1.2.3 Input Postprocess v1.0.0 CoreProcess Schedule Network Setup v1.0.0 sync Time User Visualisation WiFi v1.3.1
Git URL:GitHub - emoncms/emoncms: Web-app for processing, logging and visualising energy, temperature and other environmental dataBranch: * stable Describe: 9.9.4-247-gd0db7a57 Server OS Linux 4.14.71-v7+
Host emonpi emonpi (192.168.1.71)
Date 2019-04-24 21:06:20 UTC
Uptime 17:06:20 up 6:27, 1 user, load average: 0.00, 0.01, 0.00 HTTP Server Apache/2.4.25 (Raspbian) HTTP/1.1 CGI/1.1 80 MySQL Version 5.5.5-10.1.23-MariaDB-9+deb9u1
Host 127.0.0.1 (127.0.0.1)
Date 2019-04-24 21:06:19 (UTC 00:00)
Stats Uptime: 24546 Threads: 3 Questions: 67546 Slow queries: 0 Opens: 23 Flush tables: 1 Open tables: 17 Queries per second avg: 2.751 Redis Version 3.2.6
Host localhost:6379 (127.0.0.1)
Size 145 keys (729.26K)
Uptime 0 days MQTT Server Version Mosquitto 1.4.10
Host localhost:1883 (127.0.0.1) Pi Model Raspberry Pi 3 Model B+ Rev 1.3 - 1 GB (Sony UK)
SoC Broadcom BCM2835
Serial num. 92A84C41
Temperature CPU: 44.01°C - GPU: 44.0’C
Release emonSD-30Oct18 Memory RAM Used: 13.71%
It has zero uptime and the versions are the latest, could it be this was triggered by an update?
The faults relate to a segmentation error, Is the log partition full?
df -h
Is there a emonhub.log?
ls -la /var/log/emonhub
in fact lets see what is happening with the logs in general
ls -la /var/log
Ahhh, ok that would most likely (not-confirmed) be the latest revisions anyway, so maybe not updated?
Not seen this error before, if this is a stock set up and the log partition isn’t maxing out (or even if it is for that matter) I would look at the recent changes to emonhub systemd and logging first.
My EmonPi stopped reporting readings a couple of days ago (the 27th or 28th April)…but I only noticed yesterday. It had been running perfectly for some weeks.I restarted my EmonPi, tried updating all the software…but to no avail, - I just can’t get readings from the EmonPi. The error that’s reported is the same as @mickeymouse690 - EmonHub fails to start
-- Logs begin at Thu 2016-11-03 17:16:43 UTC, end at Thu 2019-05-02 08:28:05 UTC. -- May 01 21:41:32 emonpi systemd[1]: emonhub.service: Service hold-off time over, scheduling restart.
May 01 21:41:32 emonpi systemd[1]: Stopped emonHub service description.
May 01 21:41:32 emonpi systemd[1]: Started emonHub service description.
May 01 21:41:32 emonpi systemd[1]: emonhub.service: Main process exited, code=killed, status=11/SEGV May 01 21:41:32 emonpi systemd[1]: emonhub.service: Unit entered failed state.
May 01 21:41:32 emonpi systemd[1]: emonhub.service: Failed with result 'signal'.
May 01 21:41:32 emonpi systemd[1]: emonhub.service: Service hold-off time over, scheduling restart.
May 01 21:41:33 emonpi systemd[1]: Stopped emonHub service description.
May 01 21:41:33 emonpi systemd[1]: Started emonHub service description.
May 01 21:41:33 emonpi systemd[1]: emonhub.service: Main process exited, code=killed, status=11/SEGV May 01 21:41:33 emonpi systemd[1]: emonhub.service: Unit entered failed state.
May 01 21:41:33 emonpi systemd[1]: emonhub.service: Failed with result 'signal'.
May 01 21:41:33 emonpi systemd[1]: emonhub.service: Service hold-off time over, scheduling restart.
May 01 21:41:33 emonpi systemd[1]: Stopped emonHub service description.
May 01 21:41:33 emonpi systemd[1]: Started emonHub service description.
May 01 21:41:33 emonpi systemd[1]: emonhub.service: Main process exited, code=killed, status=11/SEGV May 01 21:41:33 emonpi systemd[1]: emonhub.service: Unit entered failed state.
May 01 21:41:33 emonpi systemd[1]: emonhub.service: Failed with result 'signal'.
May 01 21:41:33 emonpi systemd[1]: emonhub.service: Service hold-off time over, scheduling restart.
May 01 21:41:33 emonpi systemd[1]: Stopped emonHub service description.
May 01 21:41:33 emonpi systemd[1]: Started emonHub service description.
May 01 21:41:33 emonpi systemd[1]: emonhub.service: Main process exited, code=killed, status=11/SEGV May 01 21:41:33 emonpi systemd[1]: emonhub.service: Unit entered failed state.
May 01 21:41:33 emonpi systemd[1]: emonhub.service: Failed with result 'signal'.
May 01 21:41:33 emonpi systemd[1]: emonhub.service: Service hold-off time over, scheduling restart.
May 01 21:41:33 emonpi systemd[1]: Stopped emonHub service description.
May 01 21:41:33 emonpi systemd[1]: emonhub.service: Start request repeated too quickly.
May 01 21:41:33 emonpi systemd[1]: Failed to start emonHub service description.
May 01 21:41:33 emonpi systemd[1]: emonhub.service: Unit entered failed state.
May 01 21:41:33 emonpi systemd[1]: emonhub.service: Failed with result 'signal'.
(interestingly, the log viewer has the error messages, but when I try and download the log it tells me that /var/log/emonhub/emonhub.log does not exist!)
In case this is a more systemic issue, rather than just a coincidence…is there any information that i can post that might help someone debug the issue?
I waited…and waited…but no restart. I then tried to restart EmonHub separately through the admin interface as well, but again to no avail!
I only updated the EmonCMS software via the admin interface buttons…I’ve done nothing to update Raspbian (which I assume i would need to ssh into the RaspPi and run ‘apt-get update’. I could look at doing that if recommended.
I have just tried ssh’ing into the EmonPi (from my phone over a VPN…isn’t technology great!) - and I have access to try some commands now.
