[systemd-devel] Failed to mark scope session-20.scope as abandoned

Michal Sekletar msekleta at redhat.com
Mon May 12 06:11:46 PDT 2014


On Sat, May 10, 2014 at 05:12:21PM -0400, Garry T. Williams wrote:
> This recently stated showing up in the journal on Fedora F20 here:
> 
>     May 10 17:01:01 vfr systemd[1]: Starting Session 20 of user root.
>     May 10 17:01:01 vfr systemd[1]: Started Session 20 of user root.
>     May 10 17:01:01 vfr CROND[5035]: (root) CMD (run-parts /etc/cron.hourly)
>     May 10 17:01:01 vfr run-parts[5039]: (/etc/cron.hourly) starting 0anacron
>     May 10 17:01:01 vfr run-parts[5052]: (/etc/cron.hourly) finished 0anacron
>     May 10 17:01:01 vfr run-parts[5054]: (/etc/cron.hourly) starting ghc-doc-index
>     May 10 17:01:01 vfr run-parts[5065]: (/etc/cron.hourly) finished ghc-doc-index
>     May 10 17:01:01 vfr run-parts[5067]: (/etc/cron.hourly) starting mcelog.cron
>     May 10 17:01:01 vfr run-parts[5071]: (/etc/cron.hourly) finished mcelog.cron
>     May 10 17:01:01 vfr systemd[1]: Failed to mark scope session-20.scope as abandoned : Stale file handle
> 
> It seems benign.  I just haven't seen it before and thought it may be
> worth reporting here.
> 
>     garry at vfr$ journalctl|grep 'Failed to mark scope'
>     Apr 19 19:01:02 vfr systemd[1]: Failed to mark scope session-2.scope as abandoned : Stale file handle
>     May 05 22:01:02 vfr systemd[1]: Failed to mark scope session-59.scope as abandoned : Stale file handle
>     May 10 17:01:01 vfr systemd[1]: Failed to mark scope session-20.scope as abandoned : Stale file handle
>     garry at vfr$ /usr/lib/systemd/systemd --version
>     systemd 208
>     +PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
> 

I suspect this is caused by race between systemd realizing that cgroup for a scope
is empty, thus changing its state, and dispatching dbus message coming from
logind where it asks systemd to mark scope as abandoned. I don't think this is a
big deal so we could log this only if debug is on.

To make sure if it is the case can you try to reproduce with systemd and logind
debug turned on. Thanks!

Michal
> -- 
> Garry T. Williams
> 
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel


More information about the systemd-devel mailing list