Failed to start DietPi-RAMlog after updating to: v6.17.12

Having issues with your DietPi installation, or, found a bug? Post it here.
Post Reply
iPteiD
Posts: 1
Joined: Sat Nov 10, 2018 10:54 am

Failed to start DietPi-RAMlog after updating to: v6.17.12

Post by iPteiD »

I tried changing to ramdisk > changing to None > changing back to ramlog in dietpi-software. I rebooted the pi at every change.

My system:

Code: Select all

v6.17.12 | RPi 2 Model B (armv7l)
I set it back to:

Code: Select all

DietPi-Ramlog #1 : Hourly clear (recommended).

Error:

Code: Select all

 DietPi-Services
─────────────────────────────────────────────────────
 Mode: status

[  OK  ] DietPi-Services | avahi-daemon active (exited) since Sat 2018-11-10 10:48:48 CET; 25s ago
[  OK  ] DietPi-Services | nmbd active (running) since Sat 2018-11-10 10:48:49 CET; 24s ago
[  OK  ] DietPi-Services | smbd active (running) since Sat 2018-11-10 10:48:50 CET; 23s ago
[  OK  ] DietPi-Services | php7.0-fpm   active (running) since Sat 2018-11-10 10:48:51 CET; 22s ago
[  OK  ] DietPi-Services | nginx        active (running) since Sat 2018-11-10 10:48:55 CET; 18s ago
[  OK  ] DietPi-Services | qbittorrent  active (running) since Sat 2018-11-10 10:48:51 CET; 22s ago
[  OK  ] DietPi-Services | nzbget       active (running) since Sat 2018-11-10 10:48:52 CET; 22s ago
[  OK  ] DietPi-Services | aria2        active (running) since Sat 2018-11-10 10:48:52 CET; 22s ago
[  OK  ] DietPi-Services | jackett      active (running) since Sat 2018-11-10 10:48:52 CET; 22s ago
[  OK  ] DietPi-Services | sonarr       active (running) since Sat 2018-11-10 10:48:52 CET; 22s ago
[  OK  ] DietPi-Services | cron active (running) since Sat 2018-11-10 10:48:52 CET; 21s ago
[  OK  ] DietPi-Services | dropbear     active (running) since Sat 2018-11-10 10:48:30 CET; 44s ago
[  OK  ] DietPi-Services | openvpn      active (exited) since Sat 2018-11-10 10:48:29 CET; 45s ago
[  OK  ] DietPi-Services | dietpi-ramdisk       active (exited) since Sat 2018-11-10 10:48:27 CET; 47s ago
[FAILED] DietPi-Services | dietpi-ramlog        failed (Result: exit-code) since Sat 2018-11-10 10:48:26 CET; 47s ago
● dietpi-ramlog.service - DietPi-RAMlog
   Loaded: loaded (/etc/systemd/system/dietpi-ramlog.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2018-11-10 10:48:26 CET; 47s ago
  Process: 317 ExecStart=/bin/bash -c /boot/dietpi/func/dietpi-ramlog 0 &>> /tmp/dietpi-ramlog.log (code=exited, status=1/FAILURE)
  Process: 308 ExecStartPre=/bin/mkdir -p /var/tmp/dietpi/logs (code=exited, status=0/SUCCESS)

Nov 10 10:48:26 DietPi systemd[1]: Starting DietPi-RAMlog...
Nov 10 10:48:26 DietPi systemd[1]: dietpi-ramlog.service: Control process exited, code=exited status=1
Nov 10 10:48:26 DietPi systemd[1]: Failed to start DietPi-RAMlog.
Nov 10 10:48:26 DietPi systemd[1]: dietpi-ramlog.service: Unit entered failed state.
Nov 10 10:48:26 DietPi systemd[1]: dietpi-ramlog.service: Failed with result 'exit-code'.
[  OK  ] DietPi-Services | dietpi-preboot       active (exited) since Sat 2018-11-10 10:48:28 CET; 46s ago
[  OK  ] DietPi-Services | dietpi-boot  active (exited) since Sat 2018-11-10 10:48:36 CET; 38s ago
[  OK  ] DietPi-Services | dietpi-postboot      active (exited) since Sat 2018-11-10 10:48:36 CET; 38s ago
[ INFO ] DietPi-Services | dietpi-wifi-monitor  inactive (dead)
Post Reply