I have a setup monitoring house power using an EmonTX with one CT connected and transmitting to an EmonBase using a Raspberry Pi B+. This has been running since Jan 2014 with minor updates. I am not recording locally at present. Yesterday ordered an EmonTH to monitor temp/humidity in a garage and following a phone call to a very helpful Trystan and Glyn updated my setup to a more recent version with emonSD-17Jun2015.img and also updating the firmware on the RFM12b. It seemed to be working fine untill the early hours of the morning (around 3am) when the setup seemed to have ground to a halt. I should have examined what was happening directly on the Pi console when I found I couldn't access Emoncms locally or even tried to SSH into the pi. However I cycled the power to bring the system back up. I looked at sys.log and emonhub.log and they are incomplete showing parts of an early boot with part of the latest boot up appended. When I needed to edit a startup file yesterday using nano I found the file to be read only so used a sudo mount -o remount,rw / command to edit the file. That is the point where the log files show the end of an early log and part of the latest start up. I think it's because of this read only feature the log files are behaving this way. Should everything be read only. And if not how can I check or set to how they should be.
Problems with log files
Submitted by Roblister on Wed, 02/12/2015 - 12:21I have a setup monitoring house power using an EmonTX with one CT connected and transmitting to an EmonBase using a Raspberry Pi B+. This has been running since Jan 2014 with minor updates. I am not recording locally at present. Yesterday ordered an EmonTH to monitor temp/humidity in a garage and following a phone call to a very helpful Trystan and Glyn updated my setup to a more recent version with emonSD-17Jun2015.img and also updating the firmware on the RFM12b. It seemed to be working fine untill the early hours of the morning (around 3am) when the setup seemed to have ground to a halt. I should have examined what was happening directly on the Pi console when I found I couldn't access Emoncms locally or even tried to SSH into the pi. However I cycled the power to bring the system back up. I looked at sys.log and emonhub.log and they are incomplete showing parts of an early boot with part of the latest boot up appended. When I needed to edit a startup file yesterday using nano I found the file to be read only so used a sudo mount -o remount,rw / command to edit the file. That is the point where the log files show the end of an early log and part of the latest start up. I think it's because of this read only feature the log files are behaving this way. Should everything be read only. And if not how can I check or set to how they should be.