<div dir="ltr"><div class="gmail_quote">On Thu, 7 May 2015 at 22:30 Michael Biebl <<a href="mailto:biebl@debian.org">biebl@debian.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So, systemd.postinst seems to fail in the trigger<br>
We do not call systemctl uncondionally here:<br>
<br>
_systemctl() {<br>
if [ -d /run/systemd/system ]; then<br>
systemctl "$@"<br>
fi<br>
}<br>
<br>
<br>
if [ "$1" = "triggered" ]; then<br>
_systemctl daemon-reload<br>
exit 0<br>
fi<br>
<br>
So, this looks like you (wrongly) had a /run/systemd/system directory at<br>
this point?<br></blockquote><div><br></div><div>Yes, looks like it:</div><div><br></div><div>root@scrooge:/# ls -la /run/systemd/system/ total 0 drwxr-xr-x 2 root root 40 May 8 02:50 . drwxr-xr-x 6 root root 180 May 8 02:50 .. </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That said, I'm still curious, why the systemctl call was made in the<br>
first place. systemctl also complains with a D-Bus error.<br>
Did you have a /var/run/dbus/system_bus_socket?</blockquote><div><br></div><div>Doesn't look like I have that:</div><div><br></div><div>root@scrooge:/# ls -la /var/run/</div><div>total 4</div><div>drwxr-xr-x 4 root root 80 May 8 02:50 .</div><div>drwxr-xr-x 20 root root 4096 May 8 02:50 ..</div><div>drwxrwxrwt 2 root root 40 May 8 02:50 lock</div><div>drwxr-xr-x 6 root root 180 May 8 02:50 systemd</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> If that socket does not<br>
exist, systemctl should fall back to use a private dbus socket which<br>
doesn't require a run dbus system bus.<br>
Was dbus installed at this point dbus.service and dbus.socket correctly<br>
running?<br></blockquote><div><br></div><div>dbus is installed, however it is not running. In fact I think systemd hasn't actually started anything.</div><div><br></div><div><div>root@scrooge:/# ps aufx</div><div>USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND</div><div>root 1 0.0 0.4 4892 2140 ? Ss 02:50 0:00 init -z</div><div>root 2 0.0 0.0 0 0 ? S 02:50 0:00 [kthreadd/104]</div><div>root 3 0.0 0.0 0 0 ? S 02:50 0:00 \_ [khelper/104]</div><div>root 47 0.0 0.1 25540 708 ? Ss 02:51 0:00 vzctl: pts/0</div><div>root 48 0.0 0.4 4296 2612 pts/0 Ss 02:51 0:00 \_ -bash</div><div>root 387 0.0 0.1 2872 916 pts/0 R+ 03:04 0:00 \_ ps aufx</div><div>root@scrooge:/#</div></div><div><br></div><div>I suspect systemd might be trying to display something on the console, however I am not sure how to display that stuff using openvz/proxmox (thought there was a way...)</div><div><br></div><div>I think systemd has got into a very strange state, where it thinks it has started, but it isn't really running properly, and as such hasn't started anything it was suppose to.</div><div><br></div><div>Also, not just systemd that can trigger this problem (also: does the following really mean hplip and colord can't be installed without systemd?)</div><div><br></div><div><div>root@scrooge:/var/log# apt-get install systemd</div><div>Reading package lists... Done</div><div>Building dependency tree</div><div>Reading state information... Done</div><div>systemd is already the newest version.</div><div>systemd set to manually installed.</div><div>The following packages were automatically installed and are no longer required:</div><div> consolekit hpijs libck-connector0 libcolord1 libffi5 libgd2-xpm libgphoto2-2 libgphoto2-port0 libjpeg8 liblcms1 libopenjpeg2</div><div> libpam-ck-connector libpoppler19 libslp1 libsystemd-login0 libtiff4 pciutils ttf-freefont usbutils</div><div>Use 'apt-get autoremove' to remove them.</div><div>0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.</div><div>root@scrooge:/var/log# ls^C</div><div>(reverse-i-search)`': ^C</div><div>root@scrooge:/var/log# apt-get remove systemd</div><div>Reading package lists... Done</div><div>Building dependency tree</div><div>Reading state information... Done</div><div>The following packages were automatically installed and are no longer required:</div><div> avahi-daemon colord-data consolekit cups cups-browsed cups-client cups-core-drivers cups-daemon cups-filters cups-filters-core-drivers</div><div> cups-ppdc cups-server-common dconf-gsettings-backend dconf-service foomatic-db-compressed-ppds foomatic-db-engine gir1.2-glib-2.0</div><div> hpijs hplip-data libart-2.0-2 libasn1-8-heimdal libavahi-core7 libavahi-glib1 libck-connector0 libcolord1 libcolord2 libcolorhug2</div><div> libcupscgi1 libcupsmime1 libcupsppdc1 libdaemon0 libdbus-glib-1-2 libdconf1 libexif12 libffi5 libfile-copy-recursive-perl</div><div> libfontembed1 libgd2-xpm libgd3 libgirepository-1.0-1 libgphoto2-2 libgphoto2-6 libgphoto2-l10n libgphoto2-port0 libgphoto2-port10</div><div> libgssapi3-heimdal libgudev-1.0-0 libgusb2 libgutenprint2 libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhpmud0</div><div> libhx509-5-heimdal libieee1284-3 libjim0.75 libjpeg8 libkrb5-26-heimdal liblcms1 libldb1 libltdl7 libnss-mdns libntdb1 libopenjpeg2</div><div> libpam-ck-connector libperl5.20 libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 libpoppler19 libpython2.7 libqpdf13</div><div> libroken18-heimdal libsane libsane-common libsane-extras libsane-extras-common libsane-hpaio libsensors4 libslp1 libsmbclient</div><div> libsnmp-base libsnmp30 libsystemd-login0 libtalloc2 libtcl8.6 libtdb1 libtevent0 libtiff4 libtk8.6 libusb-1.0-0 libv4l-0</div><div> libv4lconvert0 libvpx1 libwbclient0 libwind0-heimdal libxss1 mscompress pciutils printer-driver-all printer-driver-brlaser</div><div> printer-driver-c2050 printer-driver-c2esp printer-driver-cjet printer-driver-dymo printer-driver-escpr printer-driver-foo2zjs</div><div> printer-driver-foo2zjs-common printer-driver-gutenprint printer-driver-hpcups printer-driver-hpijs printer-driver-m2300w</div><div> printer-driver-min12xxw printer-driver-pnm2ppa printer-driver-ptouch printer-driver-pxljr printer-driver-sag-gdi printer-driver-splix</div><div> python-crypto python-dbus python-dbus-dev python-gi python-gobject-2 python-imaging python-ldb python-ntdb python-pexpect</div><div> python-renderpm python-reportlab python-reportlab-accel python-samba python-talloc python-tdb qpdf samba-common samba-common-bin</div><div> samba-libs sane-utils smbclient tcl tcl8.6 tk tk8.6 ttf-freefont unzip update-inetd usb-modeswitch usb-modeswitch-data usbutils</div><div>Use 'apt-get autoremove' to remove them.</div><div>The following extra packages will be installed:</div><div> sysvinit-core</div><div>The following packages will be REMOVED:</div><div> colord hplip libpam-systemd policykit-1 printer-driver-postscript-hp systemd systemd-sysv</div><div>The following NEW packages will be installed:</div><div> sysvinit-core</div><div>0 upgraded, 1 newly installed, 7 to remove and 1 not upgraded.</div><div>Need to get 133 kB of archives.</div><div>After this operation, 14.7 MB disk space will be freed.</div><div>Do you want to continue? [Y/n] y</div><div>Get:1 <a href="http://proxy.pri:9999/debian/">http://proxy.pri:9999/debian/</a> jessie/main sysvinit-core i386 2.88dsf-59 [133 kB]</div><div>Fetched 133 kB in 0s (2306 kB/s)</div><div>Preconfiguring packages ...</div><div>(Reading database ... 32441 files and directories currently installed.)</div><div>Removing colord (1.2.1-1+b2) ...</div><div>Failed to get D-Bus connection: No such file or directory</div><div>dpkg: error processing package colord (--remove):</div><div> subprocess installed pre-removal script returned error exit status 1</div><div>Failed to get D-Bus connection: No such file or directory</div><div>Failed to get D-Bus connection: No such file or directory</div><div>Removing printer-driver-postscript-hp (3.14.6-1) ...</div><div>Removing hplip (3.14.6-1+b2) ...</div><div>dpkg: policykit-1: dependency problems, but removing anyway as you requested:</div><div> colord depends on policykit-1 (>= 0.103).</div><div><br></div><div>Removing policykit-1 (0.105-8) ...</div><div>Removing libpam-systemd:i386 (215-17) ...</div><div>dpkg: systemd-sysv: dependency problems, but removing anyway as you requested:</div><div> init depends on systemd-sysv | sysvinit-core | upstart; however:</div><div> Package systemd-sysv is to be removed.</div><div> Package sysvinit-core is not installed.</div><div> Package upstart is not installed.</div><div><br></div><div>Removing systemd-sysv (215-17) ...</div><div>Processing triggers for cups (1.7.5-11) ...</div><div>Processing triggers for dbus (1.8.16-1) ...</div><div>Processing triggers for man-db (2.7.0.2-5) ...</div><div>Errors were encountered while processing:</div><div> colord</div><div>E: Sub-process /usr/bin/dpkg returned an error code (1)</div><div>root@scrooge:/var/log#</div></div><div><br></div><div><br></div><div>Which in turn starts getting a bit messy:</div><div><br></div><div><div>root@scrooge:/var/log# apt-get remove systemd</div><div>Reading package lists... Done</div><div>Building dependency tree</div><div>Reading state information... Done</div><div>You might want to run 'apt-get -f install' to correct these:</div><div>The following packages have unmet dependencies:</div><div> colord : Depends: policykit-1 (>= 0.103) but it is not going to be installed</div><div> init : PreDepends: systemd-sysv but it is not going to be installed or</div><div> sysvinit-core but it is not going to be installed or</div><div> upstart but it is not going to be installed</div><div>E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).</div><div><br></div></div><div>In this case following the recommended advice reinstalls systemd, which was kind of the opposite direction of what I was hoping for...</div><div><br></div><div><br></div><div><br></div><div>At some stage I will need to upgrade the kernel on this box, that will support systemd properly (according to other reports), however will wait and see if you need any more information on first.</div><div><br></div><div>Regards</div></div></div>