I'm running proxmox (Latest community) on a Hp micro server gen 8.
Every time i create a new CT and start it, I get this error:
<root@pam> end task UPID:local1:000079DF:007F34B9:5AC8B6C3:vzstart:103:root@pam: command 'systemctl start pve-container@103' failed: exit code 1
And nothing else in syslog.
Shortly after, the whole proxmox cluster starts breaking down - CT's become unaccessible and i cannot restart any of the Proxmox services - the only "solution" is a restart. After that, i can start the current containers and the newly created one.
I have no idea where to start looking for issues.
Solved:
The issue was ACPI errors, didn't think that they would cause issues but they did.
echo "blacklist acpi_power_meter" >> /etc/modprobe.d/hwmon.conf
echo "blacklist pcspkr" >> /etc/modprobe.d/blacklist.conf
Adding that to config files makes the errors no longer show in the Syslog and the error no longer occurs.
Every time i create a new CT and start it, I get this error:
<root@pam> end task UPID:local1:000079DF:007F34B9:5AC8B6C3:vzstart:103:root@pam: command 'systemctl start pve-container@103' failed: exit code 1
And nothing else in syslog.
Shortly after, the whole proxmox cluster starts breaking down - CT's become unaccessible and i cannot restart any of the Proxmox services - the only "solution" is a restart. After that, i can start the current containers and the newly created one.
I have no idea where to start looking for issues.
Code:
root@local1:~# pveversion
pve-manager/5.1-46/ae8241d4 (running kernel: 4.13.16-1-pve)
root@local1:~# pveversion -v
proxmox-ve: 5.1-42 (running kernel: 4.13.16-1-pve)
pve-manager: 5.1-46 (running version: 5.1-46/ae8241d4)
pve-kernel-4.13: 5.1-43
pve-kernel-4.13.16-1-pve: 4.13.16-45
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-1-pve: 4.13.13-31
pve-kernel-4.10.17-2-pve: 4.10.17-20
corosync: 2.4.2-pve3
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-common-perl: 5.0-28
libpve-guest-common-perl: 2.0-14
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-17
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 2.1.1-3
lxcfs: 2.0.8-2
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-11
pve-cluster: 5.0-20
pve-container: 2.0-19
pve-docs: 5.1-16
pve-firewall: 3.0-5
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.9.1-9
pve-xtermjs: 1.0-2
qemu-server: 5.0-22
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.6-pve1~bpo9Solved:
The issue was ACPI errors, didn't think that they would cause issues but they did.
echo "blacklist acpi_power_meter" >> /etc/modprobe.d/hwmon.conf
echo "blacklist pcspkr" >> /etc/modprobe.d/blacklist.conf
Adding that to config files makes the errors no longer show in the Syslog and the error no longer occurs.
Last edited: