@borpin
Clutching at straws, I looked at Watchman’s logs.
Watchman has a USB HDD to supplement the SDHC as shown in /etc/fstab …
pi@watchman:/var/log/logrotate $ cat /etc/fstab
proc /proc proc defaults 0 0
##PARTUUID=50c2568e-01 /boot vfat defaults 0 2
##PARTUUID=50c2568e-02 / ext4 defaults,noatime,nodiratime 0 1
##PARTUUID=50c2568e-03 /home/pi/data ext2 defaults,noatime,nodiratime 0 2
# a swapfile is not a swap partition, no line here
# use dphys-swapfile swap[on|off] for that
tmpfs /tmp tmpfs nodev,nosuid,size=30M,mode=1777 0 0
tmpfs /var/tmp tmpfs nodev,nosuid,size=1M,mode=1777 0 0
tmpfs /var/log tmpfs nodev,nosuid,size=50M,mode=1777 0 0
/dev/mmcblk0p1 /boot vfat defaults,noatime,nodiratime 0 2
/dev/sda1 / ext4 defaults,noatime,nodiratime 0 1
/dev/sda2 /home/pi/data ext4 defaults,noatime,nodiratime 0 2
Current SDHC/USB HDD space utilization is revealed by df -H …
pi@watchman:/var/log/logrotate $ df -H
Filesystem Size Used Avail Use% Mounted on
/dev/root 21G 1.8G 19G 9% /
devtmpfs 508M 0 508M 0% /dev
tmpfs 513M 0 513M 0% /dev/shm
tmpfs 513M 52M 461M 11% /run
tmpfs 5.3M 4.1k 5.3M 1% /run/lock
tmpfs 513M 0 513M 0% /sys/fs/cgroup
tmpfs 53M 53M 0 100% /var/log
tmpfs 1.1M 0 1.1M 0% /var/tmp
tmpfs 32M 70k 32M 1% /tmp
/dev/mmcblk0p1 45M 24M 22M 52% /boot
/dev/sda2 293G 1.5G 277G 1% /home/pi/data
tmpfs 103M 0 103M 0% /run/user/1000
/var/log has zero available space which explains why the final entry in syslog is dated 14 Sep …
pi@watchman:/var/log $ tail -n 25 syslog
Sep 14 12:45:06 watchman dhcpcd[537]: eth0: soliciting a DHCPv6 lease
Sep 14 12:45:14 watchman dhcpcd[537]: eth0: Router Advertisement from fe80::e80:63ff:fe39:372c
Sep 14 12:45:14 watchman dhcpcd[537]: eth0: soliciting a DHCPv6 lease
Sep 14 12:45:22 watchman dhcpcd[537]: eth0: Router Advertisement from fe80::e80:63ff:fe39:372c
Sep 14 12:45:22 watchman dhcpcd[537]: eth0: soliciting a DHCPv6 lease
Sep 14 12:45:27 watchman dhcpcd[537]: eth0: Router Advertisement from fe80::e80:63ff:fe39:372c
Sep 14 12:45:27 watchman dhcpcd[537]: eth0: soliciting a DHCPv6 lease
Sep 14 12:45:27 watchman liblogging-stdlog: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0 try http://www.rsyslog.com/e/2359 ]
Sep 14 12:45:27 watchman liblogging-stdlog: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0 try http://www.rsyslog.com/e/2359 ]
Sep 14 12:45:27 watchman liblogging-stdlog: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0 try http://www.rsyslog.com/e/2359 ]
Sep 14 12:45:27 watchman liblogging-stdlog: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0 try http://www.rsyslog.com/e/2359 ]
Sep 14 12:45:27 watchman liblogging-stdlog: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0 try http://www.rsyslog.com/e/2359 ]
Sep 14 12:45:27 watchman liblogging-stdlog: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0 try http://www.rsyslog.com/e/2359 ]
Sep 14 12:45:27 watchman liblogging-stdlog: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0 try http://www.rsyslog.com/e/2359 ]
Sep 14 12:45:27 watchman liblogging-stdlog: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0 try http://www.rsyslog.com/e/2359 ]
Sep 14 12:45:27 watchman liblogging-stdlog: action 'action 3' resumed (module 'builtin:omfile') [v8.24.0 try http://www.rsyslog.com/e/2359 ]
Sep 14 12:45:27 watchman liblogging-stdlog: action 'action 3' suspended, next retry is Sat Sep 14 12:45:57 2019 [v8.24.0 try http://www.rsyslog.com/e/2007 ]
Sep 14 12:45:33 watchman dhcpcd[537]: eth0: Router Advertisement from fe80::e80:63ff:fe39:372c
Sep 14 12:45:33 watchman dhcpcd[537]: eth0: soliciting a DHCPv6 lease
Sep 14 12:45:37 watchman dhcpcd[537]: eth0: Router Advertisement from fe80::e80:63ff:fe39:372c
Sep 14 12:45:37 watchman dhcpcd[537]: eth0: soliciting a DHCPv6 lease
Sep 14 12:45:42 watchman dhcpcd[537]: eth0: Router Advertisement from fe80::e80:63ff:fe39:372c
Sep 14 12:45:42 watchman dhcpcd[537]: eth0: soliciting a DHCPv6 lease
Sep 14 12:45:52 watchman dhcpcd[537]: eth0: Router Advertisement from fe80::e80:63ff:fe39:372c
Which is undoubtedly explained by the logrotate.log …
pi@watchman:/var/log/logrotate $ tail -n 25 logrotate.log
log /var/log/daemon.log.2 doesn't exist -- won't try to dispose of it
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 1
dateext suffix '-20190914'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /var/log/apache2/access.log.1 to /var/log/apache2/access.log.2 (rotatecount 1, 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 1, 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 1
dateext suffix '-20190914'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
renaming /var/log/syslog.1 to /var/log/syslog.2 (rotatecount 1, logstart 1, i 1),
old log /var/log/syslog.1 does not exist
renaming /var/log/syslog.0 to /var/log/syslog.1 (rotatecount 1, logstart 1, i 0),
old log /var/log/syslog.0 does not exist
log /var/log/syslog.2 doesn't exist -- won't try to dispose of it
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
Should I modify fstab and substantially increase the size of /var/log ? as / has 19G available.
Could this situation have any connection with my problems with Node 13? - whether cause or effect?
As an aside - most users will not have a USB HDD - is 53M an optimal limit for /var/log?
Sorry for all the hassle …