[systemd-devel] reboot during booting up

Dangyi Liu dliu at redhat.com
Sun Nov 15 18:14:48 PST 2015


On Fri, 2015-11-13 at 13:10 +0100, Lennart Poettering wrote:
> On Fri, 13.11.15 17:41, Dangyi Liu (dliu at redhat.com) wrote:
> 
> > Hello.
> > 
> > I'm from Fedora kdump team and we found that in the latest verson
> > of
> > systemd, it's no longer legal to call reboot during system booting
> > up.
> > It complains
> > 
> > > Transaction contains conflicting jobs 'stop' and 'start' for
> > > shutdown.target.
> > 
> > I'm wondering whether it's possible to do so because I've checked
> > almost all related services and added "DefaultDependencies=no" for
> > them, but it never works. 
> 
> How do you issue the reboot call?

By calling "/bin/reboot" in a shell script.

> This should really work. Basically, there's a mode how you can
> enqueue
> jobs systemd shall execute, called "replace-irreversibly". Reboot
> requests are generally enqueued this way. This mode ensures that when
> later on contradicting jobs are enqueued that later transaction will
> fail instead of the older reboot transaction...

It seems the problem is that reboot contradicts some enqueued jobs, not
later transaction contradicts reboot job.

> Most likely when you run into this you already have some transaction
> of this kind enqueued, but the question is why. "systemctl dump"
> shows
> you all queued jobs (and more) and the Irreversible flag for each.

It tells me there's no operation 'dump' for systemctl..

> Lennart
> 


More information about the systemd-devel mailing list