Is Proxmox v4 depending on systemd?

PMoxSudo

New Member
Jan 27, 2016
21
0
1
I've just installed deb 7.9 from the amd64 netinstall with system utils and ssh server, installed sysvinit according to http://hydra.geht.net/tino/english/faq/debian/apt/jessie/ to get jessie without systemd.

I've then dist-upgraded to jessie and it seems pve fails to configure itself after installation.

I've installed pve4 on jessie(with systemd) with the following script without issues before:
Code:
sudo touch /etc/apt/sources.list.d/pve-install-repo.list
sudo bash -c "echo 'deb [arch=amd64] http://download.proxmox.com/debian jessie p ve-no-subscription' > /etc/apt/sources.list.d/pve-install-repo.list"
sudo wget -O- "http://download.proxmox.com/debian/key.asc" | sudo apt-key add -
sudo apt-get update
sudo apt-get dist-upgrade -y
sudo apt-get purge exim4 bind9* vim -y
sudo apt-get install curl htop iftop tcpdump proxmox-ve ntp ssh postfix ksm-cont rol-daemon open-iscsi tcpdump -y
sudo reboot

However, I get the following error:

apt-get upgrade:
Code:
root@pve4:~# apt-get upgrade -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up pve-manager (4.1-13) ...
Failed to get D-Bus connection: Unknown error -1
Failed to get D-Bus connection: Unknown error -1
dpkg: error processing package pve-manager (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
  Package pve-manager is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

apt-get install -f:
Code:
root@pve4:~# apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up pve-manager (4.1-13) ...
Failed to get D-Bus connection: Unknown error -1
Failed to get D-Bus connection: Unknown error -1
dpkg: error processing package pve-manager (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
  Package pve-manager is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

D-Bus status. I'm looking at the error code right now https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763299:
Code:
root@pve4:/home/sudo# /etc/init.d/dbus status
dbus is running.

Looks like that post is self-explaining:
Code:
You are using sysvinit as PID 1 as shown by the status message of the
dbus service. So the error message you get from systemctl is not suprising.

Closing the bug report.

There's still some systemd on my system:
Code:
root@pve4:~# systemd
Trying to run as user instance, but the system has not been booted with systemd.

I get what the error is because I don't want systemd as init daemon.

Call me whatever you want, but it looks like it's not possible to install pve without systemd as init daemon.

I'm not an expert by any means, but I've managed to install pve a few times and this is a new error I've not seen before.

Static IP:
Code:
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#allow-hotplug eth0
#iface eth0 inet dhcp

auto eth0
iface eth0 inet static
        address 10.0.10.106
        netmask 255.255.255.0
        gateway 10.0.10.1

/etc/hosts:
Code:
127.0.0.1       localhost
10.0.10.106     pve4.debian     pve4

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

/etc/hostname:
Code:
pve4.debian

Unable to connect on web interface(obviously, seems install can't configure itself for some reason.

Anyone can confirm that this happens because of systemd not being the init daemon?
 
Last edited:
Ok, I've looked at the proxmox hypervisor that's running this PVE systemd-less v4 VM and tried to start/restart all pve processes that I've found on the host.

Code:
root@pve4:/home# pvestatd restart
Failed to get D-Bus connection: Unknown error -1
command 'systemctl reload-or-restart pvestatd' failed: exit code 1


root@pve4:/home/# pvedaemon restart
Failed to get D-Bus connection: Unknown error -1
command 'systemctl reload-or-restart pvedaemon' failed: exit code 1


root@pve4:/home# pve-ha-crm start
Failed to get D-Bus connection: Unknown error -1
command 'systemctl start pve-ha-crm' failed: exit code 1

root@pve4:/home/# pve-ha-lrm start
Failed to get D-Bus connection: Unknown error -1
command 'systemctl start pve-ha-lrm' failed: exit code 1

root@pve4:/home/# pveproxy start
Failed to get D-Bus connection: Unknown error -1
command 'systemctl start pveproxy' failed: exit code 1
root@pve4:/home/# pveproxy restart
Failed to get D-Bus connection: Unknown error -1
command 'systemctl reload-or-restart pveproxy' failed: exit code 1

root@pve4:/home/# pveproxy restart
Failed to get D-Bus connection: Unknown error -1
command 'systemctl reload-or-restart pveproxy' failed: exit code 1

All conclusions lead to systemd being a requirement. Fine, I give up.

All I ask is you support sysvinit in v4, but it won't likely happen.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!