Ran system updates (apt-get update; apt-get -y dist-upgrade; apt-get autoremove; apt-get autoclean
and systems gets stuck building updated initramfs. Killing the 'update-initramfs' process results in it proceeding or retrying just to get stuck again.
Two nodes in the cluster are behaving like this. What debug information could I provide to identify the root cause?
Version information, as it's often requested:
and systems gets stuck building updated initramfs. Killing the 'update-initramfs' process results in it proceeding or retrying just to get stuck again.Two nodes in the cluster are behaving like this. What debug information could I provide to identify the root cause?
Code:
\_ sshd: admin@pts/0
| \_ -bash
| \_ apt-get autoremove
| \_ /usr/bin/dpkg --status-fd 26 --configure --pending
| \_ /usr/bin/perl -w /var/lib/dpkg/info/pve-kernel-4.13.13-5-pve.postinst configure 4.13.13-36
| \_ run-parts --verbose --exit-on-error --arg=4.13.13-5-pve --arg=/boot/vmlinuz-4.13.13-5-pve /etc/kernel/postinst.d
| \_ /bin/sh -e /etc/kernel/postinst.d/initramfs-tools 4.13.13-5-pve /boot/vmlinuz-4.13.13-5-pve
| \_ /bin/sh /usr/sbin/update-initramfs -c -t -k 4.13.13-5-pve -b /boot
| \_ syncVersion information, as it's often requested:
Code:
[root@kvm2 ~]# pveversion -v
proxmox-ve: not correctly installed (running kernel: 4.13.13-5-pve)
pve-manager: 5.1-43 (running version: 5.1-43/bdb08029)
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-20
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-16
pve-qemu-kvm: 2.9.1-6
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.4-pve2~bpo9