Thanks.
I confirm that everything is working good except one thing:
Did you noticed a ram increase over time? My emonpi have almost 8 days working without interruption and i notice ram increase every single day. A average of +/- 50 MB each day.
Only restore the ram usage by reboot the emonpi.
Do that happen with you too?
First problem is the /var/log is full. quick fix is to delete daemon.log (it will come back).
Second (and unrelated actually), is this a 4Gb SD Card?
[edit]
What I then meant to say is that it could be that as it cannot write to disk rsyslog may be keeping the logs in RAM. If you make some space then restart the service sudo systemctl restart rsyslog.service does RAM useage drop?
Keep an eye on /var/log and see if the RAM use returns when it fills up again.
But shouldnât the log be deleted automaticaly when that happens?
Some auto âflushâ?
The problema i see is even if i make more space, the log file will continue filling up space.
There is another discussion in progress about possibly adding a safety net to do just that, but it is not definitely going to happen and if it does it wonât be mediate.
The cause of the log partition filling up needs to be address as a bug, the size of log partition and the logrotation must be matched to the usual logfile creation rates (with some headroom). Brian thinks heâs found the issue with the logs filling up. Did you look at the link he gave you?
By default the âdataâ partition used to store Emoncms data is 1GB, this can be expanded to fill the remaining space on the SD card. This has already been done on shop bought emonPi / emonBase. To expand the data partition:
Connect via SSH and run $ sudo emonSDexpand and then follow prompts
âDid you look at the link he gave you?â
Yes. No need to further investigate this topic.
It really seems what is happening to me, is related to that.
Thanks for remind-me the link. Brian send it and i somehow, i missed that.
Thanks to all for all the help. I will wait and watch the other topic to see when will get fixed.