unable to update dietpi to latest version

Details:

Date | Fri Jul 12 19:40:13 BST 2024
Bug report | 6dbbd6b4-823d-4de3-b099-33ee20fb991d
DietPi version | v9.5.1 (MichaIng/master)
Image creator |
Pre-image |
Hardware | ROCK64 (aarch64) (ID=43)
Kernel version | Linux DietPi 6.1.63-current-rockchip64 #1 SMP PREEMPT Mon Nov 20 10:52:19 UTC 2023 aarch64 GNU/Linux
Distro | bullseye (ID=6)
Command | apt-get -y --with-new-pkgs upgrade
Exit code | 100
Software title | DietPi-Update
Steps to reproduce:
1. ...
2. ...
  Expected behaviour:
...
Actual behaviour:
...
Extra details:

...

Additional logs:


Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up exim4-config (4.94.2-7+deb11u3) ...
/usr/sbin/update-exim4.conf: 467: cannot create /dev/null: File exists
Invalid new configfile /var/lib/exim4/config.autogenerated.tmp, not installing 
/var/lib/exim4/config.autogenerated.tmp to /var/lib/exim4/config.autogenerated
dpkg: error processing package exim4-config (--configure):
installed exim4-config package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of exim4-base:
exim4-base depends on exim4-config (>= 4.94) | exim4-config-2; however:
Package exim4-config is not configured yet.
Package exim4-config-2 is not installed.
Package exim4-config which provides exim4-config-2 is not configured yet.

dpkg: error processing package exim4-base (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of exim4-daemon-light: exim4-daemon-light depends on exim4-base (>= 4.94.2); however: Package exim4-base is not configured yet.

dpkg: error processing package exim4-daemon-light (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: exim4-config exim4-base exim4-daemon-light E: Sub-process /usr/bin/dpkg returned an error code (1)



I am unable to update dietpi to latest version, due to exim4-config; exim4-base; exim-daemon-light upgrade error and 
/usr/bin/apt-key: 57: cannot create /dev/null: Permission denied

Thank you in advance

here is the output of: ls -l /dev/null

-rw-r--r-- 1 root root 0 Jul 12 21:06 /dev/null

Can you share the full update log:

cat /var/tmp/dietpi/logs/dietpi-update.log

And was this the very first dietpi-update attempt you did or did you retry it already?

root@DietPi:~# cat /var/tmp/dietpi/logs/dietpi-update.log

 DietPi-Update
─────────────────────────────────────────────────────
 Phase: Applying pre-patches

[      ] DietPi-Update | Downloading pre-patches/boot/dietpi/func/dietpi-globals                                                                                                                     : line 288: /dev/null: cannot overwrite existing file
[  OK  ] DietPi-Update | Downloading pre-patches
[      ] DietPi-Update | Applying execute permission/boot/dietpi/func/dietpi-glo                                                                                                                     bals: line 288: /dev/null: cannot overwrite existing file
[  OK  ] DietPi-Update | Applying execute permission
[  OK  ] DietPi-Update | Successfully applied pre-patches

 DietPi-Update
─────────────────────────────────────────────────────
 Phase: Upgrading APT packages

[ INFO ] DietPi-Update | APT update, please wait...
Hit:1 http://packages.azlux.fr/debian bookworm InRelease
Hit:2 http://ftp.de.debian.org/debian bullseye InRelease
Hit:3 http://ftp.de.debian.org/debian bullseye-updates InRelease
Hit:4 http://ftp.de.debian.org/debian bullseye-backports InRelease
Hit:5 https://download.mono-project.com/repo/debian buster InRelease
Hit:6 https://apt.sonarr.tv/debian buster InRelease
Hit:7 https://download.docker.com/linux/debian bullseye InRelease
Hit:8 https://dietpi.com/apt bullseye InRelease
Hit:9 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:10 https://repo.nextdns.io/deb stable InRelease
Reading package lists...
[  OK  ] DietPi-Update | APT update
[ INFO ] DietPi-Update | APT upgrade, please wait...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up exim4-config (4.94.2-7+deb11u3) ...
/usr/sbin/update-exim4.conf: 467: cannot create /dev/null: File exists
Invalid new configfile /var/lib/exim4/config.autogenerated.tmp, not installing
/var/lib/exim4/config.autogenerated.tmp to /var/lib/exim4/config.autogenerated
dpkg: error processing package exim4-config (--configure):
 installed exim4-config package post-installation script subprocess returned err                                                                                                                     or exit status 1
dpkg: dependency problems prevent configuration of exim4-base:
 exim4-base depends on exim4-config (>= 4.94) | exim4-config-2; however:
  Package exim4-config is not configured yet.
  Package exim4-config-2 is not installed.
  Package exim4-config which provides exim4-config-2 is not configured yet.

dpkg: error processing package exim4-base (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of exim4-daemon-light:
 exim4-daemon-light depends on exim4-base (>= 4.94.2); however:
  Package exim4-base is not configured yet.

dpkg: error processing package exim4-daemon-light (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 exim4-config
 exim4-base
 exim4-daemon-light
E: Sub-process /usr/bin/dpkg returned an error code (1)
[FAILED] DietPi-Update | Unable to continue, DietPi-Update will now terminate.

This is not the first try and I rebooted /tried many times

Do you have a backup you can restore from before the update? Or do you remember which DietPi version you originally upgraded from? I would like to see really all pre-patches and package upgrades applied, to be able to find the culprit.

However, to fix it:

sudo rm /dev/null
sudo mknod -m 0666 /dev/null c 1 3

I run the last two commands and dietpi-update , but it failed this is the new id 6dbbd6b4-823d-4de3-b099-33ee20fb991d

this is cat /var/tmp/dietpi/logs/dietpi-update.log

root@DietPi:~# cat /var/tmp/dietpi/logs/dietpi-update.log

 DietPi-Update
─────────────────────────────────────────────────────
 Phase: Applying pre-patches

[      ] DietPi-Update | Downloading pre-patches/boot/dietpi/func/dietpi-globals: line 288: /dev/null: cannot overwrite existing file
[  OK  ] DietPi-Update | Downloading pre-patches
[      ] DietPi-Update | Applying execute permission/boot/dietpi/func/dietpi-globals: line 288: /dev/null: cannot overwrite existing file
[  OK  ] DietPi-Update | Applying execute permission
[  OK  ] DietPi-Update | Successfully applied pre-patches

 DietPi-Update
─────────────────────────────────────────────────────
 Phase: Upgrading APT packages

[ INFO ] DietPi-Update | APT update, please wait...
Hit:1 https://dietpi.com/apt bullseye InRelease
Hit:2 http://packages.azlux.fr/debian bookworm InRelease
Hit:3 http://ftp.de.debian.org/debian bullseye InRelease
Hit:4 https://download.mono-project.com/repo/debian buster InRelease
Hit:5 https://deb.debian.org/debian-security bullseye-security InRelease
Get:6 http://ftp.de.debian.org/debian bullseye-updates InRelease [44.1 kB]
Hit:7 https://apt.sonarr.tv/debian buster InRelease
Hit:8 https://download.docker.com/linux/debian bullseye InRelease
gpgv: Signature made Tue Jul  9 19:43:33 2024 BST
gpgv:                using RSA key FFB3546A0FEE5516E659B6E31DF45FDB9C6CE851
gpgv: Good signature from "MichaIng <micha@dietpi.com>"
/usr/bin/apt-key: 57: cannot create /dev/null: Permission denied
Hit:9 https://repo.nextdns.io/deb stable InRelease
Get:10 http://ftp.de.debian.org/debian bullseye-backports InRelease [49.0 kB]
gpgv: Signature made Tue Jul  9 07:49:09 2024 BST
gpgv:                using RSA key 98B824A5FA7D3A10FDB225B7CA548A0A0312D8E6
gpgv: Good signature from "Azlux <github@azlux.fr>"
/usr/bin/apt-key: 57: cannot create /dev/null: Permission denied
gpgv: Signature made Sat Jun 29 11:27:34 2024 BST
gpgv:                using RSA key A7236886F3CCCAAD148A27F80E98404D386FA1D9
gpgv: Good signature from "Debian Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org>"
gpgv: Signature made Sat Jun 29 11:27:34 2024 BST
gpgv:                using RSA key 4CB50190207B4758A3F73A796ED0E7B82643E131
gpgv: Good signature from "Debian Archive Automatic Signing Key (12/bookworm) <ftpmaster@debian.org>"
gpgv: Signature made Sat Jun 29 11:31:04 2024 BST
gpgv:                using RSA key A4285295FC7B1A81600062A9605C66F00D6C9793
gpgv: Good signature from "Debian Stable Release Key (11/bullseye) <debian-release@lists.debian.org>"
/usr/bin/apt-key: 57: cannot create /dev/null: Permission denied
gpgv: Signature made Wed Jul 12 16:18:10 2023 BST
gpgv:                using RSA key 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
gpgv: Good signature from "Xamarin Public Jenkins (auto-signing) <releng@xamarin.com>"
/usr/bin/apt-key: 57: cannot create /dev/null: Permission denied
gpgv: Signature made Fri Jul 12 17:19:40 2024 BST
gpgv:                using RSA key 5237CEEEF212F3D51C74ABE0112695A0E562B32A
gpgv: Good signature from "Debian Security Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org>"
gpgv: Signature made Fri Jul 12 17:19:41 2024 BST
gpgv:                using RSA key ED541312A33F1128F10B1C6C54404762BBB6E853
gpgv: Good signature from "Debian Security Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org>"
/usr/bin/apt-key: 57: cannot create /dev/null: Permission denied
gpgv: Signature made Mon Mar 13 07:13:33 2023 GMT
gpgv:                using RSA key EBFF6B99D9B78493
gpgv: Can't check signature: No public key
gpgv: Signature made Mon Mar 13 07:13:33 2023 GMT
gpgv:                using RSA key 1F4F90DE2A9B4BF8
gpgv: Good signature from "Sonarr <hello@sonarr.tv>"
/usr/bin/apt-key: 57: cannot create /dev/null: Permission denied
Sub-process apt-key returned an error code (2)gpgv: Signature made Fri Jul 12 10:28:03 2024 BST
gpgv:                using RSA key 7EA0A9C3F273FCD8
gpgv: Good signature from "Docker Release (CE deb) <docker@docker.com>"
/usr/bin/apt-key: 57: cannot create /dev/null: Permission denied
gpgv: Signature made Fri Jul 12 21:17:53 2024 BST
gpgv:                using RSA key A7236886F3CCCAAD148A27F80E98404D386FA1D9
gpgv: Good signature from "Debian Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org>"
gpgv: Signature made Fri Jul 12 21:18:27 2024 BST
gpgv:                using RSA key 4CB50190207B4758A3F73A796ED0E7B82643E131
gpgv: Good signature from "Debian Archive Automatic Signing Key (12/bookworm) <ftpmaster@debian.org>"
/usr/bin/apt-key: 57: cannot create /dev/null: Permission denied
gpgv: Signature made Fri May 24 12:35:32 2024 BST
gpgv:                using RSA key AD34842BF3C80F656A833F66467A7CCC8ACFA0B7
gpgv: Good signature from "NextDNS <team@nextdns.io>"
/usr/bin/apt-key: 57: cannot create /dev/null: Permission denied
gpgv: Signature made Fri Jul 12 21:18:15 2024 BST
gpgv:                using RSA key A7236886F3CCCAAD148A27F80E98404D386FA1D9
gpgv: Good signature from "Debian Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org>"
gpgv: Signature made Fri Jul 12 21:18:46 2024 BST
gpgv:                using RSA key 4CB50190207B4758A3F73A796ED0E7B82643E131
gpgv: Good signature from "Debian Archive Automatic Signing Key (12/bookworm) <ftpmaster@debian.org>"
/usr/bin/apt-key: 57: cannot create /dev/null: Permission denied
Fetched 93.0 kB in 8s (11.1 kB/s)
Reading package lists...
[  OK  ] DietPi-Update | APT update
[ INFO ] DietPi-Update | APT upgrade, please wait...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up exim4-config (4.94.2-7+deb11u3) ...
/usr/sbin/update-exim4.conf: 467: cannot create /dev/null: File exists
Invalid new configfile /var/lib/exim4/config.autogenerated.tmp, not installing
/var/lib/exim4/config.autogenerated.tmp to /var/lib/exim4/config.autogenerated
dpkg: error processing package exim4-config (--configure):
 installed exim4-config package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of exim4-base:
 exim4-base depends on exim4-config (>= 4.94) | exim4-config-2; however:
  Package exim4-config is not configured yet.
  Package exim4-config-2 is not installed.
  Package exim4-config which provides exim4-config-2 is not configured yet.

dpkg: error processing package exim4-base (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of exim4-daemon-light:
 exim4-daemon-light depends on exim4-base (>= 4.94.2); however:
  Package exim4-base is not configured yet.

dpkg: error processing package exim4-daemon-light (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 exim4-config
 exim4-base
 exim4-daemon-light
E: Sub-process /usr/bin/dpkg returned an error code (1)
[FAILED] DietPi-Update | APT upgrade
 - Command: apt-get -y --with-new-pkgs upgrade
[ INFO ] DietPi-BugReport | Generating informative command outputs, please wait...
[ INFO ] DietPi-BugReport | cp /tmp/G_EXEC_ERROR_REPORT G_EXEC_ERROR_REPORT, please wait...
[  OK  ] DietPi-BugReport | cp /tmp/G_EXEC_ERROR_REPORT G_EXEC_ERROR_REPORT
[      ] DietPi-BugReport | Packing upload archive/boot/dietpi/func/dietpi-globals: line 288: /dev/null: cannot overwrite existing file
[  OK  ] DietPi-BugReport | Packing upload archive
[      ] DietPi-BugReport | Sending bug report/boot/dietpi/func/dietpi-globals: line 288: /dev/null: cannot overwrite existing file
[  OK  ] DietPi-BugReport | Sending bug report
[  OK  ] DietPi-BugReport | Your bug report has been successfully uploaded.
- Reference code: 6dbbd6b4-823d-4de3-b099-33ee20fb991d

Please file a related bug report at GitHub or our forum:
- https://github.com/MichaIng/DietPi/issues
- https://dietpi.com/forum/c/troubleshooting/10

The uploaded file will be removed automatically after 48 hours or when your issue has been solved. Additionally you can remove it by running:
- dietpi-bugreport -1

Press any key to continue...root@DietPi:~#

I have backups, but how to do?

dietpi-backup list

 Please select the backup from the archive you wish to restore:                                                       
                                      │                                                                                                                                                   │
                                      │                                        1 2024-05-13 19:27:01.000000000 +0100                                         │
                                      │                                        2 2024-06-04 11:13:22.215547183 +0100                                         │
                                      │                                        3 2024-05-13 19:27:01.000000000 +0100                                         │
                                      │                                        4 2023-08-21 20:47:29.073313629 +0100                                         │

What is the one that you suggest I restore?

Okay your last output shows the broken /dev/null before dietpi-update even started to do anything. Now I also see the capped lines in your first paste, which contains the same error message already from dietpi-globals, when it tried to download the the pre-patches. The dietpi-update script has not changed since v9.0, so it is unlikely to be the culprit.

Can you try the commands again and check the node right afterwards?

sudo rm /dev/null
sudo mknod -m 0666 /dev/null c 1 3
ls -l /dev/null

Then wait for a while, check again, and run only the update check (without the actual update), before checking agian:

sleep 10
ls -l /dev/null
dietpi-update 2
ls -l /dev/null

So far to assure dietpi-update until this part does not cause the issue.

The first commands

root@DietPi:~# sudo rm /dev/null    
root@DietPi:~# sudo mknod -m 0666 /dev/null c 1 3
root@DietPi:~# ls -l /dev/null       
            crw-rw-rw- 1 root root 1, 3 Jul 12 22:46 /dev/null
root@DietPi:~#

I waited 1 minute And here it is

root@DietPi:~# sleep 10                          
root@DietPi:~# ls -l /dev/null 
            crw-rw-rw- 1 root root 1, 3 Jul 12 22:46 /dev/null

root@DietPi:~# dietpi-update 2
                                                  DietPi-Update
─────────────────────────────────────────────────────
 Mode: Checking for available DietPi update

[  OK  ] DietPi-Update | Checking IPv4 network connectivity                                       
[  OK  ] DietPi-Update | Checking DNS resolver   
[ INFO ] DietPi-Update | Getting latest version from: https://raw.githubusercontent.com/MichaIng/DietPi/master/.update/version
[  OK  ] DietPi-Update | Got valid latest version: 9.6.1
[  OK  ] DietPi-Update | Update available:       
[ INFO ] DietPi-Update | Current version : v9.5.1
[ INFO ] DietPi-Update | Latest version  : v9.6.1
root@DietPi:~# ls -l /dev/null
                   crw-rw-rw- 1 root root 1, 3 Jul 12 22:46 /dev/null
root@DietPi:~#

Okay so far so good, probably it is one of the stopped services:

ls -l /dev/null
dietpi-services stop
ls -l /dev/null

root@DietPi:~ ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 12 22:46 /dev/null
root@DietPi:~ dietpi-services stop
DietPi-Services
─────────────────────────────────────────────────────
 Mode: stop 

[  OK  ] DietPi-Services | stop : cron
[  OK  ] DietPi-Services | stop : docker
[  OK  ] DietPi-Services | stop : radarr
[  OK  ] DietPi-Services | stop : sonarr
[  OK  ] DietPi-Services | stop : medusa
[  OK  ] DietPi-Services | stop : qbittorrent
[  OK  ] DietPi-Services | stop : minidlna
[  OK  ] DietPi-Services | stop : nginx
[  OK  ] DietPi-Services | stop : smbd
[  OK  ] DietPi-Services | stop : nmbd
[  OK  ] DietPi-Services | stop : avahi-daemon
root@DietPi:~ ls -l /dev/null   
crw-rw-rw- 1 root root 1, 3 Jul 12 22:46 /dev/null
root@DietPi:~

Hi I launched dietpi-update and it passed @MichaIng 🥇

Here is after reboot

Linux DietPi 6.6.34-current-rockchip64 #2 SMP PREEMPT Sun Jun 16 
11:47:49 UTC 2024 aarch64

The programs included with the Debian GNU/Linux system are free s
oftware;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Jul 12 23:10:41 2024 from 192.168.1.200
 ─────────────────────────────────────────────────────
 DietPi v9.6.1 : 23:11 - Fri 07/12/24
 ─────────────────────────────────────────────────────
 - Device model : ROCK64 (aarch64)
 - CPU temp : WARNING: 75 °C / 167 °F : Reducing the life of your device
 - LAN IP : 192.168.1.159 (eth0)
 - MOTD : DietPi v9.6 is here. Check out all changes:
          https://dietpi.com/docs/releases/v9_6/
 ─────────────────────────────────────────────────────

 DietPi Team     : https://github.com/MichaIng/DietPi#the-dietpi-project-team
 Patreon Legends : Chris Gelatt, ADSB.im
 Website         : https://dietpi.com/ | https://twitter.com/DietPi_
 Contribute      : https://dietpi.com/contribute.html
 Web Hosting by  : https://myvirtualserver.com

 dietpi-launcher : All the DietPi programs in one place
 dietpi-config   : Feature rich configuration tool for your device
 dietpi-software : Select optimised software for installation
 htop            : Resource monitor
 cpu             : Shows CPU information and stats

root@DietPi:~# cat /var/tmp/dietpi/logs/dietpi-update.log
DietPi-Update                                                                        
─────────────────────────────────────────────────────
Phase: Applying pre-patches
[  OK  ] DietPi-Update | Applying execute permission
[  OK  ] DietPi-Update | Successfully applied pre-patches                                                                                                                      DietPi-Update                                                                         ─────────────────────────────────────────────────────
Phase: Upgrading APT packages                                                         
[ INFO ] DietPi-Update | APT update, please wait...
Hit:1 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:2 https://dietpi.com/apt bullseye InRelease
Hit:3 https://repo.nextdns.io/deb stable InRelease
Hit:4 http://packages.azlux.fr/debian bookworm InRelease
Hit:5 https://download.docker.com/linux/debian bullseye InRelease
Hit:6 https://apt.sonarr.tv/debian buster InRelease
Hit:7 https://download.mono-project.com/repo/debian buster InRelease
Hit:8 http://ftp.de.debian.org/debian bullseye InRelease
Hit:9 http://ftp.de.debian.org/debian bullseye-updates InRelease
Hit:10 http://ftp.de.debian.org/debian bullseye-backports InRelease
Reading package lists...
[  OK  ] DietPi-Update | APT update
[ INFO ] DietPi-Update | APT upgrade, please wait...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up exim4-config (4.94.2-7+deb11u3) ...
Setting up exim4-base (4.94.2-7+deb11u3) ...
exim4-base.service is a disabled or a static unit not running, not starting it.
Setting up exim4-daemon-light (4.94.2-7+deb11u3) ...
[  OK  ] DietPi-Update | APT upgrade                                                                                                                                           DietPi-Update
─────────────────────────────────────────────────────
 Phase: Installing new DietPi code
[  OK  ] DietPi-Set_software | Downloading current dietpi.txt[  OK  ] verify_dietpi.txt  | Completed
[  OK  ] DietPi-Update | systemctl daemon-reload                                                                                                                               DietPi-Update
─────────────────────────────────────────────────────
 Phase: Applying incremental patches

[ INFO ] DietPi-Update | Current version : v9.5.1
[  OK  ] DietPi-Set_software | eval echo 'deb https://dietpi.com/apt all rock64' >> /etc/apt/sources.list.d/dietpi.list                                                       [  OK  ] apt-mirror dietpi | Completed
[ INFO ] DietPi-Patch | APT update, please wait...
Hit:1 http://packages.azlux.fr/debian bookworm InRelease
Hit:2 http://ftp.de.debian.org/debian bullseye InRelease
Hit:3 http://ftp.de.debian.org/debian bullseye-updates InRelease
Hit:4 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:5 https://apt.sonarr.tv/debian buster InRelease
Hit:6 http://ftp.de.debian.org/debian bullseye-backports InRelease
Hit:7 https://download.mono-project.com/repo/debian buster InRelease
Hit:8 https://download.docker.com/linux/debian bullseye InRelease
Hit:9 https://dietpi.com/apt bullseye InRelease
Get:10 https://dietpi.com/apt all InRelease [25.3 kB]
Hit:11 https://repo.nextdns.io/deb stable InRelease
Get:12 https://dietpi.com/apt all/rock64 all Packages [396 B]
Get:13 https://dietpi.com/apt all/rock64 arm64 Packages [1140 B]
Fetched 26.8 kB in 7s (3792 B/s)
Reading package lists...
[  OK  ] DietPi-Patch | APT update
[ INFO ] DietPi-Patch | APT upgrade, please wait...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  armbian-firmware linux-dtb-current-rockchip64 linux-image-current-rockchip64
  linux-u-boot-rock64-current
4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 132 MB of archives.
After this operation, 51.0 MB of additional disk space will be used.
Get:1 https://dietpi.com/apt all/rock64 all armbian-firmware all 24.8.0-trunk-dietpi1 [91.2 MB]
Get:2 https://dietpi.com/apt all/rock64 arm64 linux-dtb-current-rockchip64 arm64 24.8.0-trunk-dietpi1 [477 kB]
Get:3 https://dietpi.com/apt all/rock64 arm64 linux-image-current-rockchip64 arm64 24.8.0-trunk-dietpi1 [39.6 MB]
Get:4 https://dietpi.com/apt all/rock64 arm64 linux-u-boot-rock64-current arm64 24.8.0-trunk-dietpi1 [321 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 132 MB in 1min 3s (2078 kB/s)
(Reading database ... 31039 files and directories currently installed.)
Preparing to unpack .../armbian-firmware_24.8.0-trunk-dietpi1_all.deb ...
Unpacking armbian-firmware (24.8.0-trunk-dietpi1) over (23.11.1) ...
Preparing to unpack .../linux-dtb-current-rockchip64_24.8.0-trunk-dietpi1_arm64.deb ...Armbian 'linux-dtb-current-rockchip64' for '6.6.34-current-rockchip64': 'preinst' starting.
Armbian 'linux-dtb-current-rockchip64' for '6.6.34-current-rockchip64': 'preinst' finishing.
Unpacking linux-dtb-current-rockchip64 (24.8.0-trunk-dietpi1) over (23.11.1) ...
Preparing to unpack .../linux-image-current-rockchip64_24.8.0-trunk-dietpi1_arm64.deb ...
Armbian 'linux-image-current-rockchip64' for '6.1.63-current-rockchip64': 'prerm' starting.
Armbian 'linux-image-current-rockchip64' for '6.1.63-current-rockchip64': 'prerm' finishing.
Armbian 'linux-image-current-rockchip64' for '6.6.34-current-rockchip64': 'preinst' starting.
Armbian 'linux-image-current-rockchip64' for '6.6.34-current-rockchip64': 'preinst' finishing.
Unpacking linux-image-current-rockchip64 (24.8.0-trunk-dietpi1) over (23.11.1) ...
Armbian 'linux-image-current-rockchip64' for '6.1.63-current-rockchip64': 'postrm' starting.
Removing obsolete initramfs images
Armbian 'linux-image-current-rockchip64' for '6.1.63-current-rockchip64': 'postrm' finishing.
Preparing to unpack .../linux-u-boot-rock64-current_24.8.0-trunk-dietpi1_arm64.deb ...
Unpacking linux-u-boot-rock64-current (24.8.0-trunk-dietpi1) over (23.11.1) ...
Setting up linux-image-current-rockchip64 (24.8.0-trunk-dietpi1) ...
Armbian 'linux-image-current-rockchip64' for '6.6.34-current-rockchip64': 'postinst' starting.
Removing obsolete initramfs images
removed '/boot/initrd.img-6.1.63-current-rockchip64'
removed '/boot/uInitrd-6.1.63-current-rockchip64'
update-initramfs: Generating /boot/initrd.img-6.6.34-current-rockchip64
update-initramfs: Converting to U-Boot format
Image Name:   uInitrd
Created:      Fri Jul 12 23:07:47 2024
Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
Data Size:    13135194 Bytes = 12827.34 KiB = 12.53 MiB
Load Address: 00000000
Entry Point:  00000000
'/boot/uInitrd' -> 'uInitrd-6.6.34-current-rockchip64'
Armbian: update last-installed kernel symlink to 'Image'...
'/boot/Image' -> 'vmlinuz-6.6.34-current-rockchip64'
Armbian: Debian compat: linux-update-symlinks install 6.6.34-current-rockchip64 boot/vmlinuz-6.6.34-current-rockchip64
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.6.34-current-rockchip64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.6.34-current-rockchip64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.6.34-current-rockchip64
I: /initrd.img is now a symlink to boot/initrd.img-6.6.34-current-rockchip64
Armbian 'linux-image-current-rockchip64' for '6.6.34-current-rockchip64': 'postinst' finishing.
Setting up linux-u-boot-rock64-current (24.8.0-trunk-dietpi1) ...
Armbian 'uboot-rock64-current' for '2022.07-Se092-P6552-H8c72-Vedc0-B2e16-R448a': 'postinst' starting.
Armbian 'uboot-rock64-current' for '2022.07-Se092-P6552-H8c72-Vedc0-B2e16-R448a': 'postinst' finishing.
Setting up linux-dtb-current-rockchip64 (24.8.0-trunk-dietpi1) ...
Armbian 'linux-dtb-current-rockchip64' for '6.6.34-current-rockchip64': 'postinst' starting.
Armbian: DTB: symlinking /boot/dtb to /boot/dtb-6.6.34-current-rockchip64...
'dtb' -> 'dtb-6.6.34-current-rockchip64'
Armbian 'linux-dtb-current-rockchip64' for '6.6.34-current-rockchip64': 'postinst' finishing.
Setting up armbian-firmware (24.8.0-trunk-dietpi1) ...
[  OK  ] DietPi-Patch | APT upgrade
[  OK  ] DietPi-Patch | rmdir --ignore-fail-on-non-empty /etc/systemd/system/ifup@.service.d                                                                                  [  OK  ] DietPi-Patch | Patched to DietPi v9.6
[ INFO ] DietPi-Update | APT autopurge, please wait...
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[  OK  ] DietPi-Update | systemctl daemon-reload
[  OK  ] DietPi-Update | Incremental patching to v9.6.1 completed
[ INFO ] DietPi-Update | Checking for new available live patches
root@DietPi:~#
root@DietPi:~# ls -l /dev/null
-rw-r--r-- 1 root root 0 Jul 12 23:11 /dev/null      
root@DietPi:~# stat /dev/null
File: /dev/null               Size: 0               Blocks: 0          IO Block: 4096   regular empty file
Device: 5h/5dInode: 375         Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2024-07-12 23:10:50.340945456 +0100
Modify: 2024-07-12 23:11:57.188945488 +0100
Change: 2024-07-12 23:11:57.188945488 +0100
 Birth: 2024-07-12 23:09:46.484945425 +0100
root@DietPi:~#

The /dev/null file however is again broken. More importantly, it is broken now, after the reboot. Since /dev is recreated from scratch, this means that not the DietPi update, but something else, after the reboot, broke it. Another test:

ls -l /dev/null
dietpi-services restart
ls -l /dev/null

Linux DietPi 6.6.34-current-rockchip64 #2 SMP PREEMPT Sun Jun 16 
11:47:49 UTC 2024 aarch64

The programs included with the Debian GNU/Linux system are free s
oftware;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Jul 12 23:25:47 2024 from 192.168.1.200
 ─────────────────────────────────────────────────────
 DietPi v9.6.1 : 23:29 - Fri 07/12/24
 ─────────────────────────────────────────────────────
 - Device model : ROCK64 (aarch64)
 - CPU temp : 62 °C / 143 °F : Running hot, not recommended
 - LAN IP : 192.168.1.159 (eth0)
 - MOTD : DietPi v9.6 is here. Check out all changes:
          https://dietpi.com/docs/releases/v9_6/
 ─────────────────────────────────────────────────────

 DietPi Team     : https://github.com/MichaIng/DietPi#the-dietpi-project-team
 Patreon Legends : Chris Gelatt, ADSB.im
 Website         : https://dietpi.com/ | https://twitter.com/DietPi_
 Contribute      : https://dietpi.com/contribute.html
 Web Hosting by  : https://myvirtualserver.com

 dietpi-launcher : All the DietPi programs in one place
 dietpi-config   : Feature rich configuration tool for your device
 dietpi-software : Select optimised software for installation
 htop            : Resource monitor
 cpu             : Shows CPU information and stats

root@DietPi:~# ls -l /dev/null        -rw-r--r-- 1 root root 0 Jul 12 23:29 /dev/null
root@DietPi:~# dietpi-services restart                                       DietPi-Services
─────────────────────────────────────────────────────
 Mode: restart 

[      ] Di/boot/dietpi/func/dietpi-globals: line 288: /dev/null: cannot overwrite existing file
[  OK  ] DietPi-Services | restart : avahi-daemon
[  /boot/dietpi/func/dietpi-globals: line 288: /dev/null: cannot overwrite existing file
[  OK  ] DietPi-Services | restart : nmbd
[  /boot/dietpi/func/dietpi-globals: line 288: /dev/null: cannot overwrite existing file
[  OK  ] DietPi-Services | restart : smbd
[   /boot/dietpi/func/dietpi-globals: line 288: /dev/null: cannot overwrite existing file
[  OK  ] DietPi-Services | restart : nginx
[      /boot/dietpi/func/dietpi-globals: line 288: /dev/null: cannot overwrite existing file
[  OK  ] DietPi-Services | restart : minidlna
[ INFO ] DietPi-Services | skip : qbittorrent (disabled)
[ INFO ] DietPi-Services | skip : medusa (disabled)
[ INFO ] DietPi-Services | skip : sonarr (disabled)
[ INFO ] DietPi-Services | skip : radarr (disabled)
[  OK  ] DietPi-Services | restart : docker                                 
[  /boot/dietpi/func/dietpi-globals: line 288: /dev/null: cannot overwrite existing file                          
[  OK  ] DietPi-Services | restart : cron                                   
root@DietPi:~# ls -l /dev/null
        -rw-r--r-- 1 root root 0 Jul 12 23:29 /dev/null
root@DietPi:~#

Ah sorry, the node needs to be repaired first, of course:

rm /dev/null
mknod -m 0666 /dev/null c 1 3
ls -l /dev/null
dietpi-services restart
ls -l /dev/null

root@DietPi:~# rm /dev/null
root@DietPi:~# mknod -m 0666 /dev/null c 1 3
root@DietPi:~# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 12 23:38 /dev/null
root@DietPi:~# dietpi-services restart
                                                      DietPi-Services
───────────────────────────────────────────────────── Mode: restart 

[  OK  ] DietPi-Services | restart : avahi-daemon    [  OK  ] DietPi-Services | restart : nmbd            [  OK  ] DietPi-Services | restart : smbd            [  OK  ] DietPi-Services | restart : nginx           [  OK  ] DietPi-Services | restart : minidlna        [ INFO ] DietPi-Services | skip : qbittorrent (disabled)
[ INFO ] DietPi-Services | skip : medusa (disabled)  [ INFO ] DietPi-Services | skip : sonarr (disabled)  [ INFO ] DietPi-Services | skip : radarr (disabled)  [  OK  ] DietPi-Services | restart : docker          [  OK  ] DietPi-Services | restart : cron           
root@DietPi:~# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 12 23:38 /dev/null
root@DietPi:~#

Okay, service restarts did not break it. Can you do another reboot and see if it is broken again? If so, let's check journal logs whether we can see related errors from some point on:

journalctl

root@DietPi:~# ls -l /dev/null        
-rw-r--r-- 1 root root 0 Jul 13 06:21 
/dev/null
root@DietPi:~# uptime                                 06:23:01 up  6:35,  2 users,  load average: 0.48, 0.59, 0.62
root@DietPi:~# journalctl | grep null                Jul 13 01:25:02 DietPi systemd[1]: /dev/null is not a device.
Jul 13 01:25:02 DietPi systemd[1]: /dev/null is not a device.
Jul 13 01:25:02 DietPi systemd[1]: /dev/null is not a device.
Jul 13 01:25:02 DietPi systemd[1]: /dev/null is not a device.
Jul 13 01:25:02 DietPi systemd[1]: /dev/null is not a device.
root@DietPi:~#

checkgw.sh)
Jul 13 01:25:02 DietPi CRON[15220]: (root) CMD (test -x /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.daily; })
Jul 13 01:25:02 DietPi systemd[1]: /dev/null is not a device.
Jul 13 01:25:02 DietPi systemd[1]: Starting Network Time Synchronization...
Jul 13 01:25:02 DietPi systemd[15237]: systemd-timesyncd.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev: Invalid argument
Jul 13 01:25:02 DietPi systemd[15237]: systemd-timesyncd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-timesyncd: Invalid argument
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=226/NAMESPACE
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Jul 13 01:25:02 DietPi systemd[1]: Failed to start Network Time Synchronization.
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 1.
Jul 13 01:25:02 DietPi systemd[1]: Stopped Network Time Synchronization.
Jul 13 01:25:02 DietPi systemd[1]: /dev/null is not a device.
Jul 13 01:25:02 DietPi systemd[1]: Starting Network Time Synchronization...
Jul 13 01:25:02 DietPi systemd[15242]: systemd-timesyncd.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev: Invalid argument
Jul 13 01:25:02 DietPi systemd[15242]: systemd-timesyncd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-timesyncd: Invalid argument
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=226/NAMESPACE
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Jul 13 01:25:02 DietPi systemd[1]: Failed to start Network Time Synchronization.
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 2.
Jul 13 01:25:02 DietPi systemd[1]: Stopped Network Time Synchronization.
Jul 13 01:25:02 DietPi systemd[1]: /dev/null is not a device.
Jul 13 01:25:02 DietPi systemd[1]: Starting Network Time Synchronization...
Jul 13 01:25:02 DietPi systemd[15248]: systemd-timesyncd.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev: Invalid argument
Jul 13 01:25:02 DietPi systemd[15248]: systemd-timesyncd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-timesyncd: Invalid argument
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=226/NAMESPACE
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Jul 13 01:25:02 DietPi systemd[1]: Failed to start Network Time Synchronization.
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 3.
Jul 13 01:25:02 DietPi systemd[1]: Stopped Network Time Synchronization.
Jul 13 01:25:02 DietPi systemd[1]: /dev/null is not a device.
Jul 13 01:25:02 DietPi systemd[1]: Starting Network Time Synchronization...
Jul 13 01:25:02 DietPi systemd[15252]: systemd-timesyncd.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev: Invalid argument
Jul 13 01:25:02 DietPi systemd[15252]: systemd-timesyncd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-timesyncd: Invalid argument
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=226/NAMESPACE
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Jul 13 01:25:02 DietPi systemd[1]: Failed to start Network Time Synchronization.
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 4.
Jul 13 01:25:02 DietPi systemd[1]: Stopped Network Time Synchronization.
Jul 13 01:25:02 DietPi systemd[1]: /dev/null is not a device.
Jul 13 01:25:02 DietPi systemd[1]: Starting Network Time Synchronization...
Jul 13 01:25:02 DietPi systemd[15260]: systemd-timesyncd.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev: Invalid argument
Jul 13 01:25:02 DietPi systemd[15260]: systemd-timesyncd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-timesyncd: Invalid argument
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=226/NAMESPACE
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Jul 13 01:25:02 DietPi systemd[1]: Failed to start Network Time Synchronization.
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 5.
Jul 13 01:25:02 DietPi systemd[1]: Stopped Network Time Synchronization.
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Jul 13 01:25:02 DietPi systemd[1]: Failed to start Network Time Synchronization.
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Jul 13 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Jul 13 01:25:02 DietPi systemd[1]: Failed to start Network Time Synchronization.
Jul 13 01:25:12 DietPi CRON[15219]: pam_unix(cron:session): session closed for user root
Jul 13 01:25:35 DietPi CRON[15218]: pam_unix(cron:session): session closed for user root

It self rebooted when I was asleep, because of cron job ( checkgw.sh) I wrote if no internet is detected, because it froze after 20 days of uptime wih no reason that I could found.

After reboot

root@DietPi:~# ls -l /dev/null        -
rw-r--r-- 1 root root 0 Jul 13 17:01 /dev/null
root@DietPi:~# journalctl | grep null 
root@DietPi:~#

The daily cron job throws this error, but we don't know yet whether it also causes is, or whether it is done at boot only. Can you try this:

rm /dev/null
mknod -m 0666 /dev/null c 1 3
cd /
run-parts --report /etc/cron.hourly
ls -l /dev/null
run-parts --report /etc/cron.daily
ls -l /dev/null

The daily cron job might trigger a dietpi-sync and/or dietpi-backup, just in case you configures either to be done daily.

root@DietPi:~# rm /dev/null
root@DietPi:~# mknod -m 0666 /dev/null c 1 3
root@DietPi:~# cd /
root@DietPi:/# run-parts --report /etc/cron.hourly
root@DietPi:/# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 13 18:51 /dev/null
root@DietPi:/# run-parts --report /etc/cron.daily

root@DietPi:/# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 13 18:51 /dev/null
root@DietPi:/#

This is the setting that I changed to 2

https://www.reddit.com/r/dietpi/s/fJpMbtLuUY

root@DietPi:/#

root@DietPi:/# cat /boot/dietpi.txt | grep CONFIG_CHECK_APT_UPDATES
CONFIG_CHECK_APT_UPDATES=2
root@DietPi:/# cat /boot/dietpi.txt | grep CONFIG_CHECK_DIETPI_UPDATES
CONFIG_CHECK_DIETPI_UPDATES=1
root@DietPi:/#

Since the daily cron job did not cause it, the daily update check obviously does not cause the issue. So it seems to be something at boot then. Let's try some potential candidates:

ls -d /dev/null
systemctl start systemd-tmpfiles-setup-dev-early
ls -d /dev/null
systemctl start systemd-tmpfiles-setup-dev
ls -d /dev/null
systemctl start systemd-tmpfiles-setup
ls -d /dev/null
systemctl start systemd-tmpfiles-clean
ls -d /dev/null

root@DietPi:~# ls -d /dev/null                                                         /dev/null
root@DietPi:~# systemctl start systemd-tmpfiles-setup-dev-early
Failed to start systemd-tmpfiles-setup-dev-early.service: Unit systemd-tmpfiles-setup-dev-early.service not found.
root@DietPi:~# ls -d /dev/null
/dev/null
root@DietPi:~# systemctl start systemd-tmpfiles-setup-dev
root@DietPi:~# ls -d /dev/null
/dev/null
root@DietPi:~# systemctl start systemd-tmpfiles-setup
root@DietPi:~# ls -d /dev/null
/dev/null
root@DietPi:~# systemctl start systemd-tmpfiles-clean
root@DietPi:~# ls -d /dev/null
/dev/null
root@DietPi:~#

Oh typo, ls -l of course, to see the details of the file:

ls -l /dev/null
systemctl start systemd-tmpfiles-setup-dev-early
ls -l /dev/null
systemctl start systemd-tmpfiles-setup-dev
ls -l /dev/null
systemctl start systemd-tmpfiles-setup
ls -l /dev/null
systemctl start systemd-tmpfiles-clean
ls -l /dev/null

The first service seems to not exist yet on Bookworm, but only from Trixie on.

root@DietPi:~# ls -l /dev/null                                                         

crw-rw-rw- 1 root root 1, 3 Jul 13 18:51 /dev/null
root@DietPi:~# systemctl start systemd-tmpfiles-setup-dev-early
Failed to start systemd-tmpfiles-setup-dev-early.service: Unit systemd-tmpfiles-setup-dev-early.service not found.
root@DietPi:~# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 13 18:51 /dev/null
root@DietPi:~# systemctl start systemd-tmpfiles-setup-dev
root@DietPi:~# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 13 18:51 /dev/null
root@DietPi:~# systemctl start systemd-tmpfiles-setup
root@DietPi:~# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 13 18:51 /dev/null
root@DietPi:~# systemctl start systemd-tmpfiles-clean
root@DietPi:~# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 13 18:51 /dev/null
root@DietPi:~#
root@DietPi:~# echo $G_DISTRO_NAME

       bullseye

I just recognised that the setup jobs "remain after exit", so they need to be restarted to do something. Let's test this and some more:

ls -l /dev/null
systemctl restart systemd-tmpfiles-setup-dev
ls -l /dev/null
systemctl restart systemd-tmpfiles-setup
ls -l /dev/null
systemctl restart dietpi-ramlog
ls -l /dev/null
systemctl restart dietpi-preboot
ls -l /dev/null
systemctl restart dietpi-postboot
ls -l /dev/null
source /etc/bashrc.d/dietpi.bash
ls -l /dev/null

root@DietPi:~# ls -l /dev/null 
crw-rw-rw- 1 root root 1, 3 Jul 13 18:51 /dev/null            
root@DietPi:~# systemctl restart dietpi-ramlog
root@DietPi:~# ls -l /dev/null   
crw-rw-rw- 1 root root 1, 3 Jul 13 18:51 /dev/null             
root@DietPi:~# systemctl restart dietpi-preboot    
root@DietPi:~# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 13 18:51 /dev/null             
root@DietPi:~# systemctl restart dietpi-postboot   
root@DietPi:~# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 13 18:51 /dev/null             
root@DietPi:~# source /etc/bashrc.d/dietpi.bash
─────────────────────────────────────────────────────
DietPi v9.6.1 : 21:25 - Sat 07/13/24                          
─────────────────────────────────────────────────────
 - Device model : ROCK64 (aarch64)
 - CPU temp : 60 °C / 140 °F : Running hot, not recommended
 - LAN IP : 192.168.1.159 (eth0)
 - MOTD : DietPi v9.6 is here. Check out all changes:
          https://dietpi.com/docs/releases/v9_6/
 ─────────────────────────────────────────────────────

 DietPi Team     : https://github.com/MichaIng/DietPi#the-dietpi-project-team
 Patreon Legends : Chris Gelatt, ADSB.im
 Website         : https://dietpi.com/ | https://twitter.com/DietPi_
 Contribute      : https://dietpi.com/contribute.html
 Web Hosting by  : https://myvirtualserver.com

 dietpi-launcher : All the DietPi programs in one place
 dietpi-config   : Feature rich configuration tool for your device
 dietpi-software : Select optimised software for installation
 htop            : Resource monitor
 cpu             : Shows CPU information and stats

root@DietPi:~# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 13 18:51 /dev/null
root@DietPi:~#

I Just rebooted Intentionally


root@DietPi:~# ls -l /dev/null                                                         

-rw-r--r-- 1 root root 0 Jul 13 21:35 /dev/null
root@DietPi:~#

Did you restart the first to as well?

rm /dev/null
mknod -m 0666 /dev/null c 1 3
systemctl restart systemd-tmpfiles-setup-dev
ls -l /dev/null
systemctl restart systemd-tmpfiles-setup
ls -l /dev/null

I intentionally re-added them, since preciously it was just start, which is a no-op.

Yed and I restarted my box

root@DietPi:~# rm /dev/null                   
root@DietPi:~# mknod -m 0666 /dev/null c 1 3
root@DietPi:~# systemctl restart systemd-tmpfiles-setup-dev
root@DietPi:~# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 13 21:46 /dev/null
root@DietPi:~# systemctl restart systemd-tmpfiles-setup
Failed to restart systemd-tmpfiles-setup.service: Operation refused, unit systemd-tmpfi
les-setup.service may be requested by dependency only (it is configured to refuse manua
l start/stop).
See system logs and 'systemctl status systemd-tmpfiles-setup.service' for details.
root@DietPi:~# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 13 21:46 /dev/null
root@DietPi:~#

root@DietPi:~# systemctl status systemd-tmpfiles-setup.service       ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
     Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static)
     Active: active (exited) since Sat 2024-07-13 21:30:49 BST; 17min ago
       Docs: man:tmpfiles.d(5)
             man:systemd-tmpfiles(8)
    Process: 308 ExecStart=systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=0/SUCCESS)
   Main PID: 308 (code=exited, status=0/SUCCESS)
        CPU: 142ms

Jul 13 21:30:48 DietPi systemd[1]: Starting Create Volatile Files and Directories...
Jul 13 21:30:49 DietPi systemd[1]: Finished Create Volatile Files and Directories.
root@DietPi:~#

I wonder whether there is a better way to find the culprit than testing each and every service. There is a loggedfs: https://github.com/rflament/loggedfs

Let's try first to narrow it down, and at the same time check which DietPi script we can use to setup the loggedfs:

sed -i '1i\ls -l /dev/null | logger -t devnull' /boot/dietpi/func/dietpi-ramlog
sed -i '1i\ls -l /dev/null | logger -t devnull' /boot/dietpi/preboot
sed -i '1i\ls -l /dev/null | logger -t devnull' /boot/dietpi/postboot
reboot

Then after reboot:

journalctl -t devnull

EDIT: Ah shit, I just tested it, and this does not work for such a node:

root@micha:/tmp# loggedfs -l ~/log.txt /dev/null
root@micha:/tmp# echo test > /dev/null
bash: /dev/null: Permission denied
root@micha:/tmp# l /dev/null
ls: cannot access '/dev/null': Input/output error

But the above is still good to check at which point of boot the node is broken.

root@DietPi:~# journalctl -t devnull             
-- Journal begins at Sat 2024-07-13 21:57:36 BST, ends at Sat 2024-07-13 22:01:44 BST.
--
Jul 13 21:57:38 DietPi devnull[380]: crw-rw-rw- 1 root root 1, 3 Jan  1  1970 /dev/null
root@DietPi:~# ls -l /dev/null
-rw-r--r-- 1 root root 0 Jul 13 22:01 /dev/null
root@DietPi:~#

Hmm, are you sure you ran all three commands above? There should be 3 log entries, not just one 🤔. To check:

mawk 'NR==1' /boot/dietpi/func/dietpi-ramlog /boot/dietpi/preboot /boot/dietpi/postboot


rrent-rockchip64] (local build)
Jul 13 21:57:39 DietPi smartd[370]: Copyrig
ht (C) 2002-20, Bruce Allen, Christian Fran
ke, www.smartmontools.org
Jul 13 21:57:39 DietPi kernel: Adding 26214
0k swap on /dev/zram0.  Priority:100 extent
s:1 across:262140k SS
Jul 13 21:57:39 DietPi smartd[370]: Opened
configuration file /etc/smartd.conf
Jul 13 21:57:39 DietPi smartd[370]: Drive:
DEVICESCAN, implied '-a' Directive on line
21 of file /etc/smartd.conf
Jul 13 21:57:39 DietPi smartd[370]: Configu
ration file /etc/smartd.conf was parsed, fo
und DEVICESCAN, scanning devices
Jul 13 21:57:39 DietPi smartd[370]: In the 
system's table of devices NO devices found 
to scan
Jul 13 21:57:39 DietPi smartd[370]: Monitor
ing 0 ATA/SATA, 0 SCSI/SAS and 0 NVMe devic
es
Jul 13 21:57:39 DietPi kernel: cfg80211: Lo
ading compiled-in X.509 certificates for re
gulatory database
Jul 13 21:57:39 DietPi kernel: Loaded X.509
 cert 'sforshee: 00b28ddf47aef9cea7'
Jul 13 21:57:39 DietPi kernel: Loaded X.509
 cert 'wens: 61c038651aabdcf94bd0ac7ff06c72
48db18c600'
Jul 13 21:57:39 DietPi kernel: brcmfmac: F1
 signature read @0x18000000=0x16034334
Jul 13 21:57:39 DietPi systemd[1]: Started
Self Monitoring and Reporting Technology (S
MART) Daemon.
Jul 13 21:57:39 DietPi systemd[1]: Finished
 Linux zramswap setup.
Jul 13 21:57:39 DietPi systemd[1]: Found de
vice /sys/subsystem/net/devices/eth0.
Jul 13 21:57:39 DietPi kernel: brcmfmac: br
cmf_fw_alloc_request: using brcm/brcmfmac43
34-sdio for chip BCM4334/3
Jul 13 21:57:39 DietPi kernel: usbcore: reg
istered new interface driver brcmfmac
Jul 13 21:57:39 DietPi kernel: brcmfmac mmc
1:0001:1: Direct firmware load for brcm/brc
mfmac4334-sdio.rockchip,rk3318-box.bin fail
ed with error -2
Jul 13 21:57:39 DietPi kernel: brcmfmac mmc
1:0001:1: Direct firmware load for brcm/brc
mfmac4334-sdio.clm_blob failed with error -
2
Jul 13 21:57:39 DietPi systemd[1]: Reached
target Sound Card.
Jul 13 21:57:39 DietPi systemd[1]: Listenin
g on Load/Save RF Kill Switch Status /dev/r
fkill Watch.
Jul 13 21:57:39 DietPi systemd[1]: Finished
 Helper to synchronize boot up for ifupdown
.
Jul 13 21:57:39 DietPi kernel: brcmfmac: br
cmf_c_process_clm_blob: no clm_blob availab
le (err=-2), device may have limited channe
ls available
Jul 13 21:57:39 DietPi kernel: brcmfmac: br
cmf_c_process_txcap_blob: no txcap_blob ava
ilable (err=-2)
Jul 13 21:57:39 DietPi kernel: brcmfmac: br
cmf_c_preinit_dcmds: Firmware: BCM4334/3 wl
0: Jul 24 2019 12:58:36 version 6.10.191 (T
OB) (r) FWID 01-b049404e
Jul 13 21:57:39 DietPi systemd[1]: Starting
 Load/Save RF Kill Switch Status...
Jul 13 21:57:39 DietPi systemd-udevd[320]:
Using default interface naming scheme 'v247
'.
Jul 13 21:57:39 DietPi systemd[1]: Started
Load/Save RF Kill Switch Status.
Jul 13 21:57:39 DietPi avahi-daemon[351]: S
erver startup complete. Host name is DietPi
.local. Local service cookie is 1212989546.
Jul 13 21:57:40 DietPi systemd[1]: Found de
vice /sys/subsystem/net/devices/wlan0.
Jul 13 21:57:40 DietPi systemd[1]: Finished
 DietPi-Arr_to_RAM.
Jul 13 21:57:40 DietPi systemd[1]: Starting
 DietPi-PreBoot...
Jul 13 21:57:40 DietPi systemd[463]: dietpi
-preboot.service: Failed to execute /boot/d
ietpi/preboot: Exec format error
Jul 13 21:57:40 DietPi systemd[463]: dietpi
-preboot.service: Failed at step EXEC spawn
ing /boot/dietpi/preboot: Exec format error
Jul 13 21:57:40 DietPi systemd[1]: dietpi-p
reboot.service: Main process exited, code=e
xited, status=203/EXEC
Jul 13 21:57:40 DietPi systemd[1]: dietpi-p
reboot.service: Failed with result 'exit-co
de'.
Jul 13 21:57:40 DietPi systemd[1]: Failed t
o start DietPi-PreBoot.
Jul 13 21:57:40 DietPi systemd[1]: Reached
target Network (Pre).
Jul 13 21:57:40 DietPi systemd[1]: Starting
 ifup for eth0...
Jul 13 21:57:40 DietPi systemd[1]: Starting
 ifup for wlan0...
Jul 13 21:57:40 DietPi systemd[1]: Starting
 Raise network interfaces...
Jul 13 21:57:41 DietPi kernel: warning: `iw
config' uses wireless extensions which will
 stop working for Wi-Fi 7 hardware; use nl8
0211
Jul 13 21:57:41 DietPi avahi-daemon[351]: J
oining mDNS multicast group on interface wl
an0.IPv4 with address 192.168.42.1.
Jul 13 21:57:41 DietPi avahi-daemon[351]: N
ew relevant interface wlan0.IPv4 for mDNS.
Jul 13 21:57:41 DietPi avahi-daemon[351]: R
egistering new address record for 192.168.4
2.1 on wlan0.IPv4.
Jul 13 21:57:41 DietPi dhclient[519]: Inter
net Systems Consortium DHCP Client 4.4.1
Jul 13 21:57:41 DietPi ifup[519]: Internet
Systems Consortium DHCP Client 4.4.1
Jul 13 21:57:41 DietPi ifup[519]: Copyright
 2004-2018 Internet Systems Consortium.
Jul 13 21:57:41 DietPi ifup[519]: All right
s reserved.
Jul 13 21:57:41 DietPi ifup[519]: For info,
 please visit https://www.isc.org/software/
dhcp/
Jul 13 21:57:41 DietPi dhclient[519]: Copyr
ight 2004-2018 Internet Systems Consortium.
Jul 13 21:57:41 DietPi dhclient[519]: All r
ights reserved.
Jul 13 21:57:41 DietPi dhclient[519]: For i
nfo, please visit https://www.isc.org/softw
are/dhcp/
Jul 13 21:57:41 DietPi dhclient[519]:
Jul 13 21:57:41 DietPi kernel: rk_gmac-dwma
c ff550000.ethernet eth0: Register MEM_TYPE
_PAGE_POOL RxQ-0
Jul 13 21:57:41 DietPi kernel: rk_gmac-dwma
c ff550000.ethernet eth0: PHY [stmmac-1:00]
 driver [Rockchip integrated EPHY] (irq=POL
L)
Jul 13 21:57:41 DietPi kernel: rk_gmac-dwma
c ff550000.ethernet eth0: No Safety Feature
s support found
Jul 13 21:57:41 DietPi kernel: rk_gmac-dwma
c ff550000.ethernet eth0: PTP not supported
 by HW
Jul 13 21:57:41 DietPi kernel: rk_gmac-dwma
c ff550000.ethernet eth0: configuring for p
hy/rmii link mode
Jul 13 21:57:41 DietPi systemd[1]: Finished
 Raise network interfaces.
Jul 13 21:57:41 DietPi dhclient[519]: Liste
ning on LPF/eth0/0e:d9:a9:fd:c6:9e
Jul 13 21:57:41 DietPi ifup[519]: Listening
 on LPF/eth0/0e:d9:a9:fd:c6:9e
Jul 13 21:57:41 DietPi ifup[519]: Sending o
n   LPF/eth0/0e:d9:a9:fd:c6:9e
Jul 13 21:57:41 DietPi ifup[519]: Sending o
n   Socket/fallback
Jul 13 21:57:41 DietPi ifup[519]: DHCPDISCO
VER on eth0 to 255.255.255.255 port 67 inte
rval 5
Jul 13 21:57:41 DietPi dhclient[519]: Sendi
ng on   LPF/eth0/0e:d9:a9:fd:c6:9e
Jul 13 21:57:41 DietPi dhclient[519]: Sendi
ng on   Socket/fallback
Jul 13 21:57:41 DietPi dhclient[519]: DHCPD
ISCOVER on eth0 to 255.255.255.255 port 67
interval 5
Jul 13 21:57:41 DietPi systemd[1]: Finished
 ifup for wlan0.
Jul 13 21:57:43 DietPi kernel: rk_gmac-dwma
c ff550000.ethernet eth0: Link is Up - 100M
bps/Full - flow control off
Jul 13 21:57:44 DietPi prepare-for-mergerfs
[594]: Warning: Stopping docker.service, bu
t it can still be activated by:
Jul 13 21:57:44 DietPi prepare-for-mergerfs
[594]:   docker.socket
Jul 13 21:57:44 DietPi prepare-for-mergerfs
[595]: umount: /mnt/ecfd67f7-9081-4973-952c
-b4d8ce6ec817: not mounted.
Jul 13 21:57:44 DietPi systemd[1]: systemd-
rfkill.service: Succeeded.
Jul 13 21:57:46 DietPi dhclient[519]: DHCPD
ISCOVER on eth0 to 255.255.255.255 port 67
interval 13
Jul 13 21:57:46 DietPi ifup[519]: DHCPDISCO
VER on eth0 to 255.255.255.255 port 67 inte
rval 13
Jul 13 21:57:46 DietPi dhclient[519]: DHCPO
FFER of 192.168.1.159 from 192.168.1.1
Jul 13 21:57:46 DietPi ifup[519]: DHCPOFFER
 of 192.168.1.159 from 192.168.1.1
Jul 13 21:57:46 DietPi ifup[519]: DHCPREQUE
ST for 192.168.1.159 on eth0 to 255.255.255
.255 port 67
Jul 13 21:57:46 DietPi dhclient[519]: DHCPR
EQUEST for 192.168.1.159 on eth0 to 255.255
.255.255 port 67
Jul 13 21:57:46 DietPi dhclient[519]: DHCPA
CK of 192.168.1.159 from 192.168.1.1
Jul 13 21:57:46 DietPi ifup[519]: DHCPACK o
f 192.168.1.159 from 192.168.1.1
Jul 13 21:57:46 DietPi avahi-daemon[351]: J
oining mDNS multicast group on interface et
h0.IPv4 with address 192.168.1.159.
Jul 13 21:57:46 DietPi avahi-daemon[351]: N
ew relevant interface eth0.IPv4 for mDNS.Jul 13 21:57:46 DietPi avahi-daemon[351]: R
egistering new address record for 192.168.1
.159 on eth0.IPv4.
Jul 13 21:57:46 DietPi systemd[1]: Stopping
 Network Time Synchronization...
Jul 13 21:57:46 DietPi systemd[1]: systemd-
timesyncd.service: Succeeded.
Jul 13 21:57:46 DietPi systemd[1]: Stopped
Network Time Synchronization.
Jul 13 21:57:46 DietPi systemd[1]: Starting
 Network Time Synchronization...
Jul 13 21:57:46 DietPi systemd[1]: Started
Network Time Synchronization.
Jul 13 21:57:46 DietPi dhclient[519]: bound
 to 192.168.1.159 -- renewal in 133819 seco
nds.
Jul 13 21:57:46 DietPi ifup[519]: bound to
192.168.1.159 -- renewal in 133819 seconds.
Jul 13 21:57:47 DietPi systemd[1]: Finished
 ifup for eth0.
Jul 13 21:57:47 DietPi systemd[1]: Reached
target Network.
Jul 13 21:57:47 DietPi systemd[1]: Reached
target Network is Online.
Jul 13 21:58:08 DietPi systemd-timesyncd[64
1]: Initial synchronization to time server
176.9.44.212:123 (0.debian.pool.ntp.org).Jul 13 21:58:08 DietPi systemd[1]: Started
DietPi-PostBoot.
Jul 13 21:58:08 DietPi systemd[1]: Starting
 LSB: exim Mail Transport Agent...
Jul 13 21:58:08 DietPi systemd[1]: Starting
 LSB: DHCP server...
Jul 13 21:58:08 DietPi systemd[1]: Started
ReadyMedia (DietPi).
Jul 13 21:58:08 DietPi systemd[1]: Starting
 A high performance web server and a revers
e proxy server...
Jul 13 21:58:08 DietPi systemd[1]: Starting
 Samba NMB Daemon...
Jul 13 21:58:08 DietPi systemd[1]: Starting
 OpenVPN service...
Jul 13 21:58:08 DietPi systemd[1]: Conditio
n check resulted in fast remote file copy p
rogram daemon being skipped.
Jul 13 21:58:09 DietPi systemd[1]: Starting
 OpenBSD Secure Shell server...
Jul 13 21:58:09 DietPi systemd[1]: Starting
 Permit User Sessions...
Jul 13 21:58:09 DietPi systemd[1]: Finished
 OpenVPN service.
Jul 13 21:58:09 DietPi nginx[673]: nginx: [
alert] could not open error log file: open(
) "/var/log/nginx/error.log" failed (2: No
such file or directory)
Jul 13 21:58:09 DietPi systemd[1]: Finished
 Permit User Sessions.
Jul 13 21:58:09 DietPi systemd[1]: Started
Getty on tty1.
Jul 13 21:58:09 DietPi systemd[1]: Started
Serial Getty on ttyS2.
Jul 13 21:58:09 DietPi systemd[1]: Reached
target Login Prompts.
Jul 13 21:58:09 DietPi isc-dhcp-server[671]
: Launching IPv4 server only.
Jul 13 21:58:09 DietPi nginx[673]: 2024/07/
13 21:58:09 [emerg] 673#673: open() "/var/l
og/nginx/error.log" failed (2: No such file
 or directory)
Jul 13 21:58:09 DietPi nginx[673]: nginx: c
onfiguration file /etc/nginx/nginx.conf tes
t failed
Jul 13 21:58:09 DietPi systemd[1]: nginx.se
rvice: Control process exited, code=exited,
 status=1/FAILURE
Jul 13 21:58:09 DietPi systemd[1]: nginx.se
rvice: Failed with result 'exit-code'.
Jul 13 21:58:09 DietPi systemd[1]: Failed t
o start A high performance web server and a
 reverse proxy server.
Jul 13 21:58:09 DietPi dhcpd[738]: Wrote 16
 leases to leases file.
Jul 13 21:58:09 DietPi dhcpd[738]: Server s
tarting service.
Jul 13 21:58:09 DietPi sshd[785]: Server li
stening on 0.0.0.0 port 22.
Jul 13 21:58:09 DietPi sshd[785]: Server li
stening on :: port 22.
Jul 13 21:58:09 DietPi systemd[1]: Started
OpenBSD Secure Shell server.
Jul 13 21:58:10 DietPi exim4[670]: Starting
 MTA:
Jul 13 21:58:10 DietPi exim4[946]: 2024-07-
13 21:58:10 Cannot open main log file "/var
/log/exim4/mainlog": Permission denied: eui
d=0 egid=115
Jul 13 21:58:10 DietPi exim4[946]: 2024-07-
13 21:58:10 Warning: No server certificate
defined; will use a selfsigned one.
Jul 13 21:58:10 DietPi exim4[946]:  Suggest
ed action: either install a certificate or
change tls_advertise_hosts option
Jul 13 21:58:10 DietPi exim4[946]: 2024-07-
13 21:58:10 Cannot open main log file "/var
/log/exim4/mainlog": Permission denied: eui
d=0 egid=115
Jul 13 21:58:10 DietPi exim4[946]: exim: co
uld not open panic log - aborting: see mess
age(s) above
Jul 13 21:58:10 DietPi exim[946]: [1\2] 202
4-07-13 21:58:10 Warning: No server certifi
cate defined; will use a selfsigned one.
Jul 13 21:58:10 DietPi exim[946]: [2/2]  Su
ggested action: either install a certificat
e or change tls_advertise_hosts option
Jul 13 21:58:10 DietPi exim[946]: 2024-07-1
3 21:58:10 Cannot open main log file "/var/
log/exim4/mainlog": Permission denied: euid
=0 egid=115
Jul 13 21:58:10 DietPi exim[946]: exim: cou
ld not open panic log - aborting: see messa
ge(s) above
Jul 13 21:58:10 DietPi systemd[1]: exim4.se
rvice: Control process exited, code=exited,
 status=1/FAILURE
Jul 13 21:58:10 DietPi systemd[1]: exim4.se
rvice: Failed with result 'exit-code'.
Jul 13 21:58:10 DietPi systemd[1]: Failed t
o start LSB: exim Mail Transport Agent.
Jul 13 21:58:10 DietPi systemd[1]: exim4.se
rvice: Consumed 1.127s CPU time.
Jul 13 21:58:11 DietPi nmbd[676]: directory
_create_or_exist: mkdir failed on directory
 /var/log/samba/cores: No such file or dire
ctory
Jul 13 21:58:11 DietPi nmbd[676]: Failed to
 create /var/log/samba/cores for user 0 wit
h mode 0700
Jul 13 21:58:11 DietPi nmbd[676]: Unable to
 setup corepath for nmbd: No such file or d
irectory
Jul 13 21:58:11 DietPi nmbd[676]: [2024/07/
13 21:58:11,  0] ../../lib/util/debug.c:110
4(reopen_one_log)
Jul 13 21:58:11 DietPi nmbd[676]:   reopen_
one_log: Unable to open new log file '/var/
log/samba/log.nmbd': No such file or direct
ory
Jul 13 21:58:11 DietPi nmbd[676]: [2024/07/
13 21:58:11.004970,  0] ../../lib/util/debu
g.c:1104(reopen_one_log)
Jul 13 21:58:11 DietPi nmbd[676]:   reopen_
one_log: Unable to open new log file '/var/
log/samba/log.nmbd': No such file or direct
ory
Jul 13 21:58:11 DietPi nmbd[676]: [2024/07/
13 21:58:11.005202,  0] ../../source3/nmbd/
nmbd.c:960(main)
Jul 13 21:58:11 DietPi nmbd[676]:   nmbd ve
rsion 4.13.13-Debian started.
Jul 13 21:58:11 DietPi nmbd[676]:   Copyrig
ht Andrew Tridgell and the Samba Team 1992-
2020
Jul 13 21:58:11 DietPi nmbd[676]: [2024/07/
13 21:58:11.017144,  0] ../../lib/util/debu
g.c:1104(reopen_one_log)
Jul 13 21:58:11 DietPi nmbd[676]:   reopen_
one_log: Unable to open new log file '/var/
log/samba/log.': No such file or directory
Jul 13 21:58:11 DietPi nmbd[676]: [2024/07/
13 21:58:11.029955,  0] ../../lib/util/debu
g.c:1104(reopen_one_log)
Jul 13 21:58:11 DietPi nmbd[676]:   reopen_
one_log: Unable to open new log file '/var/
log/samba/log.nmbd': No such file or direct
ory
Jul 13 21:58:11 DietPi systemd[1]: Started
Samba NMB Daemon.
Jul 13 21:58:11 DietPi systemd[1]: Starting
 Samba SMB Daemon...
Jul 13 21:58:11 DietPi kernel: FS-Cache: Lo
aded
Jul 13 21:58:11 DietPi kernel: Key type cif
s.spnego registered
Jul 13 21:58:11 DietPi kernel: Key type cif
s.idmap registered
Jul 13 21:58:11 DietPi kernel: Use of the l
ess secure dialect vers=1.0 is not recommen
ded unless required for access to very old 
servers
Jul 13 21:58:11 DietPi kernel: CIFS: VFS: U
se of the less secure dialect vers=1.0 is n
ot recommended unless required for access t
o very old servers
Jul 13 21:58:11 DietPi kernel: CIFS: enabli
ng forceuid mount option implicitly because
 uid= option is specified
Jul 13 21:58:11 DietPi kernel: CIFS: enabli
ng forcegid mount option implicitly because
 gid= option is specified
Jul 13 21:58:11 DietPi kernel: CIFS: Attemp
ting to mount //192.168.1.1/Seagate_Expansi
on_1_e7c1
Jul 13 21:58:11 DietPi isc-dhcp-server[671]
: Starting ISC DHCPv4 server: dhcpd.
Jul 13 21:58:11 DietPi systemd[1]: Started
LSB: DHCP server.
Jul 13 21:58:12 DietPi smbd[958]: [2024/07/
13 21:58:12,  0] ../../lib/util/debug.c:110
4(reopen_one_log)
Jul 13 21:58:12 DietPi smbd[958]:   reopen_
one_log: Unable to open new log file '/var/
log/samba/log.smbd': No such file or direct
ory
Jul 13 21:58:12 DietPi smbd[958]: [2024/07/
13 21:58:12,  0] ../../lib/util/util.c:364(
directory_create_or_exist)
Jul 13 21:58:12 DietPi smbd[958]:   directo
ry_create_or_exist: mkdir failed on directo
ry /var/log/samba/cores: No such file or di
rectory
Jul 13 21:58:12 DietPi smbd[958]: [2024/07/
13 21:58:12,  0] ../../source3/lib/dumpcore
.c:59(get_default_corepath)
Jul 13 21:58:12 DietPi smbd[958]:   Failed
to create /var/log/samba/cores for user 0 w
ith mode 0700
Jul 13 21:58:12 DietPi smbd[958]: [2024/07/
13 21:58:12,  0] ../../source3/lib/dumpcore
.c:256(dump_core_setup)
Jul 13 21:58:12 DietPi smbd[958]:   Unable
to setup corepath for smbd: No such file or
 directory
Jul 13 21:58:12 DietPi smbd[958]: [2024/07/
13 21:58:12.297035,  0] ../../lib/util/debu
g.c:1104(reopen_one_log)
Jul 13 21:58:12 DietPi smbd[958]:   reopen_
one_log: Unable to open new log file '/var/
log/samba/log.smbd': No such file or direct
ory
Jul 13 21:58:12 DietPi smbd[958]: [2024/07/
13 21:58:12.297190,  0] ../../source3/smbd/
server.c:1784(main)
Jul 13 21:58:12 DietPi smbd[958]:   smbd ve
rsion 4.13.13-Debian started.
Jul 13 21:58:12 DietPi smbd[958]:   Copyrig
ht Andrew Tridgell and the Samba Team 1992-
2020
Jul 13 21:58:12 DietPi smbd[958]: [2024/07/
13 21:58:12.329808,  0] ../../lib/util/debu
g.c:1104(reopen_one_log)
Jul 13 21:58:12 DietPi smbd[958]:   reopen_
one_log: Unable to open new log file '/var/
log/samba/log.smbd': No such file or direct
ory
Jul 13 21:58:12 DietPi smbd[958]: [2024/07/
13 21:58:12.334186,  0] ../../lib/util/debu
g.c:1104(reopen_one_log)
Jul 13 21:58:12 DietPi smbd[958]:   reopen_
one_log: Unable to open new log file '/var/
log/samba/log.smbd': No such file or direct
ory
Jul 13 21:58:12 DietPi smbd[958]: [2024/07/
13 21:58:12.335275,  0] ../../lib/util/debu
g.c:1104(reopen_one_log)
Jul 13 21:58:12 DietPi smbd[958]:   reopen_
one_log: Unable to open new log file '/var/
log/samba/log.smbd': No such file or direct
ory
Jul 13 21:58:12 DietPi systemd[1]: Started
Samba SMB Daemon.
Jul 13 21:58:12 DietPi systemd[1]: Reached
target Multi-User System.
Jul 13 21:58:13 DietPi systemd[669]: dietpi
-postboot.service: Failed to execute /boot/
dietpi/postboot: Exec format error
Jul 13 21:58:13 DietPi systemd[669]: dietpi
-postboot.service: Failed at step EXEC spaw
ning /boot/dietpi/postboot: Exec format err
or
Jul 13 21:58:13 DietPi systemd[1]: dietpi-p
ostboot.service: Main process exited, code=
exited, status=203/EXEC
Jul 13 21:58:13 DietPi systemd[1]: dietpi-p
ostboot.service: Failed with result 'exit-c
ode'.
Jul 13 21:58:13 DietPi login[685]: pam_unix
(login:session): session opened for user ro
ot(uid=0) by LOGIN(uid=0)
Jul 13 21:58:14 DietPi login[987]: ROOT LOG
IN  on '/dev/tty1'

 mawk 'NR==1' /boot/dietpi/func/dietpi-ramlog /boot/dietpi/preboot /boot/dietpi/postboot                     ls -l /dev/null | logger -t devnull

Ah shit, I added them wrong. New attempt 😄:

sed -i '/logger -t devnull/d' /boot/dietpi/func/dietpi-ramlog /boot/dietpi/preboot /boot/dietpi/postboot
sed -i '1a\ls -l /dev/null | logger -t devnull' /boot/dietpi/func/dietpi-ramlog
sed -i '1a\ls -l /dev/null | logger -t devnull' /boot/dietpi/preboot
sed -i '1a\ls -l /dev/null | logger -t devnull' /boot/dietpi/postboot
reboot

The first line is the shebang, which needs to stay there, so the logger command needs to be added after the first line, not before/as first line.

And then again after reboot:

journalctl -t devnull
ls -l /dev/null

root@DietPi:~# journalctl -t devnull
-- Journal begins at Sat 2024-07-13 22:27:50 BST, ends at Sat 2024-07-13 22:30:42 BST.
--
Jul 13 22:27:52 DietPi devnull[385]: crw-rw-rw- 1 root root 1, 3 Jan  1  1970 /dev/null
Jul 13 22:27:54 DietPi devnull[467]: crw-rw-rw- 1 root root 1, 3 Jul 13 22:27 /dev/null
Jul 13 22:28:30 DietPi devnull[1018]: crw-rw-rw- 1 root root 1, 3 Jul 13 22:27 /dev/nul
l
root@DietPi:~# ls -l /dev/null    -rw-r--r-- 1 root root 0 Jul 13 22:30 /dev/null
root@DietPi:~#
root@DietPi:~# 
root@DietPi:~# mawk 'NR==1' /boot/dietpi/func/dietpi-ramlog /boot/dietpi/preboot /boot/dietpi/postboot                  #!/bin/bash

Okay, so everything is fine at least until dietpi-postboot runs, which is pretty much the end of the boot process. One thing it does, which we did not test yet and which is spawned into background:

rm /dev/null
mknod -m 0666 /dev/null c 1 3
/boot/dietpi/func/run_ntpd
ls -l /dev/null
/boot/dietpi/func/run_ntpd 1
ls -l /dev/null

If the node is still fine, then let's check journalctl for all services/targets which start or finish after dietpi-postboot:

journalctl -e

Try to locate "Started dietpi-postboot.service - DietPi-PostBoot" and copy&paste everything afterwards, or just the whole output.


e\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
Jul 13 22:30:08 DietPi containerd[2330]: time="2024-07-13T22:30:08.250868131+01:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.pause\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
Jul 13 22:30:08 DietPi systemd[1]: run-docker-runtime\x2drunc-moby-7934e2f0a86672b887ae0db87be3f8e88bc93a841f53ee12f76503e0e87a169b-runc.X8sHrS.mount: Succeeded.
Jul 13 22:30:08 DietPi systemd[1]: run-docker-runtime\x2drunc-moby-bf712e7e93b0713bd8f45b227358fa7d190eb2db5ba3cae47f628c1e9050521e-runc.DeCPZN.mount: Succeeded.
Jul 13 22:30:08 DietPi systemd[1]: Started libcontainer container 19e05cb20ae3d81d32540ca33fd8a375cf9488d2ecf20b8f4ee8a73c15e30f40.
Jul 13 22:30:08 DietPi systemd[1]: Started libcontainer container 2d9237116c213a24cb3942813a4e934c705cbde084ffd32481dbc3d15d9303fa.
Jul 13 22:30:08 DietPi systemd[1]: Started libcontainer container 7934e2f0a86672b887ae0db87be3f8e88bc93a841f53ee12f76503e0e87a169b.
Jul 13 22:30:08 DietPi systemd[1]: Started libcontainer container 7969df7e88684d75e925d07b23de13bf71753e1bd932c4f771b5d79da97ea466.
Jul 13 22:30:08 DietPi systemd[1]: Started libcontainer container bf712e7e93b0713bd8f45b227358fa7d190eb2db5ba3cae47f628c1e9050521e.
Jul 13 22:30:08 DietPi systemd[1]: Started libcontainer container d617c70ddbfe72b4bc08c60270e0edbd2e5d9ae9b3cc96c6831cbc1fd13dac1f.
Jul 13 22:30:08 DietPi systemd[1]: Started libcontainer container 1e224e6202391eedab3de95751d3fef38a0608673fdb9d4e3d094e47652ea4c4.
Jul 13 22:30:08 DietPi systemd[1]: Started libcontainer container 66790425f50381d5e5689b8dc88b12facb0ab3488785a8b793b2c75ed61f6762.
Jul 13 22:30:08 DietPi systemd[1]: Started libcontainer container e950683ceee48511271dfdcc24e11eb2602bf24b67f6d4ead246d64db0516438.
Jul 13 22:30:10 DietPi kernel: eth0: renamed from veth0982d3a
Jul 13 22:30:10 DietPi kernel: br-9e0addaff28a: port 1(vethc12d78e) entered blocking state
Jul 13 22:30:10 DietPi kernel: br-9e0addaff28a: port 1(vethc12d78e) entered forwarding state
Jul 13 22:30:10 DietPi kernel: eth0: renamed from veth1888c11
Jul 13 22:30:10 DietPi kernel: docker0: port 2(veth3c1e828) entered blocking state
Jul 13 22:30:10 DietPi kernel: docker0: port 2(veth3c1e828) entered forwarding state
Jul 13 22:30:10 DietPi kernel: eth0: renamed from veth03b2882
Jul 13 22:30:10 DietPi kernel: docker0: port 1(veth46eba98) entered blocking state
Jul 13 22:30:10 DietPi kernel: docker0: port 1(veth46eba98) entered forwarding state
Jul 13 22:30:10 DietPi kernel: eth0: renamed from vethba69b35
Jul 13 22:30:10 DietPi kernel: br-4bf64785e6d8: port 1(vethc9c8a33) entered blocking state
Jul 13 22:30:10 DietPi kernel: br-4bf64785e6d8: port 1(vethc9c8a33) entered forwarding state
Jul 13 22:30:10 DietPi kernel: eth0: renamed from veth9ec4c10
Jul 13 22:30:10 DietPi kernel: br-9e0addaff28a: port 2(veth536e26f) entered blocking state
Jul 13 22:30:10 DietPi kernel: br-9e0addaff28a: port 2(veth536e26f) entered forwarding state
Jul 13 22:30:10 DietPi kernel: eth0: renamed from veth3a3f80a
Jul 13 22:30:10 DietPi kernel: eth0: renamed from veth84bc187
Jul 13 22:30:10 DietPi kernel: br-8614d213917a: port 1(vethc152e5d) entered blocking state
Jul 13 22:30:10 DietPi kernel: br-8614d213917a: port 1(vethc152e5d) entered forwarding state
Jul 13 22:30:10 DietPi kernel: br-33c970648b25: port 1(veth3fbea98) entered blocking state
Jul 13 22:30:10 DietPi kernel: br-33c970648b25: port 1(veth3fbea98) entered forwarding state
Jul 13 22:30:10 DietPi kernel: eth0: renamed from veth8348064
Jul 13 22:30:10 DietPi 1e224e620239[2294]: s6-rc: info: service s6rc-oneshot-runner: starting
Jul 13 22:30:11 DietPi kernel: br-ed29ca25003b: port 1(veth2c7f56a) entered blocking state
Jul 13 22:30:11 DietPi kernel: br-ed29ca25003b: port 1(veth2c7f56a) entered forwarding state
Jul 13 22:30:11 DietPi 1e224e620239[2294]: s6-rc: info: service s6rc-oneshot-runner successfully started
Jul 13 22:30:11 DietPi 1e224e620239[2294]: s6-rc: info: service fix-attrs: starting
Jul 13 22:30:11 DietPi CRON[2813]: pam_unix(cron:session): session closed for user root
Jul 13 22:30:11 DietPi 1e224e620239[2294]: s6-rc: info: service fix-attrs successfully started
Jul 13 22:30:11 DietPi 1e224e620239[2294]: s6-rc: info: service legacy-cont-init: starting
Jul 13 22:30:11 DietPi 1e224e620239[2294]: s6-rc: info: service legacy-cont-init successfully started
Jul 13 22:30:11 DietPi 1e224e620239[2294]: s6-rc: info: service legacy-services: starting
Jul 13 22:30:11 DietPi 1e224e620239[2294]: services-up: info: copying legacy longrun home-assistant (no readiness notification)
Jul 13 22:30:12 DietPi 2d9237116c21[2294]: 1:C 13 Jul 2024 21:30:12.498 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
Jul 13 22:30:12 DietPi 2d9237116c21[2294]: 1:C 13 Jul 2024 21:30:12.512 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Jul 13 22:30:12 DietPi 2d9237116c21[2294]: 1:C 13 Jul 2024 21:30:12.512 * Redis version=7.2.1, bits=64, commit=00000000, modified=0, pid=1, just started
Jul 13 22:30:12 DietPi 2d9237116c21[2294]: 1:C 13 Jul 2024 21:30:12.512 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
Jul 13 22:30:12 DietPi 2d9237116c21[2294]: 1:M 13 Jul 2024 21:30:12.519 * monotonic clock: POSIX clock_gettime
Jul 13 22:30:12 DietPi 2d9237116c21[2294]: 1:M 13 Jul 2024 21:30:12.527 * Running mode=standalone, port=6379.
Jul 13 22:30:12 DietPi 2d9237116c21[2294]: 1:M 13 Jul 2024 21:30:12.531 * Server initialized
Jul 13 22:30:12 DietPi 2d9237116c21[2294]: 1:M 13 Jul 2024 21:30:12.595 * Loading RDB produced by version 7.2.1
Jul 13 22:30:12 DietPi 2d9237116c21[2294]: 1:M 13 Jul 2024 21:30:12.595 * RDB age 1970 seconds
Jul 13 22:30:12 DietPi 2d9237116c21[2294]: 1:M 13 Jul 2024 21:30:12.595 * RDB memory usage when created 0.88 Mb
Jul 13 22:30:12 DietPi 2d9237116c21[2294]: 1:M 13 Jul 2024 21:30:12.595 * Done loading RDB, keys loaded: 2, keys expired: 0.
Jul 13 22:30:12 DietPi 2d9237116c21[2294]: 1:M 13 Jul 2024 21:30:12.596 * DB loaded from disk: 0.064 secondsJul 13 22:30:12 DietPi 2d9237116c21[2294]: 1:M 13 Jul 2024 21:30:12.596 * Ready to accept connections tcp
Jul 13 22:30:12 DietPi systemd[1]: mnt-dietpi_userdata-docker\x2ddata-overlay2-opaque\x2dbug\x2dcheck185395284-merged.mount: Succeeded.
Jul 13 22:30:13 DietPi 1e224e620239[2294]: s6-rc: info: service legacy-services successfully started
Jul 13 22:30:13 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4013
Jul 13 22:30:13 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:13 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4016
Jul 13 22:30:13 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:13 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4023
Jul 13 22:30:13 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:13 DietPi 19e05cb20ae3[2294]: iptables: No chain/target/match by that name.
Jul 13 22:30:13 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4027
Jul 13 22:30:13 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:14 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4032
Jul 13 22:30:14 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:14 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4034
Jul 13 22:30:14 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:14 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4036
Jul 13 22:30:14 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:14 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4038
Jul 13 22:30:14 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:14 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4042
Jul 13 22:30:14 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:14 DietPi kernel: dotnet[3945]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
Jul 13 22:30:14 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4044
Jul 13 22:30:14 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:14 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4046
Jul 13 22:30:14 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:14 DietPi 19e05cb20ae3[2294]: iptables: No chain/target/match by that name.
Jul 13 22:30:14 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4050
Jul 13 22:30:14 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:14 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4055
Jul 13 22:30:14 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:14 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4057
Jul 13 22:30:14 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:14 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4059
Jul 13 22:30:14 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:14 DietPi kernel: bpfilter: Loaded bpfilter_umh pid 4062
Jul 13 22:30:14 DietPi kernel: bpfilter: read fail 0
Jul 13 22:30:15 DietPi 19e05cb20ae3[2294]: Enabling IPv6 Forwarding
Jul 13 22:30:15 DietPi 19e05cb20ae3[2294]: sysctl: error setting key 'net.ipv6.conf.all.disable_ipv6': Read-only file system
Jul 13 22:30:15 DietPi 19e05cb20ae3[2294]: Failed to enable IPv6 supportJul 13 22:30:15 DietPi 19e05cb20ae3[2294]: sysctl: error setting key 'net.ipv6.conf.default.forwarding': Read-only file system
Jul 13 22:30:15 DietPi 19e05cb20ae3[2294]: Failed to enable IPv6 Forwarding default
Jul 13 22:30:15 DietPi 19e05cb20ae3[2294]: sysctl: error setting key 'net.ipv6.conf.all.forwarding': Read-only file system
Jul 13 22:30:15 DietPi 19e05cb20ae3[2294]: Failed to enable IPv6 Forwarding
Jul 13 22:30:15 DietPi 19e05cb20ae3[2294]: Running 'openvpn --config /etc/openvpn/openvpn.conf --client-config-dir /etc/openvpn/ccd --crl-verify /etc/openvpn/crl.pem '
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 Unrecognized option or missing or extra parameter(s) in /etc/openvpn/openvpn.conf:27: block-outside-dns (2.5.6)
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 WARNING: --topology net30 support for server configs with IPv4 pools will be removed in a future release. Please migrate to --topology subnet as soon as possible.
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 --cipher is not set. Previous OpenVPN version defaulted to BF-CBC as fallback when cipher negotiation failed in this case. If you need this fallback please add '--data-ciphers-fallback BF-CBC' to your configuration and/or add BF-CBC to --data-ciphers.
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 OpenVPN 2.5.6 aarch64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Apr 17 2022
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 library versions: OpenSSL 1.1.1q  5 Jul 2022, LZO 2.10
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 Diffie-Hellman initialized with 2048 bit key
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 CRL: loaded 1 CRLs from file /etc/openvpn/crl.pem
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 ROUTE_GATEWAY 172.27.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:1b:00:02
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 TUN/TAP device tun0 opened
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 /sbin/ip link set dev tun0 up mtu 1500
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 /sbin/ip link set dev tun0 up
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 /sbin/ip addr add dev tun0 local 192.168.255.1 peer 192.168.255.2
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 /sbin/ip route add 192.168.254.0/24 via 192.168.255.2
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 /sbin/ip route add 192.168.255.0/24 via 192.168.255.2
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 Could not determine IPv4/IPv6 protocol. Using AF_INET
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 Socket Buffers: R=[212992->212992] S=[212992->212992]
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 UDPv4 link local (bound): [AF_INET][undef]:1194
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 UDPv4 link remote: [AF_UNSPEC]
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 GID set to nogroup
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 UID set to nobody
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 MULTI: multi_init called, r=256 v=256
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 IFCONFIG POOL IPv4: base=192.168.255.4 size=62
Jul 13 22:30:16 DietPi 19e05cb20ae3[2294]: 2024-07-13 21:30:16 Initialization Sequence Completed
Jul 13 22:30:22 DietPi 7969df7e8868[2294]: 2024/07/13 09:30PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:369 > encryption key file not present | filename=portainer
Jul 13 22:30:22 DietPi 7969df7e8868[2294]: 2024/07/13 09:30PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:392 > proceeding without encryption key |
Jul 13 22:30:22 DietPi 7969df7e8868[2294]: 2024/07/13 09:30PM INF github.com/portainer/portainer/api/database/boltdb/db.go:125 > loading PortainerDB | filename=portainer.db
Jul 13 22:30:22 DietPi d617c70ddbfe[2294]: Sat, 13 Jul 2024 23:30:22 CEST INF Starting Diun version=v4.26.0
Jul 13 22:30:22 DietPi d617c70ddbfe[2294]: Sat, 13 Jul 2024 23:30:22 CEST INF Configuration loaded from 5 environment variable(s)
Jul 13 22:30:22 DietPi d617c70ddbfe[2294]: Sat, 13 Jul 2024 23:30:22 CEST WRN No notifier available
Jul 13 22:30:22 DietPi d617c70ddbfe[2294]: Sat, 13 Jul 2024 23:30:22 CEST INF Cron triggered
Jul 13 22:30:23 DietPi d617c70ddbfe[2294]: Sat, 13 Jul 2024 23:30:23 CEST INF Found 1 image(s) to analyze provider=docker
Jul 13 22:30:23 DietPi e950683ceee4[2294]: [migrations] started
Jul 13 22:30:23 DietPi e950683ceee4[2294]: [migrations] no migrations found
Jul 13 22:30:23 DietPi bf712e7e93b0[2294]: ❯ Configuring npm user ...
Jul 13 22:30:23 DietPi bf712e7e93b0[2294]: 0
Jul 13 22:30:23 DietPi 7969df7e8868[2294]: 2024/07/13 09:30PM INF github.com/portainer/portainer/api/chisel/service.go:198 > Found Chisel private key file on disk | private-key=/data/chisel/private-key.pem
Jul 13 22:30:23 DietPi 7969df7e8868[2294]: 2024/07/13 21:30:23 server: Reverse tunnelling enabled
Jul 13 22:30:23 DietPi 7969df7e8868[2294]: 2024/07/13 21:30:23 server: Fingerprint W4ilSO2Q52Iqe5GDG0apN041yHYVZNRrP79k/fptse4=
Jul 13 22:30:23 DietPi 7969df7e8868[2294]: 2024/07/13 21:30:23 server: Listening on http://0.0.0.0:8000
Jul 13 22:30:23 DietPi 7969df7e8868[2294]: 2024/07/13 09:30PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:649 > starting Portainer | build_number=35428 go_version=1.20.5 image_tag=linux-arm64-2.19.4 nodejs_version=18.19.0 version=2.19.4 webpack_version=5.88.1 yarn_version=1.22.21
Jul 13 22:30:24 DietPi 7969df7e8868[2294]: 2024/07/13 09:30PM INF github.com/portainer/portainer/api/http/server.go:341 > starting HTTP server | bind_address=:9000
Jul 13 22:30:24 DietPi 7969df7e8868[2294]: 2024/07/13 09:30PM INF github.com/portainer/portainer/api/http/server.go:357 > starting HTTPS server | bind_address=:9443
Jul 13 22:30:24 DietPi e950683ceee4[2294]: usermod: no changes
Jul 13 22:30:24 DietPi bf712e7e93b0[2294]: usermod: no changes
Jul 13 22:30:24 DietPi e950683ceee4[2294]: ───────────────────────────────────────
Jul 13 22:30:24 DietPi e950683ceee4[2294]: 
Jul 13 22:30:24 DietPi e950683ceee4[2294]:       ██╗     ███████╗██╗ ██████╗
Jul 13 22:30:24 DietPi e950683ceee4[2294]:       ██║     ██╔════╝██║██╔═══██╗
Jul 13 22:30:24 DietPi e950683ceee4[2294]:       ██║     ███████╗██║██║   ██║
Jul 13 22:30:24 DietPi e950683ceee4[2294]:       ██║     ╚════██║██║██║   ██║
Jul 13 22:30:24 DietPi e950683ceee4[2294]:       ███████╗███████║██║╚██████╔╝
Jul 13 22:30:24 DietPi e950683ceee4[2294]:       ╚══════╝╚══════╝╚═╝ ╚═════╝
Jul 13 22:30:24 DietPi e950683ceee4[2294]: 
Jul 13 22:30:24 DietPi e950683ceee4[2294]:    Brought to you by linuxserver.io
Jul 13 22:30:24 DietPi e950683ceee4[2294]: ───────────────────────────────────────
Jul 13 22:30:24 DietPi e950683ceee4[2294]: 
Jul 13 22:30:24 DietPi e950683ceee4[2294]: To support LSIO projects visit:
Jul 13 22:30:24 DietPi e950683ceee4[2294]: https://www.linuxserver.io/donate/
Jul 13 22:30:24 DietPi e950683ceee4[2294]: 
Jul 13 22:30:24 DietPi e950683ceee4[2294]: ───────────────────────────────────────
Jul 13 22:30:24 DietPi e950683ceee4[2294]: GID/UID
Jul 13 22:30:24 DietPi e950683ceee4[2294]: ───────────────────────────────────────
Jul 13 22:30:24 DietPi bf712e7e93b0[2294]: ❯ Configuring npm group ...
Jul 13 22:30:24 DietPi e950683ceee4[2294]: 
Jul 13 22:30:24 DietPi e950683ceee4[2294]: User UID:    0
Jul 13 22:30:24 DietPi e950683ceee4[2294]: User GID:    0
Jul 13 22:30:24 DietPi e950683ceee4[2294]: ───────────────────────────────────────
Jul 13 22:30:24 DietPi e950683ceee4[2294]: 
Jul 13 22:30:24 DietPi bf712e7e93b0[2294]: ❯ Checking paths ...
Jul 13 22:30:25 DietPi bf712e7e93b0[2294]: ❯ Setting ownership ...
Jul 13 22:30:26 DietPi d617c70ddbfe[2294]: Sat, 13 Jul 2024 23:30:26 CEST INF Jobs completed added=0 failed=0 skipped=0 unchanged=1 updated=0
Jul 13 22:30:26 DietPi d617c70ddbfe[2294]: Sat, 13 Jul 2024 23:30:26 CEST INF Cron initialized with schedule 0 */6 * * *
Jul 13 22:30:26 DietPi d617c70ddbfe[2294]: Sat, 13 Jul 2024 23:30:26 CEST INF Next run in 29 minutes 44 seconds (2024-07-14 00:00:10.946395793 +0200 CEST)
Jul 13 22:30:27 DietPi 7934e2f0a866[2294]: pm2 launched in no-daemon mode (you can add DEBUG="*" env variable to get more messages)
Jul 13 22:30:27 DietPi e950683ceee4[2294]: [custom-init] No custom files found, skipping...
Jul 13 22:30:29 DietPi bf712e7e93b0[2294]: ❯ Dynamic resolvers ...
Jul 13 22:30:29 DietPi bf712e7e93b0[2294]: ❯ IPv6 ...
Jul 13 22:30:29 DietPi bf712e7e93b0[2294]: Enabling IPV6 in hosts in: /etc/nginx/conf.d
Jul 13 22:30:29 DietPi bf712e7e93b0[2294]: - /etc/nginx/conf.d/default.conf
Jul 13 22:30:29 DietPi bf712e7e93b0[2294]: - /etc/nginx/conf.d/production.conf
Jul 13 22:30:29 DietPi bf712e7e93b0[2294]: - /etc/nginx/conf.d/include/assets.conf
Jul 13 22:30:29 DietPi bf712e7e93b0[2294]: - /etc/nginx/conf.d/include/ip_ranges.conf
Jul 13 22:30:29 DietPi bf712e7e93b0[2294]: - /etc/nginx/conf.d/include/block-exploits.conf
Jul 13 22:30:29 DietPi bf712e7e93b0[2294]: - /etc/nginx/conf.d/include/proxy.conf
Jul 13 22:30:29 DietPi bf712e7e93b0[2294]: - /etc/nginx/conf.d/include/ssl-ciphers.conf
Jul 13 22:30:29 DietPi bf712e7e93b0[2294]: - /etc/nginx/conf.d/include/force-ssl.conf
Jul 13 22:30:29 DietPi bf712e7e93b0[2294]: - /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: - /etc/nginx/conf.d/include/resolvers.conf
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: Enabling IPV6 in hosts in: /data/nginx
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: - /data/nginx/proxy_host/5.conf
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: - /data/nginx/proxy_host/3.conf
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: - /data/nginx/default_host/site.conf
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: ❯ Docker secrets ...
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: 
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: -------------------------------------
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]:  _   _ ____  __  __
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: | \ | |  _ \|  \/  |
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: |  \| | |_) | |\/| |
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: | |\  |  __/| |  | |
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: |_| \_|_|   |_|  |_|
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: -------------------------------------
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: User:  npm PUID:0 ID:0 GROUP:0
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: Group: npm PGID:0 ID:0
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: -------------------------------------
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: 
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: ❯ Starting backend ...
Jul 13 22:30:30 DietPi bf712e7e93b0[2294]: ❯ Starting nginx ...
Jul 13 22:30:32 DietPi 7934e2f0a866[2294]: 2024-07-13T21:30:32: PM2 log: Launching in no daemon mode
Jul 13 22:30:32 DietPi e950683ceee4[2294]: WebUI will be started shortly after internal preparations. Please wait...
Jul 13 22:30:33 DietPi 7934e2f0a866[2294]: 2024-07-13T21:30:33: PM2 log: [PM2] Starting /app/app.js in fork_mode (1 instance)
Jul 13 22:30:33 DietPi 7934e2f0a866[2294]: 2024-07-13T21:30:33: PM2 log: App [proxy:0] starting in -fork mode-
Jul 13 22:30:33 DietPi 7934e2f0a866[2294]: 2024-07-13T21:30:33: PM2 log: App [proxy:0] online
Jul 13 22:30:33 DietPi 7934e2f0a866[2294]: 2024-07-13T21:30:33: PM2 log: [PM2] Done.
Jul 13 22:30:34 DietPi 7934e2f0a866[2294]: 2024-07-13T21:30:34: PM2 log: ┌────┬──────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
Jul 13 22:30:34 DietPi 7934e2f0a866[2294]: │ id │ name     │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
Jul 13 22:30:34 DietPi 7934e2f0a866[2294]: ├────┼──────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
Jul 13 22:30:34 DietPi 7934e2f0a866[2294]: │ 0  │ proxy    │ default     │ 1.11.0  │ fork    │ 18       │ 0s     │ 0    │ online    │ 0%       │ 35.8mb   │ root     │ disabled │
Jul 13 22:30:34 DietPi 7934e2f0a866[2294]: └────┴──────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
Jul 13 22:30:34 DietPi 7934e2f0a866[2294]: 2024-07-13T21:30:34: PM2 log: [--no-daemon] Continue to stream logs
Jul 13 22:30:34 DietPi 7934e2f0a866[2294]: 2024-07-13T21:30:34: PM2 log: [--no-daemon] Exit on target PM2 exit pid=1
Jul 13 22:30:35 DietPi e950683ceee4[2294]: 
Jul 13 22:30:35 DietPi e950683ceee4[2294]: ******** Information ********Jul 13 22:30:35 DietPi e950683ceee4[2294]: To control qBittorrent, access the WebUI at: http://localhost:8080
Jul 13 22:30:35 DietPi e950683ceee4[2294]: 
Jul 13 22:30:35 DietPi e950683ceee4[2294]: Connection to localhost (::1) 8080 port [tcp/http-alt] succeeded!Jul 13 22:30:35 DietPi e950683ceee4[2294]: [ls.io-init] done.
Jul 13 22:30:38 DietPi sshd[4585]: Accepted password for root from 192.168.1.200 port 59674 ssh2
Jul 13 22:30:39 DietPi bf712e7e93b0[2294]: [7/13/2024] [9:30:38 PM] [Global   ] › ℹ  info      Using Sqlite: /data/database.sqlite
Jul 13 22:30:39 DietPi sshd[4585]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Jul 13 22:30:42 DietPi 66790425f503[2294]: Technitium DNS Server was started successfully.
Jul 13 22:30:42 DietPi 66790425f503[2294]: Using config folder: /etc/dns/config
Jul 13 22:30:42 DietPi 66790425f503[2294]: 
Jul 13 22:30:42 DietPi 66790425f503[2294]: Note: Open http://66790425f503:5380/ in web browser to access web console.
Jul 13 22:30:42 DietPi 66790425f503[2294]: 
Jul 13 22:30:42 DietPi 66790425f503[2294]: Press [CTRL + C] to stop...
Jul 13 22:30:48 DietPi 1e224e620239[2294]: 2024-07-13 22:30:47.999 WARNING (MainThread) [homeassistant.helpers.translation] Failed to load integration for translation: Integration 'discovery' not found.
Jul 13 22:30:52 DietPi 7934e2f0a866[2294]: 21:30:52 0|proxy  | [18] [2024-07-13T21:30:52.310] [ INFO] - Start simple socks5 proxy server
Jul 13 22:30:52 DietPi 7934e2f0a866[2294]: 21:30:52 0|proxy  | [18] [2024-07-13T21:30:52.356] [ INFO] - Start listening on port: 54321
Jul 13 22:31:01 DietPi bf712e7e93b0[2294]: [7/13/2024] [9:31:01 PM] [Migrate  ] › ℹ  info      Current database version: none
Jul 13 22:31:02 DietPi 1e224e620239[2294]: 2024-07-13 22:31:02.683 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
Jul 13 22:31:06 DietPi 1e224e620239[2294]: 2024-07-13 22:31:06.879 ERROR (MainThread) [homeassistant.config] Platform error: sensor - Integration 'yr' not found.
Jul 13 22:31:06 DietPi 1e224e620239[2294]: 2024-07-13 22:31:06.920 ERROR (MainThread) [homeassistant.setup] Setup failed for 'discovery': Integration not found.
Jul 13 22:31:07 DietPi 1e224e620239[2294]: 2024-07-13 22:31:07.041 ERROR (MainThread) [homeassistant.components.automation] Unnamed automation could not be validated and has been disabled: extra keys not allowed @ data['automation']. Got {'trigger': {'platform': 'event', 'event_type': 'ifttt_webhook_received', 'event_data': {'action': 'call_service'}}, 'action': {'service_template': '{{ trigger.event.data.service }}', 'data_template': {'entity_id': '{{ trigger.event.data.entity_id }}'}}}
Jul 13 22:31:07 DietPi 1e224e620239[2294]: required key not provided @ data['action']. Got None
Jul 13 22:31:07 DietPi 1e224e620239[2294]: required key not provided @ data['trigger']. Got None
Jul 13 22:31:18 DietPi bf712e7e93b0[2294]: [7/13/2024] [9:31:18 PM] [Setup    ] › ℹ  info      Added Certbot plugins certbot-dns-desec~=1.2.1 
Jul 13 22:31:18 DietPi bf712e7e93b0[2294]: [7/13/2024] [9:31:18 PM] [Setup    ] › ℹ  info      Logrotate Timer initialized
Jul 13 22:31:18 DietPi bf712e7e93b0[2294]: [7/13/2024] [9:31:18 PM] [Setup    ] › ℹ  info      Logrotate completed.
Jul 13 22:31:18 DietPi bf712e7e93b0[2294]: [7/13/2024] [9:31:18 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
Jul 13 22:31:18 DietPi bf712e7e93b0[2294]: [7/13/2024] [9:31:18 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
Jul 13 22:31:20 DietPi bf712e7e93b0[2294]: [7/13/2024] [9:31:20 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
Jul 13 22:31:20 DietPi bf712e7e93b0[2294]: [7/13/2024] [9:31:20 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
Jul 13 22:31:20 DietPi bf712e7e93b0[2294]: [7/13/2024] [9:31:20 PM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
Jul 13 22:31:20 DietPi bf712e7e93b0[2294]: [7/13/2024] [9:31:20 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
Jul 13 22:31:20 DietPi bf712e7e93b0[2294]: [7/13/2024] [9:31:20 PM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
Jul 13 22:31:20 DietPi bf712e7e93b0[2294]: [7/13/2024] [9:31:20 PM] [Global   ] › ℹ  info      Backend PID 150 listening on port 3000 ...
Jul 13 22:31:22 DietPi 1e224e620239[2294]: 2024-07-13 22:31:22.365 ERROR (MainThread) [homeassistant.components.scene] Platform tuya does not generate unique IDs. ID tysrJA5Q9EWpWFyIiHm already exists - ignoring scene.power_off
Jul 13 22:31:22 DietPi 1e224e620239[2294]: 2024-07-13 22:31:22.366 ERROR (MainThread) [homeassistant.components.scene] Platform tuya does not generate unique IDs. ID tysZCTE9tytUhIu5mqC already exists - ignoring scene.power_on
Jul 13 22:31:22 DietPi 1e224e620239[2294]: 2024-07-13 22:31:22.590 ERROR (MainThread) [homeassistant.components.switch] Platform tuya does not generate unique IDs. ID tuya.03200296dc4f22293af6switch already exists - ignoring switch.smart_plug_socket
Jul 13 22:31:31 DietPi bf712e7e93b0[2294]: [7/13/2024] [9:31:31 PM] [Nginx    ] › ℹ  info      Reloading Nginx
Jul 13 22:31:31 DietPi bf712e7e93b0[2294]: [7/13/2024] [9:31:31 PM] [SSL      ] › ℹ  info      Renew Complete
Jul 13 22:33:48 DietPi devnull[5060]: #!/bin/bash
Jul 13 22:35:01 DietPi CRON[5198]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 22:35:01 DietPi CRON[5199]: (root) CMD (/opt/checkgw.sh)
Jul 13 22:35:11 DietPi CRON[5198]: pam_unix(cron:session): session closed for user root
Jul 13 22:39:16 DietPi sshd[4585]: Received disconnect from 192.168.1.200 port 59674:11: Normal Shutdown
Jul 13 22:39:16 DietPi sshd[4585]: Disconnected from user root 192.168.1.200 port 59674
Jul 13 22:39:16 DietPi sshd[4585]: pam_unix(sshd:session): session closed for user root
Jul 13 22:40:01 DietPi CRON[5770]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 22:40:01 DietPi CRON[5771]: (root) CMD (/opt/checkgw.sh)
Jul 13 22:40:11 DietPi CRON[5770]: pam_unix(cron:session): session closed for user root
Jul 13 22:43:08 DietPi sshd[6142]: Accepted password for root from 192.168.1.200 port 59834 ssh2
Jul 13 22:43:08 DietPi sshd[6142]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Jul 13 22:43:09 DietPi systemd[1]: Starting Cleanup of Temporary Directories...
Jul 13 22:43:09 DietPi systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Jul 13 22:43:09 DietPi systemd[1]: Finished Cleanup of Temporary Directories.
Jul 13 22:43:13 DietPi systemd[1]: Starting Network Time Synchronization...
Jul 13 22:43:14 DietPi systemd[1]: Started Network Time Synchronization.Jul 13 22:43:14 DietPi systemd-timesyncd[6201]: Initial synchronization to time server 141.98.136.83:123 (0.debian.pool.ntp.org).
Jul 13 22:43:15 DietPi systemd[1]: Stopping Network Time Synchronization...
Jul 13 22:43:15 DietPi systemd[1]: systemd-timesyncd.service: Succeeded.Jul 13 22:43:15 DietPi systemd[1]: Stopped Network Time Synchronization.Jul 13 22:45:01 DietPi CRON[6423]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 22:45:01 DietPi CRON[6424]: (root) CMD (/opt/checkgw.sh)
Jul 13 22:45:11 DietPi CRON[6423]: pam_unix(cron:session): session closed for user root
Jul 13 22:50:01 DietPi CRON[6995]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 22:50:01 DietPi CRON[6996]: (root) CMD (/opt/checkgw.sh)
Jul 13 22:50:11 DietPi CRON[6995]: pam_unix(cron:session): session closed for user root
Jul 13 22:50:14 DietPi sshd[6142]: Received disconnect from 192.168.1.200 port 59834:11: Normal Shutdown
Jul 13 22:50:14 DietPi sshd[6142]: Disconnected from user root 192.168.1.200 port 59834
Jul 13 22:50:14 DietPi sshd[6142]: pam_unix(sshd:session): session closed for user root
Jul 13 22:54:31 DietPi sshd[7500]: Accepted password for root from 192.168.1.200 port 59956 ssh2
Jul 13 22:54:31 DietPi sshd[7500]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Jul 13 22:55:01 DietPi CRON[7583]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 22:55:01 DietPi CRON[7584]: (root) CMD (/opt/checkgw.sh)
Jul 13 22:55:11 DietPi CRON[7583]: pam_unix(cron:session): session closed for user root
root@DietPi:~#

Nearly everything is the Docker engine and container startup, which should not be related, then I see the SSH logins, the tmpfiles cleanup (which we tested already) and the network time sync we just tested. The only other thing I see is this script executed from cron:

cat /opt/checkgw.sh

Though this runs some minutes after your first SSH login. There is another cron "session closed" log entry earlier, from which we do not see the start entry. So additionally, can you paste the cron logs again?

journalctl -u cron

@DietPi:~# journalctl | grep DietPi-PostBoot                                  Jul 13 22:28:01 DietPi systemd[1]: Started DietPi-PostBoot.
root@DietPi:~#
root@DietPi:~# journalctl -e --since "2024-07-13 22:28:01" --until=now > /mnt/sdb1/log.txt

Please find log.txt log.txt

root@DietPi:~# cat /opt/checkgw.sh
#!/bin/bash                  
maxPloss=10 #Maximum percent packet loss before a restart             
# Initialize to a value that would forcea restart                    
# (just in case ping gives an error and ploss doesn't get set)        
#modprobe ip6_tables         
ploss=101                    
ploss=$(ping -q -w10 dietpi.com | grep -o "[0-9]*%" | tr -d %) > /dev/null 2>&1
if [ "$ploss" -gt "$maxPloss" ]; then
        logger "internet unstable"
        echo "$(date "+%Y-%m-%d %H:%M:%S") : internet unstable" | tee -a /opt/network_check
x=`ping -c1 ifconfig.me 2>&1 | grep unknown`
if [ ! "$x" = "" ]; then
        logger  "Internet's down!! Attempting to ping gateway."
echo "$(date "+%Y-%m-%d %H:%M:%S") : Internet's down" | tee -a /opt/network_check
        ping -c3 192.168.1.1 &> /dev/null
if [ $? -gt 0 ]then
#Make a note in syslog
echo "$(date "+%Y-%m-%d %H:%M:%S") : gateway is unreacheable down restarting H96Max+" | tee -a /opt/network_check
        logger "network_check: Network connection is down, restarting H96Max+ ..."
reboot
fi
fi
fi

root@DietPi:~#

t@DietPi:~# journalctl -u cron        -- Journal begins at Sat 2024-07-13 22:27:50 BST, ends at Sat 2024-07-13 23:55:01 BST. --
Jul 13 22:27:52 DietPi systemd[1]: Started Regular background program processing daemon.
Jul 13 22:27:52 DietPi cron[354]: (CRON) INFO (pidfile fd = 3)
Jul 13 22:27:52 DietPi cron[354]: (CRON) INFO (Running @reboot jobs)
Jul 13 22:30:01 DietPi CRON[2813]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 22:30:01 DietPi CRON[2816]: (root) CMD (/opt/checkgw.sh)
Jul 13 22:30:11 DietPi CRON[2813]: pam_unix(cron:session): session closed for user root
Jul 13 22:35:01 DietPi CRON[5198]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 22:35:01 DietPi CRON[5199]: (root) CMD (/opt/checkgw.sh)
Jul 13 22:35:11 DietPi CRON[5198]: pam_unix(cron:session): session closed for user root
Jul 13 22:40:01 DietPi CRON[5770]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 22:40:01 DietPi CRON[5771]: (root) CMD (/opt/checkgw.sh)
Jul 13 22:40:11 DietPi CRON[5770]: pam_unix(cron:session): session closed for user root
Jul 13 22:45:01 DietPi CRON[6423]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 22:45:01 DietPi CRON[6424]: (root) CMD (/opt/checkgw.sh)
Jul 13 22:45:11 DietPi CRON[6423]: pam_unix(cron:session): session closed for user root
Jul 13 22:50:01 DietPi CRON[6995]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 22:50:01 DietPi CRON[6996]: (root) CMD (/opt/checkgw.sh)
Jul 13 22:50:11 DietPi CRON[6995]: pam_unix(cron:session): session closed for user root
Jul 13 22:55:01 DietPi CRON[7583]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 22:55:01 DietPi CRON[7584]: (root) CMD (/opt/checkgw.sh)
Jul 13 22:55:11 DietPi CRON[7583]: pam_unix(cron:session): session closed for user root
Jul 13 23:00:02 DietPi CRON[8166]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 23:00:02 DietPi CRON[8167]: (root) CMD (/opt/checkgw.sh)
Jul 13 23:00:12 DietPi CRON[8166]: pam_unix(cron:session): session closed for user root
Jul 13 23:05:01 DietPi CRON[8750]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 23:05:01 DietPi CRON[8751]: (root) CMD (/opt/checkgw.sh)
Jul 13 23:05:11 DietPi CRON[8750]: pam_unix(cron:session): session closed for user root
Jul 13 23:10:01 DietPi CRON[9296]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 23:10:01 DietPi CRON[9297]: (root) CMD (/opt/checkgw.sh)
Jul 13 23:10:11 DietPi CRON[9296]: pam_unix(cron:session): session closed for user root
Jul 13 23:15:01 DietPi CRON[9859]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 23:15:01 DietPi CRON[9860]: (root) CMD (/opt/checkgw.sh)
Jul 13 23:15:11 DietPi CRON[9859]: pam_unix(cron:session): session closed for user root
Jul 13 23:17:01 DietPi CRON[10092]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 23:17:01 DietPi CRON[10093]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jul 13 23:17:02 DietPi CRON[10092]: pam_unix(cron:session): session closed for user root
Jul 13 23:20:01 DietPi CRON[10492]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 23:20:01 DietPi CRON[10493]: (root) CMD (/opt/checkgw.sh)
Jul 13 23:20:11 DietPi CRON[10492]: pam_unix(cron:session): session closed for user root
Jul 13 23:25:01 DietPi CRON[11045]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 23:25:01 DietPi CRON[11046]: (root) CMD (/opt/checkgw.sh)
Jul 13 23:25:11 DietPi CRON[11045]: pam_unix(cron:session): session closed for user root
Jul 13 23:30:01 DietPi CRON[11618]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 23:30:01 DietPi CRON[11619]: (root) CMD (/opt/checkgw.sh)
Jul 13 23:30:11 DietPi CRON[11618]: pam_unix(cron:session): session closed for user root
Jul 13 23:35:01 DietPi CRON[12223]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 23:35:01 DietPi CRON[12224]: (root) CMD (/opt/checkgw.sh)
Jul 13 23:35:11 DietPi CRON[12223]: pam_unix(cron:session): session closed for user root
Jul 13 23:40:01 DietPi CRON[12806]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 23:40:01 DietPi CRON[12807]: (root) CMD (/opt/checkgw.sh)
Jul 13 23:40:11 DietPi CRON[12806]: pam_unix(cron:session): session closed for user root
Jul 13 23:45:01 DietPi CRON[13374]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 23:45:01 DietPi CRON[13375]: (root) CMD (/opt/checkgw.sh)
Jul 13 23:45:11 DietPi CRON[13374]: pam_unix(cron:session): session closed for user root
Jul 13 23:50:01 DietPi CRON[13935]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 23:50:01 DietPi CRON[13936]: (root) CMD (/opt/checkgw.sh)
Jul 13 23:50:11 DietPi CRON[13935]: pam_unix(cron:session): session closed for user root
Jul 13 23:55:01 DietPi CRON[14494]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jul 13 23:55:01 DietPi CRON[14495]: (root) CMD (/opt/checkgw.sh)
root@DietPi:~#

So indeed the first cron entry was also from this script. Can you check whether it is the culprit:

rm /dev/null
mknod -m 0666 /dev/null c 1 3
/opt/checkgw.sh
ls -l /dev/null

It seems to have at least one syntax error, but it could be also caused by copy&paste.

root@DietPi:~# rm /dev/null                   root@DietPi:~# mknod -m 0666 /dev/null c 1 3
root@DietPi:~# /opt/checkgw.sh

root@DietPi:~# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 14 06:49 /dev/null
root@DietPi:~# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jul 14 06:49 /dev/null

I commented the cron entry calling checkgw.sh using crontab -e I executed this

rm /dev/null
mknod -m 0666 /dev/null c 1 3

root@DietPi:~# ls -l /dev/null 
crw-rw-rw- 1 root root 1, 3 Jul 14 21:15 /dev/null 

root@DietPi:~# reboot

root@DietPi:~# ls -l /dev/null
-rw-r--r-- 1 root root 0 Jul 14 21:19 /dev/null
root@DietPi:~# journalctl -u cron
-- Journal begins at Sun 2024-07-14 21:14:40 BST, ends atSun2024-07
-14 21:19:39 BST. --
Jul 14 21:14:42 DietPi systemd[1]: Started Regular backgroundprogram
 processing daemon.
Jul 14 21:14:42 DietPi cron[353]: (CRON) INFO (pidfile fd=3)
Jul 14 21:14:42 DietPi cron[353]: (CRON) INFO (Running @rebootjobs)
Jul 14 21:17:01 DietPi CRON[4013]: pam_unix(cron:session):session opened for user root(uid=0) by (uid=0)
Jul 14 21:17:01 DietPi CRON[4020]: (root) CMD (cd / && run-parts--re
port /etc/cron.hourly)
Jul 14 21:17:03 DietPi CRON[4013]: pam_unix(cron:session):session closed for user root
root@DietPi:~#

Can you update dietpi-update to include this rm /dev/null mknod -m 0666 /dev/null c 1 3 In the next update?

MichaIng / DietPi

unable to update dietpi to latest version #7157

Details:

Steps to reproduce:

Expected behaviour:

Actual behaviour:

Extra details:

Additional logs: