Dietpi-Update failed (bullseye | Pi 4 | Dietpi v8.23.3)

Troubleshooting
1

Details:

  • Date | Fri Nov 10 01:31:16 AEDT 2023
  • DietPi version | v8.23.3 (MichaIng/master)
  • Image creator | DietPi Core Team
  • Pre-image | Raspberry Pi OS Lite 64-bit
  • Hardware | RPi 4 Model B (aarch64) (ID=4)
  • Kernel version | Linux Pi-1 5.10.103-v8+ #1529 SMP PREEMPT Tue Mar 8 12:26:46 GMT 2022 aarch64 GNU/Linux
  • Distro | bullseye (ID=6,RASPBIAN=0)
  • Command | systemctl start systemd-timesyncd
  • Exit code | 1
  • Software title | DietPi-TimeSync

Steps to reproduce:

  1. run> dietpi-update
  2. …

Expected behaviour:

  • …

Actual behaviour:

  • …

Extra details:

  • …
systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Fri 2023-11-10 01:31:07 AEDT; 43s ago
       Docs: man:systemd-timesyncd.service(8)
    Process: 2926720 ExecStart=/lib/systemd/systemd-timesyncd (code=exited, status=226/NAMESPACE)
   Main PID: 2926720 (code=exited, status=226/NAMESPACE)
        CPU: 39ms
..
 Nov 10 01:31:07 Pi-1 systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 5.
Nov 10 01:31:07 Pi-1 systemd[1]: Stopped Network Time Synchronization.
Nov 10 01:31:07 Pi-1 systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Nov 10 01:31:07 Pi-1 systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Nov 10 01:31:07 Pi-1 systemd[1]: Failed to start Network Time Synchronization.
Nov 10 01:31:16 Pi-1 systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Nov 10 01:31:16 Pi-1 systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Nov 10 01:31:16 Pi-1 systemd[1]: Failed to start Network Time Synchronization.

Additional logs:

Job for systemd-timesyncd.service failed because the control process exited with error code.

> journalctl -xe
Nov 10 01:31:07 Pi-1 systemd[1]: Starting Network Time Synchronization...
 Subject: A start job for unit systemd-timesyncd.service has begun execution
 Defined-By: systemd
 Support: https://www.debian.org/support
 
 A start job for unit systemd-timesyncd.service has begun execution.
 
 The job identifier is 178463.
Nov 10 01:31:07 Pi-1 systemd[2926690]: systemd-timesyncd.service: Failed to set up mount namespacing: /run/systemd/unit-root/: Stale file handle
Nov 10 01:31:07 Pi-1 systemd[2926690]: systemd-timesyncd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-timesyncd: Stale file handle
 Subject: Process /lib/systemd/systemd-timesyncd could not be executed
 Defined-By: systemd
 Support: https://www.debian.org/support
 
 The process /lib/systemd/systemd-timesyncd could not be executed and failed.
 
 The error number returned by this process is ERRNO.
Nov 10 01:31:07 Pi-1 systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=226/NAMESPACE
 Subject: Unit process exited
 Defined-By: systemd
 Support: https://www.debian.org/support
 
 An ExecStart= process belonging to unit systemd-timesyncd.service has exited.
 
 The process' exit code is 'exited' and its exit status is 226.
Nov 10 01:31:07 Pi-1 systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
 Subject: Unit failed
 Defined-By: systemd
 Support: https://www.debian.org/support
 
 The unit systemd-timesyncd.service has entered the 'failed' state with result 'exit-code'.
2

can you share whole log

journalctl -u systemd-timesyncd
3

It is strange, but now it updated fine. Did nothing, other than retried a day later. It may have been some internet backbone issue, as a major ISP here had some outage issue.