EmonPi stopped updating inputs - /var/log/ full

Greebo · 2019-03-20T01:11:43.086Z

TrystanLea:

Perhaps it wasn’t the issue and it was all just write volume

I think that’s probably the case.

I had a weather station and a CurrentCost logging to my Pi1B with a 4GB SD card. It was logging data every minute (from memory) for the weather station and every 4 seconds from the CurrentCost (again from memory). Both of those sets of data were being written to their own RRDs. That SD card stopped writing (it actually went read-only) after just over 12 months.

That was my introduction to SD Card write limits!

It was easy to fix - I just re-imaged the card to a new one and off it went again, but I changed my scripts so that the RRD’s were stored in a tmpfs and flushed (cp’d) to the SD card every 10 minutes. I switched to OEM on a Pi2B+ about 18 months ago, so I’m no longer logging the CurrentCost data but the Pi1B is still running with that same re-imaged card I put into it about 5 years ago.

borpin · 2019-03-20T10:20:52.837Z

Greebo:

I just re-imaged the card to a new one and off it went again

Interesting. Didn’t know that. I thought the card would be corrupted. Just used dd?

Bill.Thomson · 2019-03-20T11:28:50.635Z

borpin:

I thought the card would be corrupted.

In general, once flash memory becomes corrupted, it becomes read-only.
But, it’s possible for it to become corrupted in a manner which prevents reading as well as writing.
e.g. if the inode table gets mangled.

Greebo · 2019-03-20T11:42:50.075Z

In my cases (and I have had 2 instances now where I’ve exhausted the write life), the filesystem didn’t even need a fsck after it had been imaged to a new card.
I used a windows SD imaging tool, but dd would have done the same trick.

bidouilleur · 2019-03-25T18:10:58.942Z

Me again with another install that is filling up /var/log/ in less then 24 hours with feedwriter lines (deamon and syslog) these finish by clogging the partition and after a while the little pi locks up and a manual reboot is needed. There are 101 feeds on that that box.
Have to add this is a pi with an external SSD (this thing )
But since /var/log is not on SSD and limited in space … I have emonhub on error level but I think feedwriter logs are coming in and there isn’t a setting for it (or at least I didn’t find it) . Is there a way to stop these feedwriter lines in the logs ? Like only on error ???

Or is my only hope to move the logs partition to the ssd ???

I did update the pi to latest but even the logrotate can’t cope with the massive spitting of lines
In 4 minutes the syslog grew from 251342 to 310812 (after a reboot to clean the partition)

thanks for ideas, solutions

Server Information


Services
	emonhub	Active Running
	emoncms_mqtt	Active Running
	feedwriter	Active Running - sleep 60s
	service-runner	Active Running
	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 data : Branch: * stable : Describe: v9.5.1-1775-gd0db7a57
Server	OS	Linux 4.14.98-v7+
	Host	emonpi_130 : emonpi_130 : (192.168.1.130)
	Date	2019-03-25 19:07:05 CET
	Uptime	19:07:05 up 13 min, 1 user, load average: 0.11, 0.06, 0.04
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-03-25 19:07:05 (UTC 01:00‌)
	Stats	Uptime: 778 Threads: 4 Questions: 1588 Slow queries: 0 Opens: 26 Flush tables: 1 Open tables: 20 Queries per second avg: 2.041
Redis	Version	3.2.6
	Host	localhost:6379 (127.0.0.1)
	Size
	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.	5CFC8383
	Temperature	CPU: 40.78°C - GPU: 40.8’C
	Release	emonSD-30Oct18
Memory	RAM	Used: 19.49% Total: 976.73 MB Used: 190.39 MB Free: 786.35 MB
	Swap	Used: 0.00% Total: 100 MB Used: 0 B Free: 100 MB
Disk	Mount	Stats
	/	Used: 8.17% Total: 22.8 GB Used: 1.86 GB Free: 19.75 GB
	/boot	Used: 51.49% Total: 42.52 MB Used: 21.89 MB Free: 20.63 MB
	/home	Used: 0.13% Total: 206.31 GB Used: 275.43 MB Free: 195.56 GB
PHP	Version	7.0.33-0+deb9u3 (Zend Version 3.0.0)
	Modules	apache2handler : calendar v7.0.33-0+deb9u3 : Core v7.0.33-0+deb9u3 : ctype v7.0.33-0+deb9u3 : curl v7.0.33-0+deb9u3 : date v7.0.33-0+deb9u3 : dom v20031129 : exif v7.0.33-0+deb9u3 : fileinfo v1.0.5 : filter v7.0.33-0+deb9u3 : ftp v7.0.33-0+deb9u3 : gd v7.0.33-0+deb9u3 : gettext v7.0.33-0+deb9u3 : hash v1.0 : iconv v7.0.33-0+deb9u3 : igbinary v2.0.1 : json v1.4.0 : libxml v7.0.33-0+deb9u3 : mbstring v7.0.33-0+deb9u3 : mcrypt v7.0.33-0+deb9u3 : mosquitto v0.4.0 : mysqli v7.0.33-0+deb9u3 : mysqlnd vmysqlnd 5.0.12-dev - 20150407 - $Id: b5c5906d452ec590732a93b051f3827e02749b83 $ : openssl v7.0.33-0+deb9u3 : pcre v7.0.33-0+deb9u3 : PDO v7.0.33-0+deb9u3 : pdo_mysql v7.0.33-0+deb9u3 : Phar v2.0.2 : posix v7.0.33-0+deb9u3 : readline v7.0.33-0+deb9u3 : redis v4.1.1 : Reflection v7.0.33-0+deb9u3 : session v7.0.33-0+deb9u3 : shmop v7.0.33-0+deb9u3 : SimpleXML v7.0.33-0+deb9u3 : sockets v7.0.33-0+deb9u3 : SPL v7.0.33-0+deb9u3 : standard v7.0.33-0+deb9u3 : sysvmsg v7.0.33-0+deb9u3 : sysvsem v7.0.33-0+deb9u3 : sysvshm v7.0.33-0+deb9u3 : tokenizer v7.0.33-0+deb9u3 : wddx v7.0.33-0+deb9u3 : xml v7.0.33-0+deb9u3 : xmlreader v7.0.33-0+deb9u3 : xmlwriter v7.0.33-0+deb9u3 : xsl v7.0.33-0+deb9u3 : Zend OPcache v7.0.33-0+deb9u3 : zlib v7.0.33-0+deb9u3

Client Information


HTTP	Browser	Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.1.2 Safari/605.1.15
Screen	Resolution	2560 x 1600
Window	Size	1233 x 1420

Gary_Young · 2019-04-26T06:34:12.440Z

My install is filling up the syslog and daemon.log files with Feedwriter entries also. Any hope of a solution? Just purchased my system with everything pre-installed.

borpin · 2019-04-26T07:31:58.118Z

Gary_Young:

My install is filling up the syslog and daemon.log files with Feedwriter entries also.

Feedwriter or emonhub entries?

These steps will reduce the rate of filling. Reboot Required Every 20 Days Or So To Restore Logging - #47 by borpin

@TrystanLea @glyn.hudson we do need a solution to this for existing setups.

TrystanLea · 2019-04-26T15:43:27.691Z

Sorry about this @Gary_Young @bidouilleur I will get the fix for this merged in, it is in progress here: 9.9.9 master merge to stable by TrystanLea · Pull Request #1242 · emoncms/emoncms · GitHub

Gary_Young · 2019-04-26T23:01:06.635Z

Thanks! I appreciate the response and effort on this.

Gary

johnbanks · 2019-04-27T20:37:13.110Z

@TrystanLea

I have 4 emonTx/RPi3’s running the Oct 2018 image updated to 9.9.8.

A fifth RPi3 (watchman) is also on the local network receiving data by HTTP from the 4 emonTx’s.

watchman has mail installed for another purpose which incidentally means I also get a daily email at 6:25 informing on the progress of the log rotate.

On 21 April, the email reported errors when writing – No space left on device.
Today’s email was …

/etc/cron.daily/logrotate:
reading config file /etc/logrotate.conf
Reading state from file: /var/log/logrotate/logrotate.status
Allocating hash table for state file, size 64 entries Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state Creating new state

Handling 1 logs

rotating pattern: /var/log/*.log /var/log/*/*.log /var/log/syslog /var/log/messages /var/log/btmp  1048576 bytes (2 rotations) empty log files are not rotated, old logs are removed considering log /var/log/auth.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/boot.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/daemon.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-23 06:25
  log needs rotating
considering log /var/log/dataplicity.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/emoncms.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/kern.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/mail.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/mysql.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/ntp_update.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/service-runner.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/user.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/apache2/access.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-23 06:25
  log needs rotating
considering log /var/log/apache2/error.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/apache2/other_vhosts_access.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/emonpilcd/emonpilcd.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/logrotate/logrotate.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/mosquitto/mosquitto.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/mysql/error.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/redis/redis-server.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/supervisor/supervisord.log
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/syslog
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-23 06:25
  log needs rotating
considering log /var/log/messages
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) considering log /var/log/btmp
  Now: 2019-04-27 06:25
  Last rotated at 2019-04-14 06:00
  log does not need rotating (log size is below the 'size' threshold) rotating log /var/log/daemon.log, log->rotateCount is 2 dateext suffix '-20190427'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /var/log/daemon.log.2 to /var/log/daemon.log.3 (rotatecount 2, logstart 1, i 2), old log /var/log/daemon.log.2 does not exist renaming /var/log/daemon.log.1 to /var/log/daemon.log.2 (rotatecount 2, logstart 1, i 1), old log /var/log/daemon.log.1 does not exist renaming /var/log/daemon.log.0 to /var/log/daemon.log.1 (rotatecount 2, logstart 1, i 0), old log /var/log/daemon.log.0 does not exist copying /var/log/daemon.log to /var/log/daemon.log.1
error: error writing to /var/log/daemon.log.1: No space left on device
error: error copying /var/log/daemon.log to /var/log/daemon.log.1: No space left on device rotating log /var/log/apache2/access.log, log->rotateCount is 2 dateext suffix '-20190427'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /var/log/apache2/access.log.2 to /var/log/apache2/access.log.3 (rotatecount 2, logstart 1, i 2), old log /var/log/apache2/access.log.2 does not exist renaming /var/log/apache2/access.log.1 to /var/log/apache2/access.log.2 (rotatecount 2, logstart 1, i 1), old log /var/log/apache2/access.log.1 does not exist renaming /var/log/apache2/access.log.0 to /var/log/apache2/access.log.1 (rotatecount 2, logstart 1, i 0), old log /var/log/apache2/access.log.0 does not exist copying /var/log/apache2/access.log to /var/log/apache2/access.log.1
error: error writing to /var/log/apache2/access.log.1: No space left on device
error: error copying /var/log/apache2/access.log to /var/log/apache2/access.log.1: No space left on device rotating log /var/log/syslog, log->rotateCount is 2 dateext suffix '-20190427'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /var/log/syslog.2 to /var/log/syslog.3 (rotatecount 2, logstart 1, i 2), old log /var/log/syslog.2 does not exist renaming /var/log/syslog.1 to /var/log/syslog.2 (rotatecount 2, logstart 1, i 1), old log /var/log/syslog.1 does not exist renaming /var/log/syslog.0 to /var/log/syslog.1 (rotatecount 2, logstart 1, i 0), old log /var/log/syslog.0 does not exist copying /var/log/syslog to /var/log/syslog.1
error: error writing to /var/log/syslog.1: No space left on device
error: error copying /var/log/syslog to /var/log/syslog.1: No space left on device
error: error creating temp state file /var/log/logrotate/logrotate.status.tmp: No space left on device

And the contents of /var/log are …

pi@watchman:/ $ du -ah /var/log
9.7M    /var/log/syslog.3
5.9M    /var/log/daemon.log.3
204K    /var/log/mail.info
204K    /var/log/mail.log
16K     /var/log/dataplicity.log
0       /var/log/ntp_update.log
0       /var/log/service-runner.log
0       /var/log/mysql.log
136K    /var/log/emoncms.log
4.0K    /var/log/supervisor/supervisord.log
4.0K    /var/log/supervisor
4.0K    /var/log/mosquitto/mosquitto.log
4.0K    /var/log/mosquitto
4.0K    /var/log/logrotate/logrotate.status
8.0K    /var/log/logrotate/logrotate.log
12K     /var/log/logrotate
4.0K    /var/log/mysql/error.log
4.0K    /var/log/mysql
2.8M    /var/log/apache2/access.log.3
1.9M    /var/log/apache2/access.log
0       /var/log/apache2/other_vhosts_access.log
4.0K    /var/log/apache2/error.log
4.7M    /var/log/apache2
4.0K    /var/log/redis/redis-server.log
4.0K    /var/log/redis
704K    /var/log/auth.log
4.0K    /var/log/debug
28K     /var/log/kern.log
32K     /var/log/messages
4.0K    /var/log/user.log
20M     /var/log/daemon.log
9.6M    /var/log/syslog
4.0K    /var/log/emonpilcd/emonpilcd.log
4.0K    /var/log/emonpilcd
0       /var/log/btmp
4.0K    /var/log/wtmp
8.0K    /var/log/boot.log
50M     /var/log

The last entries posted to syslog & daemon.log were on 24 Apr at 2:53 when feedwriter was active.

I checked the other nodes (not set up to send emails) …

Three emonTx/RPi3 instances had /var/log full at 50M and had stopped writing to syslog on 14th, 23rd and 26th April. The last entry on one was when feedwriter was active. Two had the last log entry at 6:25 during the log rotate …

Apr 23 06:25:13 emonpi-node-11 liblogging-stdlog: action 'action 12' suspended, next retry is Tue Apr 23 06:25:43 2019 [v8.24.0 try http://www.rsyslog.com/e/2007 ]

I don’t want to try anything radical at present as I’m out of UK & communicating with the system via Dataplicity.

Is it best just to let things run and await the release of the new image that you & others are working on?

Thx

OlavKristiansen · 2020-06-22T12:24:14.875Z

I see something similar, and I am a bit concerned as we are out of the house for the next five weeks:
/var/log: Used: 96.05%
Total : 50 MB
Used : 48.02 MB
Free : 1.98 MB
Write Load : n/a

It has been on this value for the past couple of hours. Will it run full?

df - h:

Filesystem      Size  Used Avail Use% Mounted on
/dev/root       4.0G  2.2G  1.7G  58% /
devtmpfs        484M     0  484M   0% /dev
tmpfs           488M     0  488M   0% /dev/shm
tmpfs           488M  6.6M  482M   2% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           488M     0  488M   0% /sys/fs/cgroup
tmpfs           1.0M  8.0K 1016K   1% /var/lib/php/sessions
tmpfs            30M     0   30M   0% /tmp
tmpfs           1.0M     0  1.0M   0% /var/tmp
/dev/mmcblk0p3   10G  453M  9.1G   5% /var/opt/emoncms
/dev/mmcblk0p1  253M   52M  201M  21% /boot
log2ram          50M   49M  2.0M  97% /var/log
tmpfs            98M     0   98M   0% /run/user/1000

borpin · 2020-06-22T13:22:55.926Z

Have you updated?

OlavKristiansen · 2020-06-22T14:04:09.297Z

Yes, emoncms 10.2.3. I hit the Update all button last week and again today. I have not really observed the status of the /var/log until today, though, so I do not have any growth rate data.

OlavKristiansen · 2020-06-22T14:04:57.401Z

Server Information

Services

emonhub :- Active Running
emoncms_mqtt :- Active Running
feedwriter :- Active Running - sleep 300s 1466 feed points pending write
service-runner :- Active Running
emonPiLCD :- Active Running
redis-server :- Active Running
mosquitto :- Active Running
demandshaper :- Active Running

Emoncms

Version :- low-write 10.2.3
Modules :- Administration | App v2.1.6 | Backup v2.2.3 | EmonHub Config v2.0.5 | Dashboard v2.0.7 | DemandShaper v1.2.5 | Device v2.0.5 | EventProcesses | Feed | Graph v2.0.9 | Input | Postprocess v2.1.4 | CoreProcess | Schedule | Network Setup v1.0.0 | sync | Time | User | Visualisation | WiFi v2.0.2
Git :-
- URL :- GitHub - emoncms/emoncms: Web-app for processing, logging and visualising energy, temperature and other environmental data
- Branch :- * stable
- Describe :- 10.2.3

Server

OS :- Linux 4.19.75-v7+
Host :- emonpi | emonpi | (192.168.1.132)
Date :- 2020-06-22 15:02:34 BST
Uptime :- 15:02:34 up 2:39, 0 users, load average: 0.14, 0.13, 0.09

Memory

RAM :- Used: 18.97%
- Total :- 975.62 MB
- Used :- 185.07 MB
- Free :- 790.55 MB
Swap :- Used: 0.00%
- Total :- 100 MB
- Used :- 0 B
- Free :- 100 MB
  Write Load Period

Disk

/ :- Used: 54.23%
- Total :- 3.92 GB
- Used :- 2.13 GB
- Free :- 1.6 GB
- Write Load :- 353.66 B/s (2 hours 39 mins)
/var/opt/emoncms :- Used: 4.43%
- Total :- 9.98 GB
- Used :- 452.28 MB
- Free :- 9.03 GB
- Write Load :- 382.06 B/s (2 hours 39 mins)
/boot :- Used: 20.55%
- Total :- 252.05 MB
- Used :- 51.79 MB
- Free :- 200.25 MB
- Write Load :- 0.05 B/s (2 hours 39 mins)
/var/log :- Used: 96.12%
- Total :- 50 MB
- Used :- 48.06 MB
- Free :- 1.94 MB
- Write Load :- n/a

HTTP

Server :- Apache/2.4.38 (Raspbian) HTTP/1.1 CGI/1.1 80

MySQL

Version :- 5.5.5-10.3.17-MariaDB-0+deb10u1
Host :- localhost:6379 (127.0.0.1)
Date :- 2020-06-22 15:02:34 (UTC 01:00‌)
Stats :- Uptime: 9576 Threads: 14 Questions: 15670 Slow queries: 0 Opens: 48 Flush tables: 1 Open tables: 42 Queries per second avg: 1.636

Redis

Version :-
- Redis Server :- 5.0.3
- PHP Redis :- 5.0.2
Host :- localhost:6379
Size :- 532 keys (957.66K)
Uptime :- 0 days

MQTT Server

Version :- Mosquitto 1.5.7
Host :- localhost:1883 (127.0.0.1)

PHP

Version :- 7.3.9-1~deb10u1 (Zend Version 3.3.9)
Modules :- apache2handlercalendar Core ctype curl date dom v20031129exif fileinfo filter ftp gd gettext hash iconv json v1.7.0libxml mbstring mosquitto v0.4.0mysqli mysqlnd vmysqlnd 5.0.12-dev - 20150407 - $Id: 7cc7cc96e675f6d72e5cf0f267f48e167c2abb23 $openssl pcre PDO pdo_mysql Phar posix readline redis v5.0.2Reflection session shmop SimpleXML sockets sodium SPL standard sysvmsg sysvsem sysvshm tokenizer wddx xml xmlreader xmlwriter xsl Zend OPcache zlib

Pi

Model :- Raspberry Pi 3 Model B+ Rev 1.3 - 1GB (Sony UK)
Serial num. :- 56D9027C
CPU Temperature :- 55.31°C
GPU Temperature :- 55.8°C
emonpiRelease :- emonSD-17Oct19
File-system :- read-write

Client Information

HTTP

Browser :- Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Safari/537.36
Language :- nb-NO,nb;q=0.9,en-NO;q=0.8,en;q=0.7,no;q=0.6,nn;q=0.5,en-US;q=0.4

Window

Size :- 1483 x 786

Screen

Resolution :- 1920 x 1200

borpin · 2020-06-22T14:07:30.972Z

This should fix it though I would have expected an update to clear out the folder. @TrystanLea

Possible Logrotate issue with 10.2.3 Emoncms

I have noticed an issue with logrotate that may be related to the latest update. This will cause the log folder to fill up. You can see the space used in the Admin screen. To check, run logrotate… sudo /usr/sbin/logrotate -v /etc/logrotate.conf If you see this error near the top… error: Ignoring 00_defaults because the file owner is wrong (should be root or user with uid 0). you have the issue. I think this will fix that issue sudo chown root:pi /opt/openenergymonitor/EmonScripts/defaul…

Do the truncate for any large logs.

OlavKristiansen · 2020-06-22T14:29:27.991Z

Hi, thanks, I followed to that thread and it seems to have fixed the log size for now. It was not the emoncms.log file but the /var/log/logrotate/logrotate.log file, so I trunctated that one and then ran the chown command.

48340   /var/log/logrotate
48336   /var/log/logrotate/logrotate.log
288     /var/log/lastlog
132     /var/log/daemon.log
124     /var/log/syslog
124     /var/log/auth.log
60      /var/log/wtmp
44      /var/log/emonpilcd/emonpilcd.log

This was the situation before:

Filesystem      Size  Used Avail Use% Mounted on
/dev/root       4.0G  2.2G  1.7G  58% /
devtmpfs        484M     0  484M   0% /dev
tmpfs           488M     0  488M   0% /dev/shm
tmpfs           488M  6.6M  482M   2% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           488M     0  488M   0% /sys/fs/cgroup
tmpfs           1.0M  4.0K 1020K   1% /var/lib/php/sessions
tmpfs            30M     0   30M   0% /tmp
tmpfs           1.0M     0  1.0M   0% /var/tmp
/dev/mmcblk0p3   10G  453M  9.1G   5% /var/opt/emoncms
/dev/mmcblk0p1  253M   52M  201M  21% /boot
log2ram          50M   49M  2.0M  97% /var/log
tmpfs            98M     0   98M   0% /run/user/1000

And after:

Filesystem      Size  Used Avail Use% Mounted on
/dev/root       4.0G  2.2G  1.7G  58% /
devtmpfs        484M     0  484M   0% /dev
tmpfs           488M     0  488M   0% /dev/shm
tmpfs           488M  6.6M  482M   2% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           488M     0  488M   0% /sys/fs/cgroup
tmpfs           1.0M  8.0K 1016K   1% /var/lib/php/sessions
tmpfs            30M     0   30M   0% /tmp
tmpfs           1.0M     0  1.0M   0% /var/tmp
/dev/mmcblk0p3   10G  453M  9.1G   5% /var/opt/emoncms
/dev/mmcblk0p1  253M   52M  201M  21% /boot
log2ram          50M  904K   50M   2% /var/log
tmpfs            98M     0   98M   0% /run/user/1000

OlavKristiansen · 2020-06-22T14:30:20.354Z

Is this going to be a permanent fix?

borpin · 2020-06-22T14:43:31.993Z

As long as the logrotate command does not give any errors then yes.

SteffanCook · 2020-09-14T11:59:29.785Z

My emonPi running the 17thOct’19 version of the firmware was reporting a full (50mb/50mb) /var/log.

borpin · 2020-09-14T12:02:12.787Z

I suggest you update emonSD-24Jul20 release