Hello, If I upgrade a Jessie openvz container on my proxmox box, systemd fails to start up. This is no surprise, the kernel seems to be rather old:
root@scrooge:/# uname -a Linux scrooge 2.6.32-26-pve #1 SMP Mon Oct 14 08:22:20 CEST 2013 i686 GNU/Linux Obviously, I should have set things up not to install systemd before I did the upgrade. However, I want to fix this container. So, lets try: root@scrooge:/# apt-get remove systemd-sysv Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: cgmanager libcgmanager0 libnih-dbus1 libnih1 systemd-shim sysvinit-core Suggested packages: pm-utils The following packages will be REMOVED: systemd-sysv The following NEW packages will be installed: cgmanager libcgmanager0 libnih-dbus1 libnih1 systemd-shim sysvinit-core 0 upgraded, 6 newly installed, 1 to remove and 1 not upgraded. Need to get 493 kB of archives. After this operation, 1074 kB of additional disk space will be used. Do you want to continue? [Y/n] y Adding 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' Unpacking systemd-shim (9-1) ... Processing triggers for systemd (215-17) ... Failed to get D-Bus connection: No such file or directory dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for man-db (2.7.0.2-5) ... Processing triggers for dbus (1.8.16-1) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) Furthermore, when I did this on the 21st of April, I noticed some other packages can also generate similar errors (hplip, printer-driver-postscript-hp, and color IIRC, which to my surprise all require systemd; althought I don't need them; it is possible these problems are now fixed however since Jessie was released (it seems that the above apt-get command doesn't remove libpam-systemd any more so those packages don't get removed). For this particular case, when reproduced today, the solution seems to be simple: ln -sf /bin/true /bin/systemctl apt-get remove systemd-sysv Is this the thing I should be filling bug reports about? (I hope this doesn't generate a systemd flamewar here, that isn't my intention; also I have solved the problem with my broken VM, so don't need help here.) Regards
