Can not restart a service

[Innovip]

Dear all,

I just upgraded my machine from 5.4.XX to 6.3-6-6.3.
The new Proxmox environnement runs fine.

One some VMs, when I ssh and try, for instance to 'systemctl restart apache2' (or any other service), I get the following error:
---
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
---

It seems a bit strange, because the machines (Proxmox and VMs) are running OK..

Just in case this might help someone...
---
root@s4:~# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.103-1-pve)
pve-manager: 6.3-6 (running version: 6.3-6/2184247e)
pve-kernel-5.4: 6.3-7
pve-kernel-helper: 6.3-7
pve-kernel-5.4.103-1-pve: 5.4.103-1
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.18-12-pve: 4.15.18-36
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-5
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.10-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-6
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.2.0-3
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-8
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.3-pve2
root@s4:~# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.103-1-pve)
pve-manager: 6.3-6 (running version: 6.3-6/2184247e)
pve-kernel-5.4: 6.3-7
pve-kernel-helper: 6.3-7
pve-kernel-5.4.103-1-pve: 5.4.103-1
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.18-12-pve: 4.15.18-36
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-5
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.10-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-6
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.2.0-3
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-8
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.3-pve2
---

Thank you in advance if you spend some time for me...

 

[Stoiko Ivanov]

One some VMs, when I ssh and try, for instance to 'systemctl restart apache2'

* What kind of guests/VMs are showing this problem (Qemu-VM or lxc container)?
* Please share the config of a guest showing the problem
* Which OS is running inside the guest?

 

[Innovip]

Hello Stoiko,

Thank you for your help.
1- The only think that I can see is: throught the Proxmox console - options - QEMU agent : defautl (disabled). Where else can I check ?
2- What information do you need ? :-(
3- Debian 4.19.152-1

 

[Stoiko Ivanov]

The guest has a unique ID (VMID - e.g. 100)
please post the output of:
* `qm config <VMID>`
* `pct config <VMID>`
(only one of the commands will work)

 

[Innovip]

Here you are:
---
root@s4:~# qm config 101
bootdisk: scsi0
cores: 1
ide2: local:iso/debian-9.9.0-amd64-netinst.iso,media=cdrom
memory: 512
name: S6
net0: virtio=E6:7E:BF:10:E1:7E,bridge=vmbr1,firewall=1
numa: 0
onboot: 1
ostype: l26
scsi0: local-zfs:vm-101-disk-0,size=100G
scsihw: virtio-scsi-pci
smbios1: uuid=f6f278dd-e906-4536-8884-d787b71698ee
sockets: 1
vmgenid: 34d079bd-092f-4ccc-bde7-c8d993a2b7bb
---

 

[Stoiko Ivanov]

Given that this is a Qemu Virtual machine (running debian) I doubt that the reason for the error is related to the Proxmox upgrade:
Qemu VMs don't share the kernel with the hypervisor, but run as 'virtual computers'

-> Check the log/journal inside the VM - the issue is most likely only there

I hope this helps!