log2ram: log2ram.service failed (timeout)

pi@RasPiHole:~ $ `cd log2ram-master`
pi@RasPiHole:~/log2ram-master $ `systemctl status log2ram.service`
● log2ram.service - Log2Ram
   Loaded: loaded (/etc/systemd/system/log2ram.service; enabled; vendor preset: enabled)
   Active: failed (Result: timeout) since Sun 2019-02-10 14:01:29 CET; 3min 23s ago
  Process: 217 ExecStart=/usr/local/bin/log2ram start (code=killed, signal=TERM)
 Main PID: 217 (code=killed, signal=TERM)

Feb 10 14:01:29 RasPiHole log2ram[217]: [58B blob data]
Feb 10 14:01:29 RasPiHole log2ram[217]: [58B blob data]
Feb 10 14:01:29 RasPiHole log2ram[217]: [59B blob data]
Feb 10 14:01:29 RasPiHole log2ram[217]: mount: wrong fs type, bad option, bad superblock on log2ram,
Feb 10 14:01:29 RasPiHole log2ram[217]:        missing codepage or helper program, or other error
Feb 10 14:01:29 RasPiHole log2ram[217]:        In some cases useful info is found in syslog - try
Feb 10 14:01:29 RasPiHole log2ram[217]:        dmesg | tail or so.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

/log2ram-master $  `dmesg | tail`
[  125.479972] systemd[1]: log2ram.service: Main process exited, code=killed, status=15/TERM
[  125.480821] systemd[1]: Failed to start Log2Ram.
[  125.481205] systemd[1]: log2ram.service: Unit entered failed state.
[  125.481248] systemd[1]: log2ram.service: Failed with result 'timeout'.
[  125.486038] systemd[1]: Starting Journal Service...
[  125.594830] systemd[1]: Started Journal Service.
[  125.643757] systemd-journald[2469]: Received request to flush runtime journal from PID 1
[  126.593789] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[  126.621515] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
[  128.228864] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 23 (11 by maintainers)

Most upvoted comments

Thank, I’m out of time now. I will check next week. Thank for all the informations.

azlux on Feb 21, 2019

Your case is curious. First time I see this issue. Can you enable log2ram again ? I also need the ouput of :

findmnt --verify
cat /etc/log2ram.conf | grep SIZE
free -h
cat /etc/fstab
systemd-analyze plot - please use a paste bin for this one. Lot of output, it’s a svg picture.
systemd-analyze critical-chain
whereis mount
mount -V

Can you try to manually mount a folder to test if you have the same error, and same dmesg ? Remove the folder /var/hdd.log/ and use the following command Here the command:

mount --bind /var/log/ /var/hdd.log/
mount --make-private /var/hdd.log/
mount -t tmpfs -o nosuid,noexec,nodev,mode=0755,size="40M" log2ram /var/log/

azlux on Feb 13, 2019

Strange. Can I have the output of mount ?

azlux on Feb 11, 2019

It’s not possible. Log2Ram do not create tmpfs is the service cannot start. Do you use the raspbian lite ?

azlux on Feb 11, 2019

Wait. You are on a raspberry and you have many tmpfs reserving ram space. To you think there are enought RAM space available for log2ram (depending of your configuration)

Can you check with free -h ?

azlux on Feb 11, 2019

Hi, Can you give me the output of sudo fdisk -l ?

azlux on Feb 10, 2019