Required Information
- DietPi version |
G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=5
G_DIETPI_VERSION_RC=1
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’ - Distro version | bullseye
- Kernel version | aarch64 GNU/Linux
- SBC model | RPI4+
- Power supply used | (EG: 5V 1A RAVpower)
- SD card used |
Hi, I run a pretty basic setup, really just proFTP and Portainer (that runs vpn and various arrs + plex). Up until late May I was backing up the system as described here: Automate dietpi-backup - #14 by brightwolf
This functionality has since been added to dietpi-backup so I decided to swap over to that. The problem I’ve found is that dietpi-backup regularly doesn’t complete/fails and therefore that the services are not restarted until I do it manually.
Expected behaviour
– services are stopped
- backup is completed
- services are restarted
Actual behaviour
- services are stopped
- backup is not completed
- services are not restarted
Extra details
Daily cron has been set to run at 2am.
.dietpi-backup.log shows no completed entry for today (13th)
.dietpi-backup_stats
Backup completed : 2022-05-22_04:53:59
Backup completed : 2022-05-23_02:04:32
Backup completed : 2022-05-24_02:40:28
Backup completed : 2022-05-25_02:14:13
Backup completed : 2022-05-28_02:03:55
Backup completed : 2022-05-31_02:04:10
Backup completed : 2022-06-03_02:03:39
Backup completed : 2022-06-06_02:04:34
Backup completed : 2022-06-09_02:05:09
Backup completed : 2022-06-12_02:02:54
● docker.service - Docker Application Container Engine │
│ Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled) │
│ Drop-In: /usr/lib/systemd/system/docker.service.d │
│ └─dietpi-simple.conf │
│ Active: inactive (dead) since Mon 2022-06-13 02:00:46 +07; 6h ago │
│ TriggeredBy: ● docker.socket │
│ Docs: https://docs.docker.com │
│ Process: 688653 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, │
│ status=0/SUCCESS) │
│ Main PID: 688653 (code=exited, status=0/SUCCESS) │
│ CPU: 14min 39.913s │
│ │
│ Jun 13 02:00:37 DietPi 85d4103e3a4f[688653]: [s6-finish] sending all processes the TERM signal. │
│ Jun 13 02:00:39 DietPi ad3d0da37160[688653]: [s6-finish] sending all processes the KILL signal and exiting. │
│ Jun 13 02:00:39 DietPi 3466f74bc0f5[688653]: [s6-finish] sending all processes the KILL signal and exiting. │
│ Jun 13 02:00:39 DietPi 68001ceb3ac3[688653]: [s6-finish] sending all processes the KILL signal and exiting. │
│ Jun 13 02:00:40 DietPi 8f2ad045b4ca[688653]: [s6-finish] sending all processes the KILL signal and exiting. │
│ Jun 13 02:00:40 DietPi 2f6df63c9780[688653]: [s6-finish] sending all processes the KILL signal and exiting. │
│ Jun 13 02:00:40 DietPi 85d4103e3a4f[688653]: [s6-finish] sending all processes the KILL signal and exiting. │
│ Jun 13 02:00:46 DietPi systemd[1]: docker.service: Succeeded. │
│ Jun 13 02:00:46 DietPi systemd[1]: Stopped Docker Application Container Engine. │
│ Jun 13 02:00:46 DietPi systemd[1]: docker.service: Consumed 14min 39.913s CPU time.
│ ● cron.service - Regular background program processing daemon │
│ Loaded: loaded (/lib/systemd/system/cron.service; disabled; vendor preset: enabled) │
│ Active: inactive (dead) │
│ Docs: man:cron(8) │
│ │
│ Jun 13 02:00:35 DietPi systemd[1]: cron.service: Unit process 1093782 (cron) remains running after unit stopped. │
│ Jun 13 02:00:35 DietPi systemd[1]: cron.service: Unit process 1093783 (dash) remains running after unit stopped. │
│ Jun 13 02:00:35 DietPi systemd[1]: cron.service: Unit process 1093784 (run-parts) remains running after unit │
│ stopped. │
│ Jun 13 02:00:35 DietPi systemd[1]: cron.service: Unit process 1093786 (dietpi) remains running after unit stopped. │
│ Jun 13 02:00:35 DietPi systemd[1]: cron.service: Unit process 1094556 (dietpi-backup) remains running after unit │
│ stopped. │
│ Jun 13 02:00:35 DietPi systemd[1]: cron.service: Unit process 1094571 (dietpi-services) remains running after unit │
│ stopped. │
│ Jun 13 02:00:35 DietPi systemd[1]: cron.service: Unit process 1094574 (systemctl) remains running after unit │
│ stopped. │
│ Jun 13 02:00:35 DietPi systemd[1]: Stopped Regular background program processing daemon. │
│ Jun 13 02:00:35 DietPi systemd[1]: cron.service: Consumed 27.041s CPU time. │
│ Jun 13 02:02:34 DietPi CRON[1093782]: pam_unix(cron:session): session closed for user root
```
looking at the cron.service for previous days where it ran successfully:
Jun 12 02:00:01 DietPi CRON[687280]: (root) CMD (test -x /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.daily; })
Jun 12 02:00:25 DietPi systemd[1]: Stopping Regular background program processing daemon...
Jun 12 02:00:25 DietPi systemd[1]: cron.service: Succeeded.
Jun 12 02:00:25 DietPi systemd[1]: cron.service: Unit process 687279 (cron) remains running after unit stopped.
Jun 12 02:00:25 DietPi systemd[1]: cron.service: Unit process 687280 (dash) remains running after unit stopped.
Jun 12 02:00:25 DietPi systemd[1]: cron.service: Unit process 687281 (run-parts) remains running after unit stopped.
Jun 12 02:00:25 DietPi systemd[1]: cron.service: Unit process 687283 (dietpi) remains running after unit stopped.
Jun 12 02:00:25 DietPi systemd[1]: cron.service: Unit process 687985 (dietpi-backup) remains running after unit stopped.
Jun 12 02:00:25 DietPi systemd[1]: cron.service: Unit process 688000 (dietpi-services) remains running after unit stopped.
Jun 12 02:00:25 DietPi systemd[1]: cron.service: Unit process 688003 (systemctl) remains running after unit stopped.
Jun 12 02:00:25 DietPi systemd[1]: Stopped Regular background program processing daemon.
Jun 12 02:00:25 DietPi systemd[1]: cron.service: Consumed 25.778s CPU time.
Jun 12 02:02:54 DietPi systemd[1]: cron.service: Found left-over process 687279 (cron) in control group while starting unit. Ignoring.
Jun 12 02:02:54 DietPi systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 12 02:02:54 DietPi systemd[1]: cron.service: Found left-over process 687280 (dash) in control group while starting unit. Ignoring.
Jun 12 02:02:54 DietPi systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 12 02:02:54 DietPi systemd[1]: cron.service: Found left-over process 687281 (run-parts) in control group while starting unit. Ignoring.
Jun 12 02:02:54 DietPi systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 12 02:02:54 DietPi systemd[1]: cron.service: Found left-over process 687283 (dietpi) in control group while starting unit. Ignoring.
Jun 12 02:02:54 DietPi systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 12 02:02:54 DietPi systemd[1]: cron.service: Found left-over process 687985 (dietpi-backup) in control group while starting unit. Ignoring.
Jun 12 02:02:54 DietPi systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 12 02:02:54 DietPi systemd[1]: cron.service: Found left-over process 688645 (dietpi-services) in control group while starting unit. Ignoring.
Jun 12 02:02:54 DietPi systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 12 02:02:54 DietPi systemd[1]: cron.service: Found left-over process 688654 (systemctl) in control group while starting unit. Ignoring.
Jun 12 02:02:54 DietPi systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 12 02:02:54 DietPi systemd[1]: Started Regular background program processing daemon.
Jun 12 02:02:54 DietPi cron[688655]: (CRON) INFO (pidfile fd = 3)
Jun 12 02:02:54 DietPi cron[688655]: (CRON) INFO (Skipping @reboot jobs -- not system startup)
Jun 12 02:02:54 DietPi CRON[687279]: pam_unix(cron:session): session closed for user root
Jun 12 02:17:01 DietPi CRON[695567]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)```
Any guidance would be greatly appreciated