| pve-manager/6.3-2/22f57405 5.4.73-1-pve #1 SMP PVE 5.4.73-1 There is no HA membership, the node is only part of a cluster with one CT (211) on it. |
Inside the LXC container, Bareos (bakula fork) is running with a Postgresql DB.
Command: command 'lxc-stop -n 211 --nokill --timeout 60' failed: exit code 1
ps aux | grep 211
root 6243 0.0 0.0 3836 2964 ? Ss 14:51 0:00 /usr/bin/lxc-start -F -n 211
root 13333 0.0 2.0 361628 122652 ? Ss 15:15 0:00 task UPID
ve4:00003415:000388A8:6076EAF3:vzshutdown:211:root@pct list
VMID Status Lock Name
211 running bareos.domain.com
pct enter 211
[root@bareos ~]# ps ax
PID TTY STAT TIME COMMAND
1 ? Ss 0:00 /sbin/init
39 ? Ss 0:00 /usr/lib/systemd/systemd-journald
48 ? Ss 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-o
52 ? Ssl 0:01 /usr/sbin/NetworkManager --no-daemon
2894 ? Ss 0:00 /bin/bash
2908 ? R+ 0:00 ps ax
How can I find out, which process blocks the CT for shutting down successful?
This are following the lines from /var/log/messages of the CT
Apr 14 15:06:24 bareos systemd[1]: systemd-tmpfiles-clean.service: Failed to reset devices.list: Operation not permitted
Apr 14 15:06:24 bareos systemd[1]: Starting Cleanup of Temporary Directories...
Apr 14 15:06:24 bareos systemd-tmpfiles[2678]: [/usr/lib/tmpfiles.d/postgresql.conf:1] Line references path below legacy directory /var/run/, updating /var/run/postgresql → /run/postgresql; please update the tmpfiles.d/ drop-in file accordingly.
Apr 14 15:06:24 bareos systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Apr 14 15:06:24 bareos systemd[1]: Started Cleanup of Temporary Directories.
The client is at the moment acessable by "pct enter".
Last edited: