EmonPi hangs with "raspberry pi booting"

AndyEvison · 2017-02-19T09:53:59.351Z

Hi
Initially I got a blank logfile , but after I reran the update I managed to get one which is attached.
I don’t know how to attach the log file as I am classed as a new user

pb66 · 2017-02-19T11:16:53.312Z

I’ve bumped your user level up a notch so you should be able to attach logs now, however the preferred method is to just put the content into the post between 2 sets of 3 back ticks like so

copy and paste log content here

as it is easier to view and doesn’t require users to download it.

It’s a shame we don’t have the original from when the error may of happened but there may still be some clues in the new log.

AndyEvison · 2017-02-19T11:38:39.693Z

Hi

Thank you again

Below is my logfile as you suggested.

----------

Filesystem is unlocked - Write access
type ' rpi-ro ' to lock
Stopping system emonPiLCD daemon:start-stop-daemon: warning: failed to kill 2497: No such process
No process in pidfile '/var/run/emonPiLCD.pid' found running; none killed.
 failed!
I2C LCD DETECTED Ox27
Starting emonPi Update >
via update

Sun Feb 19 09:30:03 UTC 2017

EUID: 1000

emonSD-17Jun2015

git pull /home/pi/emonpi
* master
From https://github.com/openenergymonitor/emonpi
   f8a8499..e60cb72  master     -> origin/master
 * [new branch]      continuous-sampling -> origin/continuous-sampling
 * [new branch]      emonhub-restart -> origin/emonhub-restart
 * [new branch]      openhab2   -> origin/openhab2
 * [new tag]         2.5.0      -> 2.5.0
 * [new tag]         2.7.0      -> 2.7.0
 * [new tag]         2.8.0      -> 2.8.0
 * [new tag]         2.8.1      -> 2.8.1
 * [new tag]         2.8.2      -> 2.8.2
 * [new tag]         emonSD-17Jun2015 -> emonSD-17Jun2015
 * [new tag]         emonSD-22Dec2015 -> emonSD-22Dec2015
Already up-to-date.
git pull /home/pi/RFM2Pi
* master
From https://github.com/openenergymonitor/RFM2Pi
   aafb04b..30e650d  master     -> origin/master
 * [new tag]         0.0.2      -> 0.0.2
From https://github.com/openenergymonitor/RFM2Pi
 * [new tag]         1.2.0      -> 1.2.0
 * [new tag]         1.3        -> 1.3
 * [new tag]         1.3.0      -> 1.3.0
 * [new tag]         1.4.0      -> 1.4.0
 * [new tag]         V1.2       -> V1.2
 * [new tag]         V1.3       -> V1.3
 * [new tag]         v1.2       -> v1.2
Updating aafb04b..30e650d
Fast-forward
 .gitignore                                         |   14 +-
 .travis.yml                                        |   21 +
 README.md                                          |    6 +-
 firmware/RFM69CW_RF_Demo_ATmega328/Blink.cpp.hex   |  161 ----
 ...oot328_8mhz_RFM69CW_RF12_Demo_ATmega328.cpp.hex |  476 +++++------
 .../RFM12_Demo_ATmega328.cpp.hex.readme            |    2 -
 .../RFM69CW_RF12_Demo_ATmega328.cpp.hex.hex        |  595 ++++++++++++++
 .../RFM69CW_RF12_Demo_ATmega328/.gitignore         |    2 +
 .../RFM69CW_RF12_Demo_ATmega328/lib/readme.txt     |   36 +
 .../RFM69CW_RF12_Demo_ATmega328/platformio.ini     |   31 +
 .../RFM69CW_RF12_Demo_ATmega328/src/src.ino        |  658 +++++++++++++++
 ...hex => V12_RFM69CW_RF12_Demo_ATmega328.cpp.hex} |    0
 firmware/boards.txt                                |    2 +
 .../RFM69CW_RF12_Demo_ATmega328_Pulse.cpp.hex      |  623 +++++++++++++++
 .../RFM69CW_RF12_Demo_ATmega328_Pulse.ino}         |   68 +-
 .../RFM69CW_RF12_Demo_ATmega328_Pulse}/dataflash.h |    0
 .../RFM69CW_RF12_Demo_ATmega328_Pulse/pulse.ino    |   41 +
 .../RFM69CW_RF12_Demo_ATmega328_Pulse_DS18B20.ino  |  773 ++++++++++++++++++
 .../compiled.hex                                   |  835 ++++++++++++++++++++
 .../dataflash.h                                    |  358 +++++++++
 .../ds18b20.ino                                    |   40 +
 .../pulse.ino                                      |   36 +
 .../Full_RF12demo_atmega328.cpp.hex                |    0
 .../Full_RF12demo_atmega328.ino                    |    0
 .../ATtiny84_RF12_Demo.cpp.hex                     |    0
 .../Optiboot328_8mhz_RF12_Demo.hex                 |    0
 .../RF12_Demo_atmega328.cpp.hex                    |    0
 .../RF12_Demo_atmega328/RF12_Demo_atmega328.ino    |    0
 .../RF12_Demo_atmega328_OLED/DigoleSerial.cpp      |    0
 .../RF12_Demo_atmega328_OLED/DigoleSerial.h        |    0
 .../RF12_Demo_atmega328_OLED.ino                   |    0
 .../RF12_Demo_atmega328_OLED/RF12mods.cpp          |    0
 .../{ => old}/RF12_Demo_atmega328_OLED/RF12mods.h  |    0
 .../TinySensor_RF12_Demo/TinySensor_RF12_Demo.ino  |    0
 update-RFM12 => update-RFM12.sh                    |    2 +-
 update-RFM69 => update-RFM69.sh                    |    2 +-
 update_dev_pulse_ds18b20.sh                        |    7 +
 37 files changed, 4368 insertions(+), 421 deletions(-)
 create mode 100644 .travis.yml
 delete mode 100644 firmware/RFM69CW_RF_Demo_ATmega328/Blink.cpp.hex
 delete mode 100644 firmware/RFM69CW_RF_Demo_ATmega328/RFM12_Demo_ATmega328.cpp.hex.readme
 create mode 100644 firmware/RFM69CW_RF_Demo_ATmega328/RFM69CW_RF12_Demo_ATmega328.cpp.hex.hex
 create mode 100644 firmware/RFM69CW_RF_Demo_ATmega328/RFM69CW_RF12_Demo_ATmega328/.gitignore
 create mode 100644 firmware/RFM69CW_RF_Demo_ATmega328/RFM69CW_RF12_Demo_ATmega328/lib/readme.txt
 create mode 100644 firmware/RFM69CW_RF_Demo_ATmega328/RFM69CW_RF12_Demo_ATmega328/platformio.ini
 create mode 100644 firmware/RFM69CW_RF_Demo_ATmega328/RFM69CW_RF12_Demo_ATmega328/src/src.ino
 rename firmware/RFM69CW_RF_Demo_ATmega328/{RFM69CW_RF12_Demo_ATmega328.cpp.hex => V12_RFM69CW_RF12_Demo_ATmega328.cpp.hex} (100%)
 create mode 100644 firmware/dev/RFM69CW_RF12_Demo_ATmega328_Pulse/RFM69CW_RF12_Demo_ATmega328_Pulse.cpp.hex
 rename firmware/{RFM69CW_RF_Demo_ATmega328/RFM69CW_RF12_Demo_ATmega328/RFM69CW_RF12_Demo_ATmega328.ino => dev/RFM69CW_RF12_Demo_ATmega328_Pulse/RFM69CW_RF12_Demo_ATmega328_Pulse.ino} (91%)
 rename firmware/{RFM69CW_RF_Demo_ATmega328/RFM69CW_RF12_Demo_ATmega328 => dev/RFM69CW_RF12_Demo_ATmega328_Pulse}/dataflash.h (100%)
 create mode 100644 firmware/dev/RFM69CW_RF12_Demo_ATmega328_Pulse/pulse.ino
 create mode 100644 firmware/dev/RFM69CW_RF12_Demo_ATmega328_Pulse_DS18B20/RFM69CW_RF12_Demo_ATmega328_Pulse_DS18B20.ino
 create mode 100644 firmware/dev/RFM69CW_RF12_Demo_ATmega328_Pulse_DS18B20/compiled.hex
 create mode 100644 firmware/dev/RFM69CW_RF12_Demo_ATmega328_Pulse_DS18B20/dataflash.h
 create mode 100644 firmware/dev/RFM69CW_RF12_Demo_ATmega328_Pulse_DS18B20/ds18b20.ino
 create mode 100644 firmware/dev/RFM69CW_RF12_Demo_ATmega328_Pulse_DS18B20/pulse.ino
 rename firmware/{ => old}/Full_RF12demo_atmega328/Full_RF12demo_atmega328.cpp.hex (100%)
 rename firmware/{ => old}/Full_RF12demo_atmega328/Full_RF12demo_atmega328.ino (100%)
 rename firmware/{ => old}/Pre_compiled_ATtiny84_RF12_Demo_hex/ATtiny84_RF12_Demo.cpp.hex (100%)
 rename firmware/{ => old}/RF12_Demo_atmega328/Optiboot328_8mhz_RF12_Demo.hex (100%)
 rename firmware/{ => old}/RF12_Demo_atmega328/RF12_Demo_atmega328.cpp.hex (100%)
 rename firmware/{ => old}/RF12_Demo_atmega328/RF12_Demo_atmega328.ino (100%)
 rename firmware/{ => old}/RF12_Demo_atmega328_OLED/DigoleSerial.cpp (100%)
 rename firmware/{ => old}/RF12_Demo_atmega328_OLED/DigoleSerial.h (100%)
 rename firmware/{ => old}/RF12_Demo_atmega328_OLED/RF12_Demo_atmega328_OLED.ino (100%)
 rename firmware/{ => old}/RF12_Demo_atmega328_OLED/RF12mods.cpp (100%)
 rename firmware/{ => old}/RF12_Demo_atmega328_OLED/RF12mods.h (100%)
 rename firmware/{ => old}/RFM2Pi_RF12_Demo/TinySensor_RF12_Demo/TinySensor_RF12_Demo.ino (100%)
 rename update-RFM12 => update-RFM12.sh (60%)
 rename update-RFM69 => update-RFM69.sh (58%)
 create mode 100755 update_dev_pulse_ds18b20.sh
git pull /home/pi/emonhub
* emon-pi
From https://github.com/openenergymonitor/emonhub
   2a8664a..c496fc0  emon-pi    -> origin/emon-pi
Updating 1c73004..c496fc0
Fast-forward
 .gitignore                                         |    1 +
 README.md                                          |   94 +++-
 conf/default/emonhub                               |    6 +-
 conf/emonhub-blanknodes.conf                       |   97 ----
 conf/emonhub.conf                                  |  247 +++++-----
 conf/emonpi.default.emonhub.conf                   |  199 ++++++++
 conf/interfacer_examples/directserial/readme.md    |   37 ++
 .../graphite/graphite.emonhub.conf                 |   11 +
 conf/interfacer_examples/graphite/readme.md        |   63 +++
 .../modbus/modbusTCP.emonhub.conf                  |  235 ++++++++++
 conf/interfacer_examples/modbus/readme.md          |   83 ++++
 conf/interfacer_examples/smilices/readme.md        |   36 ++
 .../smilices/smilics.emonhub.conf                  |   54 +++
 conf/interfacer_examples/vedirect/readme.md        |   55 +++
 .../vedirect/vedirect.emonhub.conf                 |   60 +++
 conf/nodes/10                                      |   12 +
 conf/nodes/11                                      |    7 +
 conf/nodes/19                                      |    9 +
 conf/nodes/20                                      |    9 +
 conf/nodes/21                                      |    9 +
 conf/nodes/22                                      |    9 +
 conf/nodes/23                                      |    9 +
 conf/nodes/24                                      |    9 +
 conf/nodes/25                                      |    9 +
 conf/nodes/26                                      |    9 +
 conf/nodes/5                                       |    9 +
 conf/nodes/6                                       |    9 +
 conf/nodes/7                                       |    9 +
 conf/nodes/8                                       |    9 +
 conf/nodes/9                                       |   12 +
 conf/nodes/Readme.md                               |    3 +
 conf/nodes/emonpi_auto_add_nodes.sh                |   18 +
 conf/old.default.emonhub.conf                      |  195 ++++++++
 configuration.md                                   |  475 ++++++++++++++++++++
 install                                            |    6 +-
 service/emonhub                                    |    9 +-
 src/emonhub.py                                     |   81 ++--
 src/emonhub_setup.py                               |    4 +-
 src/interfacers/Cargo.py                           |   10 +-
 src/interfacers/EmonFroniusModbusTcpInterfacer.py  |   44 ++
 src/interfacers/EmonHubEmoncmsHTTPInterfacer.py    |   29 +-
 src/interfacers/EmonHubGraphiteInterfacer.py       |  103 +++++
 src/interfacers/EmonHubJeeInterfacer.py            |    7 +-
 src/interfacers/EmonHubMqttInterfacer.py           |   81 +++-
 src/interfacers/EmonHubSerialInterfacer.py         |    3 +-
 src/interfacers/EmonHubSmilicsInterfacer.py        |  126 ++++++
 src/interfacers/EmonHubSocketInterfacer.py         |    6 +-
 src/interfacers/EmonHubVEDirectInterfacer.py       |  205 +++++++++
 src/interfacers/EmonModbusTcpInterfacer.py         |  141 ++++++
 src/interfacers/emonhub_interfacer.py              |   90 ++--
 50 files changed, 2724 insertions(+), 329 deletions(-)
 delete mode 100644 conf/emonhub-blanknodes.conf
 create mode 100644 conf/emonpi.default.emonhub.conf
 create mode 100644 conf/interfacer_examples/directserial/readme.md
 create mode 100644 conf/interfacer_examples/graphite/graphite.emonhub.conf
 create mode 100644 conf/interfacer_examples/graphite/readme.md
 create mode 100644 conf/interfacer_examples/modbus/modbusTCP.emonhub.conf
 create mode 100644 conf/interfacer_examples/modbus/readme.md
 create mode 100644 conf/interfacer_examples/smilices/readme.md
 create mode 100644 conf/interfacer_examples/smilices/smilics.emonhub.conf
 create mode 100644 conf/interfacer_examples/vedirect/readme.md
 create mode 100644 conf/interfacer_examples/vedirect/vedirect.emonhub.conf
 create mode 100644 conf/nodes/10
 create mode 100644 conf/nodes/11
 create mode 100644 conf/nodes/19
 create mode 100644 conf/nodes/20
 create mode 100644 conf/nodes/21
 create mode 100644 conf/nodes/22
 create mode 100644 conf/nodes/23
 create mode 100644 conf/nodes/24
 create mode 100644 conf/nodes/25
 create mode 100644 conf/nodes/26
 create mode 100644 conf/nodes/5
 create mode 100644 conf/nodes/6
 create mode 100644 conf/nodes/7
 create mode 100644 conf/nodes/8
 create mode 100644 conf/nodes/9
 create mode 100644 conf/nodes/Readme.md
 create mode 100755 conf/nodes/emonpi_auto_add_nodes.sh
 create mode 100644 conf/old.default.emonhub.conf
 create mode 100644 configuration.md
 create mode 100644 src/interfacers/EmonFroniusModbusTcpInterfacer.py
 create mode 100644 src/interfacers/EmonHubGraphiteInterfacer.py
 create mode 100644 src/interfacers/EmonHubSmilicsInterfacer.py
 create mode 100644 src/interfacers/EmonHubVEDirectInterfacer.py
 create mode 100644 src/interfacers/EmonModbusTcpInterfacer.py

Start emonPi Atmega328 firmware update:

=================================
EmonPi update started
=================================

EUID: 1000

Requirement already up-to-date: paho-mqtt in /usr/local/lib/python2.7/dist-packages
Cleaning up...
Stopping OpenEnergyMonitor emonHub: emonhub has been stopped ok.
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 (17898 bytes):

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

avrdude-original: 17898 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 17898 bytes
avrdude-original: reading on-chip flash data:

Reading | ################################################## | 100% 1.86s

avrdude-original: verifying ...
avrdude-original: 17898 bytes of flash verified
Starting OpenEnergyMonitor emonHub: emonhub has been started ok.


Start emonhub update script:

=================================
EmonPi update started
=================================
Running emonhub automatic node addition script
EUID: 1000
EUID: 1000
[[5]]
Node 5 already present
Added node 6 to emonhub.conf
Added node 7 to emonhub.conf
Added node 8 to emonhub.conf
[[9]]
Node 9 already present
[[10]]
Node 10 already present
Added node 11 to emonhub.conf
[[19]]
Node 19 already present
[[20]]
Node 20 already present
[[21]]
Node 21 already present
[[22]]
Node 22 already present
Added node 23 to emonhub.conf
Added node 24 to emonhub.conf
Added node 25 to emonhub.conf
Added node 26 to emonhub.conf

Start emoncms update:

=================================
Emoncms update started

Sun Feb 19 09:30:24 UTC 2017

EUID: 1000
Checking cron tab for service runner entry...
service runner crontab entry already installed

git pull /var/www/emoncms
* low-write
# On branch low-write
# Changes not staged for commit:
#   (use "git add/rm <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#	deleted:    Modules/input/input_menu.php
#
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	Modules/backup
#	Modules/graph/
no changes added to commit (use "git add" and/or "git commit -a")
Already up-to-date.

git pull /var/www/emoncms/Modules/nodes
# On branch master
nothing to commit (working directory clean)
* master
Already up-to-date.

git pull /var/www/emoncms/Modules/app
* master
# On branch master
nothing to commit (working directory clean)
Already up-to-date.

git pull /var/www/emoncms/Modules/config
* master
# On branch master
nothing to commit (working directory clean)
Your configuration specifies to merge with the ref 'master'
from the remote, but no such ref was fetched.

git pull /var/www/emoncms/Modules/wifi
* master
# On branch master
nothing to commit (working directory clean)
Already up-to-date.
git pull /var/www/emoncms/Modules/dashboard
* low-write
# On branch low-write
# Changes not staged for commit:
#   (use "git add/rm <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#	deleted:    ../input/input_menu.php
#
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	../backup
#	../graph/
no changes added to commit (use "git add" and/or "git commit -a")
Already up-to-date.

git pull /var/www/emoncms/Modules/graph
* master
# On branch master
nothing to commit (working directory clean)
Already up-to-date.

git pull /home/pi/postprocess
Already on 'emonpi'
Already up-to-date.
git pull /home/pi/backup
* master
# On branch master
nothing to commit (working directory clean)
Already up-to-date.


Update Emoncms database
[]

Restarting Services...
Restarting OpenEnergyMonitor emonHub: emonhub has been restarted ok.
Log is turned off
Restarting feedwriter
Log is turned off
Restarting emoncms-nodes

sudo: systemctl: command not found

set log rotate config owner to root
Restarting Services...


Job is already running!
Start emonPi LCD service
Starting system emonPiLCD daemon:.

...................
emonPi update done
Sun Feb 19 09:31:27 UTC 2017

Filesystem is locked - Read Only access
type ' rpi-rw ' to unlock
Filesystem is unlocked - Write access
type ' rpi-ro ' to lock
Stopping system emonPiLCD daemon:start-stop-daemon: warning: failed to kill 12072: No such process
No process in pidfile '/var/run/emonPiLCD.pid' found running; none killed.
 failed!
I2C LCD DETECTED Ox27
Starting emonPi Update >
via update

Sun Feb 19 09:36:03 UTC 2017

EUID: 1000

emonSD-17Jun2015

git pull /home/pi/emonpi
* master
Already up-to-date.
git pull /home/pi/RFM2Pi
* master
Already up-to-date.
git pull /home/pi/emonhub
* emon-pi
Already up-to-date.

Start emonPi Atmega328 firmware update:

=================================
EmonPi update started
=================================

EUID: 1000

Requirement already up-to-date: paho-mqtt in /usr/local/lib/python2.7/dist-packages
Cleaning up...
Stopping OpenEnergyMonitor emonHub: emonhub has been stopped ok.
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 (17898 bytes):

Writing | ################################################## | 100% 2.51s

avrdude-original: 17898 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 17898 bytes
avrdude-original: reading on-chip flash data:

Reading | ################################################## | 100% 1.91s

avrdude-original: verifying ...
avrdude-original: 17898 bytes of flash verified
Starting OpenEnergyMonitor emonHub: emonhub has been started ok.


Start emonhub update script:

=================================
EmonPi update started
=================================
Running emonhub automatic node addition script
EUID: 1000
EUID: 1000
[[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
[[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

Sun Feb 19 09:36:16 UTC 2017

EUID: 1000
Checking cron tab for service runner entry...
service runner crontab entry already installed

git pull /var/www/emoncms
* low-write
# On branch low-write
# Changes not staged for commit:
#   (use "git add/rm <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#	deleted:    Modules/input/input_menu.php
#
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	Modules/backup
#	Modules/graph/
no changes added to commit (use "git add" and/or "git commit -a")
Already up-to-date.

git pull /var/www/emoncms/Modules/nodes
# On branch master
nothing to commit (working directory clean)
* master
Already up-to-date.

git pull /var/www/emoncms/Modules/app
* master
# On branch master
nothing to commit (working directory clean)
Already up-to-date.

git pull /var/www/emoncms/Modules/config
* master
# On branch master
nothing to commit (working directory clean)
Your configuration specifies to merge with the ref 'master'
from the remote, but no such ref was fetched.

git pull /var/www/emoncms/Modules/wifi
* master
# On branch master
nothing to commit (working directory clean)
Already up-to-date.
git pull /var/www/emoncms/Modules/dashboard
* low-write
# On branch low-write
# Changes not staged for commit:
#   (use "git add/rm <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#	deleted:    ../input/input_menu.php
#
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	../backup
#	../graph/
no changes added to commit (use "git add" and/or "git commit -a")
Already up-to-date.

git pull /var/www/emoncms/Modules/graph
* master
# On branch master
nothing to commit (working directory clean)
Already up-to-date.

git pull /home/pi/postprocess
Already on 'emonpi'
Already up-to-date.
git pull /home/pi/backup
* master
# On branch master
nothing to commit (working directory clean)
Already up-to-date.


Update Emoncms database
[]

Restarting Services...
Restarting OpenEnergyMonitor emonHub: emonhub has been restarted ok.
Log is turned off
Restarting feedwriter
Log is turned off
Restarting emoncms-nodes

sudo: systemctl: command not found

set log rotate config owner to root
Restarting Services...


Job is already running!
Start emonPi LCD service
Starting system emonPiLCD daemon:.

emonPi update done
Sun Feb 19 09:37:19 UTC 2017

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

----------



----------

pb66 · 2017-02-19T12:23:34.302Z

At first glance I can see that there are 2 logs, both for today. The first one has pulled in many updates from git which suggests the original update did not get far before it fell over as any completed pulls do not get repeated.

At the very begining there is a warning that the emonPiLCD service couldn’t be stopped as there was no PID file, suggesting it wasn’t running, this would fit with what you have seen and also with the fact that the emonPiLCD is restarted right at the end of the update process so if the original update failed to complete no attempt to restart it would of occurred.

However if you have rebooted in between updates, then the service should have been running as it is started at boot, in this case it would suggest there is an issue starting the emonPiLCD service.

what do you get if you run the following from the command line?
``
sudo service emonPiLCD status


IMO it is not worth spending hours trying to fix this image as it will always be out of date, there have been a lot of changes and even the OS has moved on to a safer version ([Dirty Cow vulnerability](https://community.openenergymonitor.org/t/dirty-cow-vulnerability/2010)) which cannot be easily reached from the image you are running.

If you are able to "export" your data for importing into the new image that will prevent data loss as your feeds are retained, but you will need to rebuild your input and input processing as the nodes module is no longer used and changes to the dashboards module mean you will need to reconfigure them too as they now use feedid refs not feed names as before. But investing time in these changes has more value than patching up the old image.

I would recommend possibly using a second (larger?) 8gb SD card so that you needn't disturb the existing SD card and then if you have a USB usb card reader you can always access the old image by plugging it into the emonPi running the new image if you need to.

AndyEvison · 2017-02-19T15:49:54.304Z

Hi Thanks again for such a quick response.

I thought the answer would be to start again. I assume my emonpi requires an SD card rather than a microSD. (I don’t think the emonpi has ever been out of its box, hence I have not seen the installed a=card.

At this point I do not know how to run something from the command line prompt. I am a windows user so don’t know how to get there.

I will go and read up on downloading the latest image so I reinstall and start again.

Many thanks
Andy

AndyEvison · 2017-02-19T17:17:40.594Z

Hi

Just took the emonpi out of its case and found it is a micro SD card so the newly flashed SD card wont fit. Will get an appropriate size one in the morning.

regards
Andy

pb66 · 2017-02-19T18:55:38.660Z

AndyEvison:

I assume my emonpi requires an SD card rather than a microSD.

AndyEvison:

Just took the emonpi out of its case and found it is a micro SD card

Sorry yes I didn’t see your earlier before you posted again, I should of been more specific it is a micro SD, all the emonPi’s are as all the Pi’s are since prior to the emonPi launch, only the early A and B (not +'s, 2’s, 3’s or 0’s) are full SD.

AndyEvison · 2017-02-20T08:43:56.312Z

Sorry about that question. I did have a very early Pi which did have an SD card, but since then I have a Pi3 used as a media player which obviously has micro SD. As I had an emonpi for sometime so I guessed wrongly. So thanks for the good advice. I am awaiting arrival a new Micro SD card which seems by far the best approach, especially as I do not have the knowledge to dive into the Linux commands.

AndyEvison · 2017-02-20T17:49:57.631Z

Hi
New card received and image created on it. It all fired up OK as we expected. Looking at inputs I can see data relating my CT sensors, and voltage as well as the temp sensors that I have on an emonTX3. At the moment each time I try to define a feed I get a message “Error: feed could not be created, undefined”. I am off to read the guides to see what I have missed.

PS I like the interface and admin console although I do not understand what the scrolling messages mean yet.

AndyEvison · 2017-02-23T15:49:28.161Z

Hi,
Things seems to be mostly working. The emonPi is sending data to emoncms and I have reactivated my dashboard and it is working.

The remaining issue is that when logging on to my emonPi I can see all the inputs which refresh at regular intervals. But when I try to create any feed I get a message “Error! Feed could not be created ’ undefined”. Also in the console view I get entries like this:
|ERROR|feed_model.php|EngineClass() Engine id ‘1’ is not supported

I cannot find much on the community and I have tried restarting but nothing changes.
Thanks

hockeyshooter · 2017-03-01T11:18:02.498Z

Same issue with me. Mine is a metal ended one and after an update to (I think) 2.82 I’m stuck with “Raspberry Pi Booting…” on the screen, the pushbutton does nothing, the reset button does nothing and of course I can’t see any IP addresses so have to query the router to see what its IP is.

Was the update I did corrupted by Amazon S3?!

There is no data on the device that I’m worried about keeping and I even have a spare card (32Gb) I can use instead. If my only recourse is to re-flash the card, can someone point me to the idiot’s guide for doing so?

I can log into its web interface via wifi but can’t telnet into it at all. All of its nodes appear to be inactive.

hockeyshooter · 2017-03-01T12:06:27.411Z

Have tried the update link again. The log now says:

Filesystem is unlocked - Write access
type ' rpi-ro ' to lock
Stopping system emonPiLCD daemon:start-stop-daemon: warning: failed to kill 2479: No such process
No process in pidfile '/var/run/emonPiLCD.pid' found running; none killed.
 failed!
I2C LCD DETECTED Ox27
Starting emonPi Update >
via update

Wed Mar  1 11:42:03 UTC 2017

EUID: 1000

emonSD-17Jun2015_2updated

git pull /home/pi/emonpi
* master
Already up-to-date.
git pull /home/pi/RFM2Pi
* master
Already up-to-date.
git pull /home/pi/emonhub
* emon-pi
Already up-to-date.

Start emonPi Atmega328 firmware update:

=================================
EmonPi update started
=================================

EUID: 1000

Requirement already up-to-date: paho-mqtt in /usr/local/lib/python2.7/dist-packages
Cleaning up...
Stopping OpenEnergyMonitor emonHub: emonhub has been stopped ok.
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 (17898 bytes):

Writing | ################################################## | 100% 2.56s

avrdude-original: 17898 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 17898 bytes
avrdude-original: reading on-chip flash data:

Reading | ################################################## | 100% 1.95s

avrdude-original: verifying ...
avrdude-original: 17898 bytes of flash verified
Starting OpenEnergyMonitor emonHub: emonhub has been started ok.


Start emonhub update script:

=================================
EmonPi update started
=================================
Running emonhub automatic node addition script
EUID: 1000
EUID: 1000
[[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
[[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

Wed Mar  1 11:42:22 UTC 2017

EUID: 1000
Checking cron tab for service runner entry...
service runner crontab entry already installed

git pull /var/www/emoncms
* low-write
# On branch low-write
# Changes not staged for commit:
#   (use "git add/rm <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#	deleted:    Modules/input/input_menu.php
#
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	Modules/backup
#	Modules/graph/
#	old.settings.php
no changes added to commit (use "git add" and/or "git commit -a")
Already up-to-date.

git pull /var/www/emoncms/Modules/nodes
# On branch master
nothing to commit (working directory clean)
* master
Already up-to-date.

git pull /var/www/emoncms/Modules/app
* master
# On branch master
nothing to commit (working directory clean)
Already up-to-date.

git pull /var/www/emoncms/Modules/config
* master
# On branch master
nothing to commit (working directory clean)
Your configuration specifies to merge with the ref 'master'
from the remote, but no such ref was fetched.

git pull /var/www/emoncms/Modules/wifi
* master
# On branch master
nothing to commit (working directory clean)
Already up-to-date.
git pull /var/www/emoncms/Modules/dashboard
* low-write
# On branch low-write
# Changes not staged for commit:
#   (use "git add/rm <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#	deleted:    ../input/input_menu.php
#
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	../backup
#	../graph/
#	../../old.settings.php
no changes added to commit (use "git add" and/or "git commit -a")
Already up-to-date.

git pull /var/www/emoncms/Modules/graph
* master
# On branch master
nothing to commit (working directory clean)
Already up-to-date.

git pull /home/pi/postprocess
Already on 'emonpi'
Already up-to-date.
git pull /home/pi/backup
* master
# On branch master
nothing to commit (working directory clean)
Already up-to-date.


Update Emoncms database
[]

Restarting Services...
Restarting OpenEnergyMonitor emonHub: emonhub has been restarted ok.
Log is turned off
Restarting feedwriter
Log is turned off
Restarting emoncms-nodes

sudo: systemctl: command not found

set log rotate config owner to root
Restarting Services...


Job is already running!
Start emonPi LCD service
Starting system emonPiLCD daemon:.

...................
emonPi update done
Wed Mar  1 11:43:31 UTC 2017

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

pb66 · 2017-03-01T12:52:19.285Z

AndyEvison:

At the moment each time I try to define a feed I get a message “Error: feed could not be created, undefined”. I am off to read the guides to see what I have missed.

Can you recall have you expanded the filesystem?

Although a bit cryptic the error may just be that it cannot create a feed (ignoring the “ERROR|feed_model.php|EngineClass() Engine id ‘1’ is not supported” for a moment). The downloaded Image is highly compacted before compression so there is no spare space until the fiile system (and the data partition) is expanded.

On the emoncms admin page does the disc space indication show you have any space or is it 100% used?

You can also check disk usage via ssh using

df -h

pb66 · 2017-03-01T12:58:05.690Z

hockeyshooter:

Was the update I did corrupted by Amazon S3?!

It’s most likely due to the fact you had an early 2015 image which is incompatible with the current image updater. the clue is the “sudo: systemctl: command not found” in your update.log, that suggests you are not running the latest Raspbian Jessie, plus you have the “emoncms nodes module” which is now retired, If you have no important data on that image I would recommend downloading the latest image and start afresh. There is little point trying to fix something that will always be “old software” even if some later updates are applied.

hockeyshooter · 2017-03-01T13:01:27.213Z

pb66:

There is little point trying to fix something that will always be “old software” even if some later updates are applied.

Agreed and quite happy to start that card from scratch. Hoping now that you can point me to an idiots guide because I’m really not familiar with doing this sort of thing!

pb66 · 2017-03-01T13:07:33.647Z

I can only suggest starting with the “guide” link at the top of the page, I believe it is supposed to be self explanatory to follow so please report back if that’s not the case. I do not know where to point you or where to find the latest image without digging myself, sorry if that sounds unhelpful, that is not my intention I just haven’t kept abreast of the “fluid” movements of the docs of late.

AndyEvison · 2017-03-01T13:31:05.305Z

Hi,

Can’t quite remember about extending the file system so this could be the answer. Originally I used a 16gb card. I think I had the same problem then but I screwed up my emonCMS dashboard so I re-flashed the original “4gb” card and put it in and again my dashboard etc was fine on emoncms. So the truth is that I must be out of space. Also the “admin” option has gone from the menu - following your comment that seems likely to be the cause of that too. Will try again and this time make sure I have extended the partition.
Many thanks

hockeyshooter · 2017-03-02T10:22:57.967Z

I’ve just downloaded the 7 Nov 2016 image and flashed it onto a new (32Gb) card and the emonPi again gets no further than “Raspberry Pi Booting…” - I don’t even see anything on an attached screen.

Found the instructions at the bottom of this page:

GitHub

emonSD pre built SD card Download & Change Log · openenergymonitor/emonpi...

Raspberry Pi Based Energy Monitor. Hardware, Firmware & related software for the PI. - emonSD pre built SD card Download & Change Log · openenergymonitor/emonpi Wiki

Have instead gone back to the 3 May 2016 release, which appears to work. So maybe the Nov 2016 image is corrupted? Or just doesn’t like the Pi 2?

AndyEvison · 2017-03-02T11:15:40.368Z

Hi

I was correct in thinking I had screwed up my new 16GB SD card as when I put it into the Emonpi it hung on "RaspberryPI rebooting. So I removed it and re-flashed it and all started up fine. I let it run through updates. I am now able to create feeds etc.

As far as I am concerned everything seems to be working. as it should be. So your suggestions about lack of space on my old 4GB card were correct. Also it seems clear that something I did on the first attempt with the 16GB card managed to cause it to re-create the original “hanging on Raspberry Pi booting” message, but I can’t tell you quite what. I assume that re-flashing the card would remove any logs that would show the cause. Now everything is working I am not bothered about the cause but if my system holds anything that may help other avoid or resolve it I am happy to provide it.

Regards

Andy - my issue /question is solved. Thanks for all the help.

pb66 · 2017-03-02T12:38:15.770Z

As far as I’m aware the image is ok, did you check the checksum after downloading? perhaps corrupted in transit?

The image does try to update at firstboot and that can take a while to finish. During that time it can be unclear something is happening, especially if the display isn’t functioning correctly.

I would recommend downloading again (if needed) confirm the checksum is good and install to your SD card. When you put it in the emonPi, ensure it has a good Ethernet connection, power it up and leave it for a while, half hour or so at least so you know everything will have run it’s course. Then and only then try rebooting, after the firmware has been updated and updates applied.