Community
OpenEnergyMonitor

Community

EmonPi gone mental

Tags: #<Tag:0x00007fa33ead2df0>

Hi - My eomon pi has gone mental. It’s lost a load of data locally, which although a shame is not the end of the world. However, it now updates from its inputs infrequently around 60-80 seconds, has self created a million and one “inactive” inputs - many have some data assigned to them and it would appear to have self created a lode of nodes as well. I can no longer get to the device using its statically assigned IP address, but can attach via the dynamically assigned address. It is still updating the online version, so I am not too worried about wiping it if required and would like to bring it up to the newer base install anyway, which I suspect means losing all the local data anyway.

Model Raspberry Pi 3 Model B Rev 1.2 - 1 GB (Stadium)
SoC Broadcom BCM2835
Serial num. 62C8F2E4
Temperature 50.46°C - 50.5°C
emonpiRelease emonSD-26Oct17

A couple of questions:

  1. can I repair it or would it be better to move forward with the base install anyway? Happy to try either
  2. If I move to the new install - or indeed wipe this and rebuild it - will I lose the data on line? I’m trying to build a view of my energy use over a year - to see the savings from solar panels etc so dont want to lose the online data - no so worried about the local data.
  3. Why does it keep self creating nodes and inputs etc?
LAST ENTRIES ON THE LOG FILE
Starting update via service-runner-update.sh (v2.0) >
Filesystem is unlocked - Write access
type ' rpi-ro ' to lock
- emonSD version: emonSD-26Oct17
emonSD base image check passed...continue update
git pull /home/pi/emonpi
* master
wifiap
On branch master
Your branch is up-to-date with 'origin/master'.
Untracked files:
(use "git add ..." to include in what will be committed)

1

nothing added to commit but untracked files present (use "git add" to track)
Already up-to-date.
-------------------------------------------------------------
Main Update Script
-------------------------------------------------------------
Date: Mon 17 Jun 21:15:12 UTC 2019
EUID: 1000
usrdir: /home/pi
type: all
firmware: emonpi
Checking environment:
- pi user found

EUID: 1000
Hardware detected: EmonPi
Stopping emonPiLCD service
Display update message on LCD
I2C LCD DETECTED Ox27
-------------------------------------------------------------
Hit http://ppa.launchpad.net xenial InRelease
Hit http://mirrordirector.raspbian.org jessie InRelease
Get:1 http://repo.mosquitto.org jessie InRelease [11.0 kB]
Ign http://dl.bintray.com stable InRelease
Hit http://archive.raspberrypi.org jessie InRelease
Get:2 http://dl.bintray.com stable Release.gpg [821 B]
Get:3 http://dl.bintray.com stable Release [6,051 B]
Err http://repo.mosquitto.org jessie InRelease

Hit http://ppa.launchpad.net xenial/main Sources
Hit http://ppa.launchpad.net xenial/main armhf Packages
Hit http://ppa.launchpad.net xenial/main Translation-en
Get:4 http://dl.bintray.com stable/main armhf Packages [77.8 kB]
Hit http://archive.raspberrypi.org jessie/main armhf Packages
Hit http://archive.raspberrypi.org jessie/ui armhf Packages
Hit http://mirrordirector.raspbian.org jessie/main armhf Packages
Hit http://mirrordirector.raspbian.org jessie/contrib armhf Packages
Hit http://mirrordirector.raspbian.org jessie/non-free armhf Packages
Hit http://mirrordirector.raspbian.org jessie/rpi armhf Packages
Ign http://archive.raspberrypi.org jessie/main Translation-en_GB
Ign http://archive.raspberrypi.org jessie/main Translation-en
Ign http://archive.raspberrypi.org jessie/ui Translation-en_GB
Ign http://archive.raspberrypi.org jessie/ui Translation-en
Ign http://dl.bintray.com stable/main Translation-en_GB
Ign http://dl.bintray.com stable/main Translation-en
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en
Ign http://mirrordirector.raspbian.org jessie/main Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/main Translation-en
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en
Fetched 84.6 kB in 22s (3,689 B/s)
Reading package lists...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.mosquitto.org jessie InRelease: The following signatures were invalid: KEYEXPIRED 1515017477 KEYEXPIRED 1515017477 KEYEXPIRED 1515017477

W: Failed to fetch http://repo.mosquitto.org/debian/dists/jessie/InRelease

W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
rng-tools is already the newest version.
python-gpiozero is already the newest version.
python-rpi.gpio is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 139 not upgraded.
Requirement already up-to-date: paho-mqtt in /usr/local/lib/python2.7/dist-packages
You are using pip version 8.1.2, however version 19.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
-------------------------------------------------------------
git pull /home/pi/RFM2Pi
* master
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
Already up-to-date.

git pull /home/pi/usefulscripts
* master
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
Already up-to-date.

git pull /home/pi/huawei-hilink-status
* master
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
Already up-to-date.

git pull /home/pi/oem_openHab
* master
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
Already up-to-date.

git pull /home/pi/oem_node-red
* master
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
Already up-to-date.

-------------------------------------------------------------
EmonPi Firmware Update
-------------------------------------------------------------
Start ATmega328 serial upload using avrdude with latest.hex
Discrete Sampling
avrdude -c arduino -p ATMEGA328P -P /dev/ttyAMA0 -b 115200 -U flash:w:/home/pi/emonpi/firmware/compiled/latest.hex
avrdude-original: Using autoreset DTR on GPIO Pin 7

avrdude-original: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude-original: Device signature = 0x1e950f
avrdude-original: NOTE: "flash" memory has been specified, an erase cycle will be performed
To disable this feature, specify the -D option.
avrdude-original: erasing chip
avrdude-original: reading input file "/home/pi/emonpi/firmware/compiled/latest.hex"
avrdude-original: input file /home/pi/emonpi/firmware/compiled/latest.hex auto detected as Intel Hex
avrdude-original: writing flash (17886 bytes):

Writing | ################################################## | 100% 2.48s

avrdude-original: 17886 bytes of flash written
avrdude-original: verifying flash memory against /home/pi/emonpi/firmware/compiled/latest.hex:
avrdude-original: load data flash data from input file /home/pi/emonpi/firmware/compiled/latest.hex:
avrdude-original: input file /home/pi/emonpi/firmware/compiled/latest.hex auto detected as Intel Hex
avrdude-original: input file /home/pi/emonpi/firmware/compiled/latest.hex contains 17886 bytes
avrdude-original: reading on-chip flash data:

Reading | ################################################## | 100% 1.88s

avrdude-original: verifying ...
avrdude-original: 17886 bytes of flash verified
strace: |autoreset: Broken pipe
strace: |autoreset: Broken pipe
strace: |autoreset: Broken pipe
strace: |autoreset: Broken pipe
strace: |autoreset: Broken pipe

avrdude-original done. Thank you.

strace: |autoreset: Broken pipe
Start emonhub update script:
-------------------------------------------------------------
emonHub update started
-------------------------------------------------------------
- usr directory: /home/pi
git pull /home/pi/emonhub
K0den-wibeee_interface
* emon-pi
hmm01i-syslogging
On branch emon-pi
Your branch is up-to-date with 'origin/emon-pi'.
nothing to commit, working directory clean
Already up-to-date.
Creating emonhub logfile
Symlinking emonhub.conf to /etc/emonhub/emonhub.conf
emonhub.service already installed

Running emonhub automatic node addition script
[[5]]
Node 5 already present
[[6]]
Node 6 already present
[[7]]
Node 7 already present
[[8]]
Node 8 already present
[[9]]
Node 9 already present
[[10]]
Node 10 already present
[[11]]
Node 11 already present
[[12]]
Node 12 already present
[[13]]
Node 13 already present
[[14]]
Node 14 already present
[[19]]
Node 19 already present
[[20]]
Node 20 already present
[[21]]
Node 21 already present
[[22]]
Node 22 already present
[[23]]
Node 23 already present
[[24]]
Node 24 already present
[[25]]
Node 25 already present
[[26]]
Node 26 already present

Start emoncms update:

-------------------------------------------------------------
Emoncms update started
Emoncms update script V1.3 (26th March 2019)
-------------------------------------------------------------
- usr directory: /home/pi
- emoncms directory: /var/www/emoncms

current settings.php md5: 0e4803a641b7784ed23edf87506ce761
Default settings.php md5: 0e4803a641b7784ed23edf87506ce761
settings.php has NOT been user modifed

Checking status of /var/www/emoncms git repository
- git branch: stable
- no local changes
- running: git pull origin stable

From https://github.com/emoncms/emoncms
* branch stable -> FETCH_HEAD
Already up-to-date.

NEW default settings.php md5: 0e4803a641b7784ed23edf87506ce761
settings.php not updated

-------------------------------------------------------------
Updating Emoncms Modules
-------------------------------------------------------------

------------------------------------------
Updating /var/www/emoncms/Modules/app module
------------------------------------------
- git branch: stable
- git tags: 1.2.0-108-g6e5016a
- no local changes
- running: git pull origin stable

From https://github.com/emoncms/app
* branch stable -> FETCH_HEAD
Already up-to-date.

------------------------------------------
Updating /var/www/emoncms/Modules/config module
------------------------------------------
- git branch: stable
- git tags: 1.0.0-63-g1d9238e
- no local changes
- running: git pull origin stable

From https://github.com/emoncms/config
* branch stable -> FETCH_HEAD
Already up-to-date.

------------------------------------------
Updating /var/www/emoncms/Modules/dashboard module
------------------------------------------
- git branch: stable
- git tags: 1.3.1-115-gabd1a0b
- no local changes
- running: git pull origin stable

From https://github.com/emoncms/dashboard
* branch stable -> FETCH_HEAD
Already up-to-date.

------------------------------------------
Updating /var/www/emoncms/Modules/device module
------------------------------------------
- git branch: master
- git tags: 1.1.1-48-g2ea6e74
- no local changes
- running: git pull origin master

From https://github.com/emoncms/device
* branch master -> FETCH_HEAD
Already up-to-date.

------------------------------------------
Updating /var/www/emoncms/Modules/graph module
------------------------------------------
- git branch: stable
- git tags: 1.2.1-151-gc7f4ea9
- no local changes
- running: git pull origin stable

From https://github.com/emoncms/graph
* branch stable -> FETCH_HEAD
Already up-to-date.

------------------------------------------
Updating /var/www/emoncms/Modules/wifi module
------------------------------------------
- git branch: stable
- git tags: 1.2.0-39-gb67783d
- no local changes
- running: git pull origin stable

From https://github.com/emoncms/wifi
* branch stable -> FETCH_HEAD
Already up-to-date.

------------------------------------------
Updating postprocess module
------------------------------------------
- git branch: emonpi
- git tags: 2.1.0
- no local changes
- running: git pull origin emonpi

Already up-to-date.
Already on 'emonpi'
Your branch is up-to-date with 'remotes/origin/emonpi'.

------------------------------------------
Updating sync module
------------------------------------------
- git branch: master
- git tags: 2.0.1-2-gc5eb931
- no local changes
- running: git pull origin master

Already up-to-date.
Already on 'master'
Your branch is up-to-date with 'origin/master'.

------------------------------------------
Updating backup module
------------------------------------------
- git branch: stable
- git tags: 2.0.0-12-g67a1f1d
- no local changes
- running: git pull origin stable

Already up-to-date.
Already on 'stable'
Your branch is up-to-date with 'origin/stable'.

------------------------------------------
Auto Installation of Emoncms Modules
------------------------------------------
- graph module already installed
- device module already installed
- postprocess module already installed
- sync module already installed
- backup module already installed

www-data : www-data video systemd-journal

------------------------------------------
SERVICES
------------------------------------------
emoncms_mqtt.service already installed
feedwriter.service already installed
service-runner.service already installed
------------------------------------------
Reloading systemctl deamon
Update Emoncms database
[]

Restarting Services...
- sudo systemctl restart feedwriter.service
--- ActiveState=active ---
- sudo systemctl restart emoncms_mqtt.service
--- ActiveState=active ---
- sudo systemctl restart emonhub.service
--- ActiveState=active ---
- sudo /etc/init.d/openhab restart
Restarting openhab (via systemctl): openhab.service.
● openhab.service - Starts and stops the openHAB Home Automation Bus
Loaded: loaded (/usr/lib/systemd/system/openhab.service; enabled)
Active: active (running) since Mon 2019-06-17 21:16:33 UTC; 91ms ago
Docs: http://www.openhab.org
Process: 7219 ExecStartPre=/usr/share/openhab/bin/setpermissions.sh (code=exited, status=0/SUCCESS)
Main PID: 7265 (openhab.sh)
CGroup: /system.slice/openhab.service
├─7265 /bin/sh /usr/share/openhab/bin/openhab.sh -o
└─7287 /usr/bin/java -Dlogback.configurationFile=/etc/openhab/logback.xml -Dosgi.clean=true -Declipse.ignoreApp=true -Dosgi.noShutdown=true -Djetty.port=8080 -Dopenhab.configfile=/etc/openhab/configurations/openhab.cfg -Dopenhab.configdir=/etc/openhab/configurations -Dopenhab.logdir=/var/log/openhab -Dsmarthome.userdata=/var/lib/openhab -Djetty.home=/usr/share/openhab -Djetty.port.ssl=8443 -Djetty.config=/etc/openhab/jetty -Djetty.logs=/var/log/openhab -Djetty.rundir=/usr/share/openhab -Dfelix.fileinstall.dir=/usr/share/openhab/addons -Dfelix.fileinstall.filter=.*\.jar -Djava.library.path=/usr/share/openhab/lib -Djava.security.auth.login.config=/etc/openhab/login.conf -Dorg.quartz.properties=/etc/openhab/quartz.properties -Dequinox.ds.block_timeout=240000 -Dequinox.scr.waitTimeOnBlock=60000 -Dfelix.fileinstall.active.level=4 -Djava.awt.headless=true -jar /usr/share/openhab/server/plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar -configuration /var/lib/openhab/workspace -data /var/lib/openhab/workspace -console 5555

Jun 17 21:16:33 emonpi setpermissions.sh[7219]: setting owner openhab:openhab recursively for /var/lib/openhab
Jun 17 21:16:33 emonpi setpermissions.sh[7219]: setting permissions and owner openhab:openhab recursively for /var/log/openhab
Jun 17 21:16:33 emonpi setpermissions.sh[7219]: setting permissions and owner openhab:openhab recursively for /etc/openhab/configurations
Jun 17 21:16:33 emonpi setpermissions.sh[7219]: setting permissions and owner openhab:openhab for /usr/share/openhab/webapps/static
Jun 17 21:16:33 emonpi setpermissions.sh[7219]: setting permissions and owner openhab:openhab for /etc/openhab/jetty/etc/keystore
Jun 17 21:16:33 emonpi setpermissions.sh[7219]: setting permissions and owner openhab:openhab for /etc/openhab/configurations/users.cfg
Jun 17 21:16:33 emonpi systemd[1]: Started Starts and stops the openHAB Home Automation Bus.
Symlinking emonpiupdate.log
Installing emoncms logrotate...

Now setting up Logrotate...
Backing up old logrotate configuration...
Linked to new logrotate configuration...
Backing up old logrotate cron job...
mv: cannot stat ‘/etc/cron.daily/logrotate’: No such file or directory
Linked to new logrotate cron job...

Completed


Completed

Running logrotate...

set log rotate config owner to root

------------------------------------------
Emoncms update script complete
------------------------------------------


Starting emonPi LCD service..

Filesystem is locked - Read Only access
type ' rpi-rw ' to unlock

-------------------------------------------------------------
emonPi update done: Mon 17 Jun 21:16:43 UTC 2019
-------------------------------------------------------------
restarting service-runner

The only point I can answer with certainty is the one about losing your data “on line” - I presume you mean at emoncms.org? NO, your local emonCMS and emoncms.org are entirely separate, the only link is that you happen to send the same data to both.

Why does it keep creating nodes and inputs? Could it be that someone in your immediate locality has started using the same frequency and it just happens that some data you are picking up is “legal” to emonhub, so gets interpreted and added to the system? Dodgy doorbells and car alarms are a known problem. And if something like that is blocking the radio channel, it would also explain the sparse updates.

But taking all the symptoms together, I’d seriously wonder whether you have SD Card issues, but I’ll leave a diagnosis of that to those who know more about this than I do.

1 Like

I’ll be honest, I live on a “old” cul-de-sac - surrounded by pensioners. They have only just grasped that electric appears in the wires in their houses. I doubt anyone has an emon, no-one close has a wireless doorbell likewise I doubt car alarms etc, just because of where my emon is located it’s quite shielded from the outside world. The sparse updates are local - these shouldn’t be affected by radio issues anyway, should they?

I’m happy enough to rebuild it. Will it just append to existing data online?

Cheers for the reply :slight_smile:

emoncms.org doesn’t care where the data comes from, as long as it’s got the correct APIkey. You could type the data manually in your web browser and send it every 10 seconds, if you wished. :roll_eyes:

Whatever you do, I’d advise a fresh SD card. But wait a while and see what those more knowledgeable say.

1 Like

That was the first thought I had too, i.e an SD card that’s about to bite the dust.

1 Like

New card arrived - I guess it’s time to rebuild from scratch. Wish me luck :sweat_smile:

Here’s to ya! thumbsup

OK… after a bit of tinkering trying to get the feeds/inputs named the same as before, tripping over a few things (doh) I would now like to factory reset and build cleanly. But the old factory reset command no longer works on the Oct2018 build?

Anyone know how to reset this build to factory?

If you’re starting over with a fresh copy of emonCMS on a new SD card, you’re effectively at
“factory settings” now.

Yes I was… then I built it - making a few mistakes, so was going to reset and start clean, but fixed my mistakes ok.

Still odd the factory reset cmd no longer works?

Ah, I see. Don’t know why the command itself doesn’t work.
Sounds like that’s one for @glyn.hudson

Would be good to know. Anyway, thanks for your input Bill, much appreciated.

Glyn should be able to shed some light on that one.

YVW, S!

Hi… me again. So with the new card installed all was well… left it alone and haven’t even tinkered. However, we seem to be back to long update intervals. WTF…

Why? 10sec updates it should be…

Hello @Wratty o dear! Can you check if there is a specific process using a lot of processor or memory using top?

$ top

If you reboot the pi does the long update clear? Does it start updating more regularly?

Can you post the server details (click on copy as markdown from the admin page and paste here - no further formatting required)

The first thing to check is the emonhub log and see if it is registering the data from the add on board. Go to the emonhub menu and download the log and paste here.

If that is showing data received at 10s intervals, check to see whether the data is being sent to emoncms via MQTT by issuing the command

mosquitto_sub -v -u 'emonpi' -P 'emonpimqtt2016' -t emon/#
Server Information

Server Information

Services

  • emonhub :- Active Running
  • emoncms_mqtt :- Active Running
  • feedwriter :- Active Running - sleep 60s 18 feed points pending write
  • service-runner :- Active Running
  • emonPiLCD :- Active Running
  • redis-server :- Active Running
  • mosquitto :- Active Running

Emoncms

  • Version :- low-write 10.1.2
  • Modules :- Administration | App v2.0.1 | Backup v2.1.0 | EmonHub Config v2.0.2 | Dashboard v2.0.3 | Device v2.0.0 | EventProcesses | Feed | Graph v2.0.1 | Input | Postprocess v2.1.0 | CoreProcess | Schedule | Network Setup v1.0.0 | sync | Time | User | Visualisation | WiFi v2.0.0
  • Git :-

Server

  • OS :- Linux 4.14.71-v7+
  • Host :- emonpi | emonpi | (172.17.17.11)
  • Date :- 2019-07-18 17:44:46 UTC
  • Uptime :- 17:44:46 up 3 days, 4:25, 1 user, load average: 0.14, 0.09, 0.09

Memory

  • RAM :- Used: 18.82%
    • Total :- 976.74 MB
    • Used :- 183.8 MB
    • Free :- 792.94 MB
  • Swap :- Used: 0.00%
    • Total :- 100 MB
    • Used :- 0 B
    • Free :- 100 MB

Disk

  • / :- Used: 39.98%
    • Total :- 3.81 GB
    • Used :- 1.52 GB
    • Free :- 2.11 GB
  • /boot :- Used: 51.69%
    • Total :- 42.52 MB
    • Used :- 21.98 MB
    • Free :- 20.54 MB
  • /home/pi/data :- Used: 1.17%
    • Total :- 10.32 GB
    • Used :- 123.63 MB
    • Free :- 9.67 GB

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 :- localhost:6379 (127.0.0.1)
  • Date :- 2019-07-18 17:44:45 (UTC 00:00‌​)
  • Stats :- Uptime: 275115 Threads: 3 Questions: 373797 Slow queries: 0 Opens: 43 Flush tables: 1 Open tables: 37 Queries per second avg: 1.358

Redis

  • Version :- 3.2.6
  • Host :- localhost:6379
  • Size :- 80 keys (871.65K)
  • Uptime :- 3 days

MQTT Server

  • Version :- Mosquitto 1.4.10
  • Host :- localhost:1883 (127.0.0.1)

PHP

  • Version :- 7.0.30-0+deb9u1 (Zend Version 3.0.0)
  • Modules :- apache2handler | calendar v7.0.30-0+deb9u1 | Core v7.0.30-0+deb9u1 | ctype v7.0.30-0+deb9u1 | curl v7.0.30-0+deb9u1 | date v7.0.30-0+deb9u1 | dom v20031129 | exif v7.0.30-0+deb9u1 | fileinfo v1.0.5 | filter v7.0.30-0+deb9u1 | ftp v7.0.30-0+deb9u1 | gd v7.0.30-0+deb9u1 | gettext v7.0.30-0+deb9u1 | hash v1.0 | iconv v7.0.30-0+deb9u1 | igbinary v2.0.1 | json v1.4.0 | libxml v7.0.30-0+deb9u1 | mbstring v7.0.30-0+deb9u1 | mcrypt v7.0.30-0+deb9u1 | mosquitto v0.4.0 | mysqli v7.0.30-0+deb9u1 | mysqlnd vmysqlnd 5.0.12-dev - 20150407 - $Id: b5c5906d452ec590732a93b051f3827e02749b83 $ | openssl v7.0.30-0+deb9u1 | pcre v7.0.30-0+deb9u1 | PDO v7.0.30-0+deb9u1 | pdo_mysql v7.0.30-0+deb9u1 | Phar v2.0.2 | posix v7.0.30-0+deb9u1 | readline v7.0.30-0+deb9u1 | redis v4.1.1 | Reflection v7.0.30-0+deb9u1 | session v7.0.30-0+deb9u1 | shmop v7.0.30-0+deb9u1 | SimpleXML v7.0.30-0+deb9u1 | sockets v7.0.30-0+deb9u1 | SPL v7.0.30-0+deb9u1 | standard v7.0.30-0+deb9u1 | sysvmsg v7.0.30-0+deb9u1 | sysvsem v7.0.30-0+deb9u1 | sysvshm v7.0.30-0+deb9u1 | tokenizer v7.0.30-0+deb9u1 | wddx v7.0.30-0+deb9u1 | xml v7.0.30-0+deb9u1 | xmlreader v7.0.30-0+deb9u1 | xmlwriter v7.0.30-0+deb9u1 | xsl v7.0.30-0+deb9u1 | Zend OPcache v7.0.30-0+deb9u1 | zlib v7.0.30-0+deb9u1

Pi

  • Model :- Raspberry Pi 3 Model B Rev 1.2 - 1 GB (Stadium)
  • SoC :- Broadcom BCM2835
  • Serial num. :- 62C8F2E4
  • Temperature :- 51.54°C - 51.0°C
  • emonpiRelease :- emonSD-30Oct18
  • File-system :- read-write
Client Information

Client Information

HTTP

  • Browser :- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
  • Language :- en-GB,en;q=0.5

Window

  • Size :- 1903 x 926

Screen

  • Resolution :- 1920 x 1080

A reboot doesn’t fix it.

Emonhub log?

LAST ENTRIES ON THE LOG FILE
2019-07-15 13:19:35.581|ERROR|feedwriter.php|Starting feedwriter script
2019-07-15 13:19:36.871|WARN|emoncms_mqtt.php|Not connected, retrying connection
2019-07-15 13:19:36.907|WARN|emoncms_mqtt.php|Connecting to MQTT server: Connection Accepted.: code: 0
2019-07-15 13:19:37.931|ERROR|feedwriter.php|Starting feedwriter script
2019-07-15 13:20:51.149|ERROR|feedwriter.php|Starting feedwriter script
2019-07-15 13:26:29.950|ERROR|feedwriter.php|Starting feedwriter script
2019-07-15 13:26:31.117|WARN|emoncms_mqtt.php|Not connected, retrying connection
2019-07-15 13:26:31.139|WARN|emoncms_mqtt.php|Connecting to MQTT server: Connection Accepted.: code: 0
2019-07-15 13:38:10.263|WARN|feed_model.php|Feed model: Requested feed does not exist feedid=16
2019-07-15 13:43:57.452|ERROR|index.php|Not Authenticated|input/view

We need the emonhub log. Go to the cog/emonhub