Restart the service error

[parker0909]

Hello All,

We got the problem when i try to restart the pvedaemon service and i found below message in the syslog. We got the problem the host disconnect suddenly from the cluster. I not sue it is related to the pvedaemon or not. Thank you.


Restart message:
command 'systemctl restart pvedaemon' failed: received interrupt


syslog for pvedaemon
-- Logs begin at Mon 2019-12-16 09:33:16 HKT, end at Tue 2019-12-17 09:32:03 HKT. --
Dec 16 09:33:29 cccs02 systemd[1]: Starting PVE API Daemon...
Dec 16 09:33:33 cccs02 pvedaemon[3336]: starting server
Dec 16 09:33:33 cccs02 pvedaemon[3336]: starting 3 worker(s)
Dec 16 09:33:33 cccs02 pvedaemon[3336]: worker 3339 started
Dec 16 09:33:33 cccs02 pvedaemon[3336]: worker 3340 started
Dec 16 09:33:33 cccs02 pvedaemon[3336]: worker 3341 started
Dec 16 09:33:33 cccs02 systemd[1]: Started PVE API Daemon.
Dec 17 09:27:31 cccs02 pvedaemon[3340]: <root@pam> starting task UPID:cccs02:00073663:008350EB:5DF82F03:aptupdate::root@pam:
Dec 17 09:27:36 cccs02 pvedaemon[472675]: update new package list: /var/lib/pve-manager/pkgupdates
Dec 17 09:27:38 cccs02 pvedaemon[3340]: <root@pam> end task UPID:cccs02:00073663:008350EB:5DF82F03:aptupdate::root@pam: OK
Dec 17 09:29:42 cccs02 pvedaemon[3339]: command '/bin/lsblk --json -o path,parttype' failed: exit code 1
Dec 17 09:29:42 cccs02 pvedaemon[3339]: command '/sbin/zpool list -HPLv' failed: exit code 127


-
Package Version
Virtual Environment 5.4-13
Search
Node 'cccs02'
Hour (maximum)
CPU usage 2.20% of 24 CPU(s)
IO delay 0.07%
Load average 0.51,0.69,0.78
RAM usage 16.49% (20.76 GiB of 125.86 GiB)
KSM sharing 0 B
HD space(root) 8.08% (2.66 GiB of 32.97 GiB)
SWAP usage 0.00% (0 B of 8.00 GiB)
CPU(s) 24 x Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz (2 Sockets)
Kernel Version Linux 4.15.18-21-pve #1 SMP PVE 4.15.18-48 (Fri, 20 Sep 2019 11:28:30 +0200)
PVE Manager Version pve-manager/5.4-13/aee6f0ec
Server View
Logs
()
proxmox-ve: 5.4-2 (running kernel: 4.15.18-21-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-9
pve-kernel-4.15.18-21-pve: 4.15.18-48
pve-kernel-4.15.18-17-pve: 4.15.18-43
pve-kernel-4.15.18-10-pve: 4.15.18-32
ceph: 12.2.12-pve1
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-4
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 6.0-8
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-60
proxmox-widget-toolkit: 2.0-7
pve-cluster: 5.0-38
pve-container: 3.0-7
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 3.0-22
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-3
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.13.2-1
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2

 

[t.lamprecht]

Hi,

We got the problem when i try to restart the pvedaemon service

Why did you restarted it, any issues?

We got the problem the host disconnect suddenly from the cluster. I not sue it is related to the pvedaemon or not.

I mean, pvedaemon handles all the API requests which need higher priviledges, so it's a pretty important daemon for a node..
Did you tried to restart it again, not that whyever you were just unlucky and it got signaled during restart.

Dec 17 09:29:42 cccs02 pvedaemon[3339]: command '/bin/lsblk --json -o path,parttype' failed: exit code 1
Dec 17 09:29:42 cccs02 pvedaemon[3339]: command '/sbin/zpool list -HPLv' failed: exit code 127

And those two quoted commands above work if you execute them manually, they are just status commands so it's save to do so.

Any recent changes on that node?