within 60
> seconds, and seems to hang at:
>
> "a stop job is running for User Manager for 0"
>
> The machine is still in single user mode, so I cannot get any more
> information out of it. The message is rather useless, because it does
> not tell me anything
On Sun, Feb 09, 2014 at 12:35:20PM +0530, Kashyap Chamarthy wrote:
[. . .]
> > The message is rather useless, because it does
> > not tell me anything about the problem. Which job is still running? What
> > is it waiting for? What's a User Manager? Who is "0"?
> >
> > I'm not even sure at what c
s not a netinstall, so something could be different in your
environment.
>
> Regularly, we get tests failing because the VM does not boot within 60
> seconds, and seems to hang at:
>
> "a stop job is running for User Manager for 0"
>
> The machine is still in sin
On Thu, 6 Feb 2014, Reindl Harald wrote:
which is user 0
that is yours, an not only yours
https://bugzilla.redhat.com/show_bug.cgi?id=1023820
This workaround solved my problem:
https://bugzilla.redhat.com/show_bug.cgi?id=1023788#c2
basically:
cat > /etc/systemd/system/sshd-shutdown.service
Am 06.02.2014 20:59, schrieb Paul Wouters:
> On Thu, 6 Feb 2014, Reindl Harald wrote:
>
>>> Regularly, we get tests failing because the VM does not boot within 60
>>> seconds, and seems to hang at:
>>>
>>> "a stop job is running for Us
On Thu, 6 Feb 2014, Reindl Harald wrote:
Regularly, we get tests failing because the VM does not boot within 60
seconds, and seems to hang at:
"a stop job is running for User Manager for 0"
here you go
https://bugzilla.redhat.com/show_bug.cgi?id=1023820
https://bugzilla.
ithin 60
> seconds, and seems to hang at:
>
> "a stop job is running for User Manager for 0"
here you go
https://bugzilla.redhat.com/show_bug.cgi?id=1023820
https://bugzilla.redhat.com/show_bug.cgi?id=1010572
https://bugzilla.redhat.com/show_bug.cgi?id=1057811
https://bugzill
I'm using a minimal netinstall version of fedora20 for testing using
KVM. We very often cycle these machines (once per test, we run hundreds
of tests)
Regularly, we get tests failing because the VM does not boot within 60
seconds, and seems to hang at:
"a stop job is runnin