Your message dated Sat, 24 Mar 2018 22:44:21 +0100
with message-id <3a7169f2-aa23-2f81-0733-e2437bc4f...@debian.org>
and subject line Re: systemd-machined: error: error from service: 
CreateMachine: Activation of org.freedesktop.machine1 timed out
has caused the Debian Bug report #799922,
regarding systemd-machined: error: error from service: CreateMachine: 
Activation of org.freedesktop.machine1 timed out
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
799922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 215-17+deb8u2
Severity: normal
File: systemd-machined

Dear Maintainer,

when trying to re-start a guest machine (doing virsh shutdown to use
new library files in the qemu process), startup via
"virsh start <machine>" failed:

error: Failed to start domain <machine>
error: error from service: CreateMachine: Activation of 
org.freedesktop.machine1 timed out


The host in question is up for around 40 days. It seems as if libvirt
needs some dbus connection and systemd-machined for guest
startup. Restarting systemd-machined via "service systemd-machined
restart" cleared the situation.

So obviously, some sort of communication between systemd and dbus was
lost unnoticed - maybe by recent library upgrades and daemon restarts
by needrestart? Maybe some restart dependency is broken?


Yours sincerely
Matthias Merz

-- Package-specific info:

-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/48 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  acl             2.2.52-2
ii  adduser         3.113+nmu3
ii  initscripts     2.88dsf-59
ii  libacl1         2.2.52-2
ii  libaudit1       1:2.4-1+b1
ii  libblkid1       2.25.2-6
ii  libc6           2.19-18+deb8u1
ii  libcap2         1:2.24-8
ii  libcap2-bin     1:2.24-8
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20     1.6.3-2
ii  libkmod2        18-3
ii  liblzma5        5.1.1alpha+20120614-2+b3
ii  libpam0g        1.1.8-3.1
ii  libselinux1     2.3-2
ii  libsystemd0     215-17+deb8u2
ii  mount           2.25.2-6
ii  sysv-rc         2.88dsf-59
ii  udev            215-17+deb8u2
ii  util-linux      2.25.2-6

Versions of packages systemd recommends:
ii  dbus            1.8.20-0+deb8u1
ii  libpam-systemd  215-17+deb8u2

Versions of packages systemd suggests:
pn  systemd-ui  <none>

-- Configuration Files:
/etc/systemd/system.conf changed:
[Manager]
ShowStatus=yes


-- no debconf information

--- End Message ---
--- Begin Message ---
On Fri, 2 Jun 2017 03:01:22 +0200 Michael Biebl <bi...@debian.org> wrote:
> Control: tags -1 + moreinfo
> 
> Hi Matthias
> 
> On Thu, 24 Sep 2015 11:11:23 +0200 Matthias Merz <deb...@merz-ka.de> wrote:
> > Package: systemd
> > Version: 215-17+deb8u2
> > Severity: normal
> > File: systemd-machined
> > 
> > Dear Maintainer,
> > 
> > when trying to re-start a guest machine (doing virsh shutdown to use
> > new library files in the qemu process), startup via
> > "virsh start <machine>" failed:
> > 
> > error: Failed to start domain <machine>
> > error: error from service: CreateMachine: Activation of 
> > org.freedesktop.machine1 timed out
> > 
> > 
> > The host in question is up for around 40 days. It seems as if libvirt
> > needs some dbus connection and systemd-machined for guest
> > startup. Restarting systemd-machined via "service systemd-machined
> > restart" cleared the situation.
> > 
> > So obviously, some sort of communication between systemd and dbus was
> > lost unnoticed - maybe by recent library upgrades and daemon restarts
> > by needrestart? Maybe some restart dependency is broken?
> 
> Sorry for not getting back to you earlier.
> Is this still a problem you can reproduce? If so, I'd send you further
> instructions how to debug this.

I revisited this old bug report and with the given information I was
unable to reproduce the issue. So I'm going to close it.

Please report back, if you still run into this issue with an up-to-date
stretch system. We can then reopen the bug report.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Reply via email to