possibly problem with rawhide (systemd-217?): "Found ordering cycle on basic.target/start"
i.gnatenko.brain at gmail.com
Fri Oct 31 15:57:58 UTC 2014
systemd-logind: failed to get session: PID 879 doesnt belong to any known
On Oct 31, 2014 7:31 PM, "Lennart Poettering" <mzerqung at 0pointer.de> wrote:
> On Fri, 31.10.14 16:20, Lennart Poettering (mzerqung at 0pointer.de) wrote:
> > On Fri, 31.10.14 16:13, Michal Schmidt (mschmidt at redhat.com) wrote:
> > > On 10/31/2014 03:42 PM, Kevin Fenzi wrote:
> > > > On Fri, 31 Oct 2014 14:01:12 +0100
> > > > Lennart Poettering <mzerqung at 0pointer.de> wrote:
> > > >
> > > >> So the problem appears to be that gssproxy.service been ordered
> > > >> remote-fs-pre.target. That target is ordered before
> > > >> basic.target. However gssproxy.service also is ordered after
> > > >> basic.target (simply because all services by default are ordered
> > > >> before basic.target, unless they explicitly specify
> > > >> DefaultDependencies=no), hence there's an ordering cycle.
> > > >>
> > > >> Most likely some NFS maintainers tried to move gss-proxy.service
> > > >> the early boot, and didn't set DefaultDependencies=no.
> > > >>
> > > >> That said, services running in early boot must be written in a
> > > >> specific style (i.e. not assume /var to be around, and suchlike), I
> > > >> do wonder if gssproxy is ready for that.
> > > >>
> > > >> Anyway, long story short: file a bug against the gssproxy package.
> > > >
> > > > I don't think this explains all the problems folks are having with
> > > > systemd-217.
> > >
> > > I wonder if the new ordering dependency between
> > > systemd-journal-flush.service and systemd-tmpfiles-setup.service
> > > (added in 74055aa76 "journalctl: add new --flush command and make use
> > > of it in systemd-journal-flush.service") participates in the ordering
> > > cycles.
> > Ahh, indeed. It moves remote-fs.target into the early-boot where it
> > doesn't belong.
> > My fault.
> > Will drop the remote-fs.target dep from the flush service.
> > Thanks for tracking this down.
> Would be good if somebody who ran into this problem could check if
> this change fixes it:
> (the actual commit unfortunately contains an unrelated change to
> nspawn, I fucked that up, sorry. Ignore everything but the change to
> Lennart Poettering, Red Hat
> devel mailing list
> devel at lists.fedoraproject.org
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the devel