On Wed, Aug 06, 2014 at 04:09:56PM -0700, Marc J. Driftmeyer wrote: > Package: libvirt-daemon-system > Version: 1.2.7-3 > Severity: normal > > Dear Maintainer, > > Today's install resulted in a broken libvirt installation.
Install means "dist-upgrade" ? > Output: > > mdriftmeyer@horus:/etc/init.d$ sudo systemctl status libvirtd.service > libvirtd.service - Virtualization daemon > Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled) > Active: failed (Result: start-limit) since Wed 2014-08-06 16:03:13 PDT; > 21s ago > Docs: man:libvirtd(8) > http://libvirt.org > Process: 16200 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited, > status=1/FAILURE) > Main PID: 16200 (code=exited, status=1/FAILURE) > > Aug 06 16:03:13 horus systemd[1]: Failed to start Virtualization daemon. > Aug 06 16:03:13 horus systemd[1]: Unit libvirtd.service entered failed > state. > Aug 06 16:03:13 horus systemd[1]: libvirtd.service holdoff time over, > sched...t. > Aug 06 16:03:13 horus systemd[1]: Stopping Virtualization daemon... > Aug 06 16:03:13 horus systemd[1]: Starting Virtualization daemon... > Aug 06 16:03:13 horus systemd[1]: libvirtd.service start request repeated > t...t. > Aug 06 16:03:13 horus systemd[1]: Failed to start Virtualization daemon. > Aug 06 16:03:13 horus systemd[1]: Unit libvirtd.service entered failed > state. > Hint: Some lines were ellipsized, use -l to show in full. > mdriftmeyer@horus:/etc/init.d$ sudo systemctl start libvirtd.service > Job for libvirtd.service failed. See 'systemctl status libvirtd.service' and > 'journalctl -xn' for details. > mdriftmeyer@horus:/etc/init.d$ sudo journalctl -xn > -- Logs begin at Sat 2014-08-02 19:02:24 PDT, end at Wed 2014-08-06 16:04:19 > PDT > Aug 06 16:04:03 horus systemd[1]: Unit libvirtd.service entered failed > state. > Aug 06 16:04:03 horus systemd[1]: libvirtd.service holdoff time over, > scheduling > Aug 06 16:04:03 horus systemd[1]: Cannot add dependency job for unit > uuidd.socke This looks odd. > Aug 06 16:04:03 horus systemd[1]: Stopping Virtualization daemon... > -- Subject: Unit libvirtd.service has begun shutting down > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit libvirtd.service has begun shutting down. > Aug 06 16:04:03 horus systemd[1]: Starting Virtualization daemon... > -- Subject: Unit libvirtd.service has begun with start-up > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit libvirtd.service has begun starting up. > Aug 06 16:04:03 horus systemd[1]: libvirtd.service start request repeated > too qu > Aug 06 16:04:03 horus systemd[1]: Failed to start Virtualization daemon. > -- Subject: Unit libvirtd.service has failed > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit libvirtd.service has failed. > -- > -- The result is failed. > Aug 06 16:04:03 horus systemd[1]: Unit libvirtd.service entered failed > state. > Aug 06 16:04:19 horus sudo[16228]: mdriftmeyer : TTY=pts/1 ; PWD=/etc/init.d > ; U > Aug 06 16:04:19 horus sudo[16228]: pam_unix(sudo:session): session opened > for us > lines 6-28/28 (END) This doesn't make much sense to me yet. Could you attach the output of journalctl /usr/sbin/libvirtd Could you also attach syslog from around 16:04:19? If all alse fails could you do a: /usr/sbin/libvirtd Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org