Proxmox V7.1-10 systemd-timedated.service failed 226/Namespace

S

smogporter

New Member
Oct 6, 2020
3
0
1
34
Hi Guys,
i have a Proxmox Cluster with Version V7.1-10 and V6.4-13

The 6.4-13 is actually not updated, but in the future I like to Update the Server.


At the V7.1-10 I have a problem with Timedatd and hostnamed Service.
The Time are not Synchonized.
The V7.1-10 have an NVME / ZFS Pool.

Here the systemctl List:
root@XXXX:~# systemctl list-units --state=failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● systemd-hostnamed.service loaded failed failed Hostname Service
● systemd-timedated.service loaded failed failed Time & Date Service
● zfs-import@NVME\x2d372.service loaded failed failed Import ZFS pool NVME\x2d372
● zfs-import@NVMEx2d372.service loaded failed failed Import ZFS pool NVMEx2d372
● pvesr.timer not-found failed failed pvesr.timer

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
5 loaded units listed.


root@XXXX:~# systemctl status systemd-hostnamed.service
● systemd-hostnamed.service - Hostname Service
Loaded: loaded (/lib/systemd/system/systemd-hostnamed.service; static)
Active: failed (Result: exit-code) since Thu 2022-02-10 10:23:24 CET; 22h ago
Docs: man:systemd-hostnamed.service(8)
man:hostname(5)
man:machine-info(5)
man:org.freedesktop.resolve1(5)
Process: 881025 ExecStart=/lib/systemd/systemd-hostnamed (code=exited, status=226/NAMESPACE)
Main PID: 881025 (code=exited, status=226/NAMESPACE)
CPU: 10ms

Feb 10 10:23:14 XXXX systemd[1]: Starting Hostname Service...
Feb 10 10:23:24 XXXX systemd[881025]: systemd-hostnamed.service: Failed to set up mount namespacing: /run/systemd/unit-root/: Host is down
Feb 10 10:23:24 XXXX systemd[881025]: systemd-hostnamed.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-hostname>
Feb 10 10:23:24 XXXX systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=226/NAMESPACE
Feb 10 10:23:24 XXXX systemd[1]: systemd-hostnamed.service: Failed with result 'exit-code'.
Feb 10 10:23:24 XXXX systemd[1]: Failed to start Hostname Service.
lines 1-17/17 (END)

root@XXXX :~# systemctl status systemd-timedated.service
● systemd-timedated.service - Time & Date Service
Loaded: loaded (/lib/systemd/system/systemd-timedated.service; static)
Active: failed (Result: exit-code) since Thu 2022-02-10 10:18:56 CET; 22h ago
Docs: man:systemd-timedated.service(8)
man:localtime(5)
man:org.freedesktop.timedate1(5)
Process: 842584 ExecStart=/lib/systemd/systemd-timedated (code=exited, status=226/NAMESPACE)
Main PID: 842584 (code=exited, status=226/NAMESPACE)
CPU: 7ms

Feb 10 10:18:46 XXXX systemd[1]: Starting Time & Date Service...
Feb 10 10:18:56 XXXX systemd[842584]: systemd-timedated.service: Failed to set up mount namespacing: /run/systemd/unit-root/: Ho>
Feb 10 10:18:56 XXXX systemd[842584]: systemd-timedated.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-timedate>
Feb 10 10:18:56 XXXX systemd[1]: systemd-timedated.service: Main process exited, code=exited, status=226/NAMESPACE
Feb 10 10:18:56 XXXX systemd[1]: systemd-timedated.service: Failed with result 'exit-code'.
Feb 10 10:18:56 XXXX systemd[1]: Failed to start Time & Date Service.


The services can´t start. The installation of the system is an Standard installation with ZFS Pool.

Anyone can Help me?
 
If I start Timesyncd manually its synchronized the time

root@XXXXX:~# /usr/lib/systemd/systemd-timesyncd
Initial synchronization to time server 192.168.123.123:123 (XXXXXX.local).
 
Hi,
Proxmox VE does not use systemd-timesyncd as NTP client. It uses chrony, please post the output of systemctl status chrony.service if you encounter timesync issues and disable the systemd-timesyncd service.
 
In my case it's because of an SMB-storage for offline backups which causes the error if the endpoint of the mount is not available when it's offline
 
You must log in or register to reply here.
Top Bottom