Re: [systemd-devel] Failed to mark scope session-20.scope as abandoned
On 5-12-14 15:11:46 Michal Sekletar wrote: 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]: Failed to mark scope session-20.scope as abandoned : Stale file handle 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! Heh. Reproducing was an interesting problem. Based on your suspicion, I created a crontab to run a couple of logger(1) commands every minute and then tried to create a lot of I/O on the system in the hope that I could recreate the race. Luckily, I caught it. I see systemd[1]: session-45.scope changed running - dead systemd[1]: Collecting session-45.scope happening in the log before systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Scope.Abandon() on /org/freedesktop/systemd1/unit/session_2d45_2escope systemd[1]: Failed to mark scope session-45.scope as abandoned : Stale file handle Is that the race? systemd[1]: Got D-Bus request: org.freedesktop.DBus.NameOwnerChanged() on /org/freedesktop/DBus systemd-logind[654]: Got message: org.freedesktop.DBus org.freedesktop.DBus NameOwnerChanged systemd-logind[654]: Got message: :1.117 org.freedesktop.login1.Manager CreateSession systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.StartTransientUnit() on /org/freedesktop/systemd1 systemd[1]: Failed to load configuration for session-45.scope: No such file or directory systemd[1]: SELinux access check scon=system_u:system_r:systemd_logind_t:s0 tcon=system_u:system_r:init_t:s0 tclass=service perm=start path=(null) cmdline=(null): 0 systemd[1]: SELinux access check scon=system_u:system_r:systemd_logind_t:s0 tcon=system_u:object_r:systemd_unit_file_t:s0 tclass=service perm=start path=/run/systemd/system/session-45.scope cmdline=(null): 0 systemd[1]: Trying to enqueue job session-45.scope/start/fail systemd[1]: Installed new job session-45.scope/start as 3401 systemd[1]: Enqueued job session-45.scope/start as 3401 systemd[1]: Starting Session 45 of user garry. systemd[1]: session-45.scope changed dead - running systemd[1]: Job session-45.scope/start finished, result=done systemd[1]: Started Session 45 of user garry. systemd[1]: Got D-Bus request: org.freedesktop.DBus.NameOwnerChanged() on /org/freedesktop/DBus systemd-logind[654]: New session 45 of user garry. systemd-logind[654]: Got message: org.freedesktop.DBus org.freedesktop.DBus NameOwnerChanged systemd-logind[654]: Got message: :1.118 org.freedesktop.login1.Manager CreateSession systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.StartTransientUnit() on /org/freedesktop/systemd1 systemd[1]: Failed to load configuration for session-44.scope: No such file or directory systemd[1]: SELinux access check scon=system_u:system_r:systemd_logind_t:s0 tcon=system_u:system_r:init_t:s0 tclass=service perm=start path=(null) cmdline=(null): 0 systemd[1]: SELinux access check scon=system_u:system_r:systemd_logind_t:s0 tcon=system_u:object_r:systemd_unit_file_t:s0 tclass=service perm=start path=/run/systemd/system/session-44.scope cmdline=(null): 0 systemd[1]: Trying to enqueue job session-44.scope/start/fail systemd[1]: Installed new job session-44.scope/start as 3407 systemd[1]: Enqueued job session-44.scope/start as 3407 systemd[1]: Starting Session 44 of user garry. systemd-logind[654]: New session 44 of user garry. systemd-logind[654]: Got message: :1.2 org.freedesktop.systemd1.Manager JobRemoved systemd[1]: session-44.scope changed dead - running systemd[1]: Job session-44.scope/start finished, result=done systemd[1]: Started Session 44 of user garry. systemd[1]: Got D-Bus request: org.freedesktop.DBus.NameOwnerChanged() on /org/freedesktop/DBus systemd-logind[654]: Got message: org.freedesktop.DBus org.freedesktop.DBus NameOwnerChanged systemd-logind[654]: Got message: :1.2 org.freedesktop.systemd1.Manager JobRemoved systemd-logind[654]: Got message: org.freedesktop.DBus org.freedesktop.DBus NameOwnerChanged systemd-logind[654]: Got message: org.freedesktop.DBus org.freedesktop.DBus NameOwnerChanged systemd-logind[654]: Got message: :1.119 org.freedesktop.login1.Manager ReleaseSession systemd-logind[654]: Got message: org.freedesktop.DBus org.freedesktop.DBus NameOwnerChanged systemd[1]: Got D-Bus request: org.freedesktop.DBus.NameOwnerChanged() on /org/freedesktop/DBus systemd[1]: Got D-Bus request: org.freedesktop.DBus.NameOwnerChanged() on /org/freedesktop/DBus systemd[1]: Got D-Bus request: org.freedesktop.DBus.NameOwnerChanged() on /org/freedesktop/DBus systemd[1]: Got D-Bus request
[systemd-devel] Failed to mark scope session-20.scope as abandoned
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@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@vfr$ /usr/lib/systemd/systemd --version systemd 208 +PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -- Garry T. Williams ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Duplicate Messages in Journal
On Friday, December 20, 2013 04:05:09 Zbigniew Jędrzejewski-Szmek wrote: On Thu, Dec 19, 2013 at 09:11:17PM -0500, Garry T. Williams wrote: I see these messages in my journal: Dec 19 20:58:57 tfr systemd[1]: Started Load/Save Screen Backlight Brightness of acpi_video0. Why is the message repeated so many times? Usually because something resets the brightness all the time and/or the kernel reports brightness levels through udev events. The journal itself has nothing to with this. OK, I get the bit about the journal. I found sort of the source of this: garry@tfr$ udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[6722.903153] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[6722.904958] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[6722.906931] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[6722.909084] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[6722.910965] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[6722.913139] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [6722.913336] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[6722.915996] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [6722.916708] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [6722.916778] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [6722.917165] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [6722.917525] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [6722.917986] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [6722.918265] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[6722.920045] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [6722.920410] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[6722.924880] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [6722.925270] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) ^C% garry@tfr$ I got this output by hitting (only once) Fn+F4. So, I guess it's the kernel reporting the event nine times. I wonder why that happens... -- Garry T. Williams ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Duplicate Messages in Journal
I see these messages in my journal: Dec 19 20:58:57 tfr systemd[1]: Started Load/Save Screen Backlight Brightness of acpi_video0. Dec 19 20:58:57 tfr systemd[1]: Started Load/Save Screen Backlight Brightness of acpi_video0. Dec 19 20:58:57 tfr systemd[1]: Started Load/Save Screen Backlight Brightness of acpi_video0. Dec 19 20:58:57 tfr systemd[1]: Started Load/Save Screen Backlight Brightness of acpi_video0. Dec 19 20:58:57 tfr systemd[1]: Started Load/Save Screen Backlight Brightness of acpi_video0. Dec 19 20:58:57 tfr systemd[1]: Started Load/Save Screen Backlight Brightness of acpi_video0. Dec 19 20:58:57 tfr systemd[1]: Started Load/Save Screen Backlight Brightness of acpi_video0. Dec 19 20:58:57 tfr systemd[1]: Started Load/Save Screen Backlight Brightness of acpi_video0. Dec 19 20:58:57 tfr systemd[1]: Started Load/Save Screen Backlight Brightness of acpi_video0. Why is the message repeated so many times? -- Garry T. Williams ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] /home Fails to Mount During Boot
Recently, my /home file system fails to mount during boot. The relevant message is: systemd[1]: Job dev-sda4.device/start timed out. systemd[1]: Timed out waiting for device dev-sda4.device. I'm dropped to a prompt for root's password and after receiving a shell prompt, the command mount /home completes without error and after exiting the shell the boot-up proceeds normally. This is sort of new behavior. I saw it once or twice during the last few months, but now, after updating to kernel 3.10.3-300.fc19.x86_64, it happens on each boot. How can I debug this problem? systemd-204-9.fc19.x86_64 kernel-3.10.3-300.fc19.x86_64 /etc/fstab: /dev/sda4 /home btrfs noatime 0 0 The /home file system is a raid1 btrfs across two identical drive partitions, sda4 and sdb4. Log: Jul 27 17:33:42 vfr systemd[1]: Mounted /boot. Jul 27 17:33:42 vfr kernel: EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jul 27 17:33:42 vfr kernel: SELinux: initialized (dev md0, type ext4), uses xattr Jul 27 17:35:08 vfr systemd[1]: Job dev-sda4.device/start timed out. Jul 27 17:35:08 vfr systemd[1]: Timed out waiting for device dev-sda4.device. Jul 27 17:35:08 vfr systemd[1]: Dependency failed for /home. Jul 27 17:35:08 vfr systemd[1]: Dependency failed for Local File Systems. Jul 27 17:35:08 vfr systemd[1]: Dependency failed for Mark the need to relabel after reboot. Jul 27 17:35:08 vfr systemd[1]: Dependency failed for Relabel all filesystems, if necessary. Jul 27 17:35:08 vfr systemd[1]: Triggering OnFailure= dependencies of local-fs.target. Jul 27 17:35:08 vfr systemd[1]: Stopped Daily Cleanup of Temporary Directories. Jul 27 17:35:08 vfr systemd[1]: Stopped IPv4 firewall with iptables. Jul 27 17:35:08 vfr systemd[1]: Stopped ABRT Xorg log watcher. Jul 27 17:35:08 vfr systemd[1]: Stopped CUPS Printer Service Spool. Jul 27 17:35:08 vfr alsactl[427]: alsactl 1.0.27.2 daemon started Jul 27 17:35:09 vfr systemd-journal[278]: Allowing system journal files to grow to 100.0M. Jul 27 17:35:08 vfr systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. Jul 27 17:35:08 vfr systemd[1]: Started Tell Plymouth To Write Out Runtime Data. Jul 27 17:35:08 vfr systemd[1]: Started Recreate Volatile Files and Directories. Jul 27 17:35:08 vfr systemd[1]: Started Security Auditing Service. Jul 27 17:35:08 vfr systemd[1]: Starting Update UTMP about System Runlevel Changes... Jul 27 17:35:08 vfr systemd[1]: Started Update UTMP about System Runlevel Changes. Jul 27 17:35:08 vfr systemd[1]: Startup finished in 1.311s (kernel) + 1.778s (initrd) + 1min 32.142s (userspace) = 1min 35.231s. Jul 27 17:35:08 vfr auditd[428]: Started dispatcher: /sbin/audispd pid: 438 Jul 27 17:35:08 vfr audispd[438]: priority_boost_parser called with: 4 Jul 27 17:35:08 vfr audispd[438]: max_restarts_parser called with: 10 Jul 27 17:35:08 vfr audispd[438]: audispd initialized with q_depth=120 and 1 active plugins Jul 27 17:35:08 vfr auditd[428]: Init complete, auditd 2.3.1 listening for events (startup state enable) Jul 27 17:35:08 vfr sedispatch[443]: Connection Error (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory): AVC Will be dropped Jul 27 17:35:08 vfr sedispatch[443]: Connection Error (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory): AVC Will be dropped Jul 27 17:35:13 vfr auditctl[429]: No rules Jul 27 17:35:13 vfr auditctl[429]: AUDIT_STATUS: enabled=0 flag=1 pid=0 rate_limit=0 backlog_limit=320 lost=0 backlog=0 Jul 27 17:35:13 vfr kernel: [127B blob data] Jul 27 17:35:38 vfr systemd[1]: Starting Stop Read-Ahead Data Collection... Jul 27 17:35:38 vfr systemd[1]: Started Stop Read-Ahead Data Collection. Jul 27 17:40:15 vfr kernel: device fsid 6c3aeff6-9a50-4481-a175-7b98980eb638 devid 1 transid 674749 /dev/sda4 Jul 27 17:40:15 vfr kernel: btrfs: disk space caching is enabled Jul 27 17:40:16 vfr kernel: SELinux: initialized (dev sdb4, type btrfs), uses xattr -- Garry T. Williams ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] shell-completion: fix zsh completion installation
On 7-26-13 00:41:11 Michael Biebl wrote: 2013/7/25 William Giokas 1007...@gmail.com: Moved zsh shell completion to shell-completion/zsh/_systemd for automake's sake. Also allow users to specify where the files should go with:: ./configure --with-zshcompletiondir=/path/to/some/where and by default going to `$datadir/zsh/site-functions` I was told [1], the directory for 3rd party packages would be /usr/share/zsh/vendor-completions. But I'm not a zsh user, so I'm just paroting what I read there. If it's any help, I am a zsh user and Fedora 19 has this file installed on my system: /usr/share/zsh/5.0.2/functions/_systemd My /usr/share/zsh/site-functions directory is empty. -- Garry T. Williams ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] /home Fails to Mount During Boot
On 7-28-13 01:14:55 Tom Gundersen wrote: On Sun, Jul 28, 2013 at 12:13 AM, Garry T. Williams gtwilli...@gmail.com wrote: /etc/fstab: /dev/sda4 /home btrfs noatime 0 0 The /home file system is a raid1 btrfs across two identical drive partitions, sda4 and sdb4. I believe you want to use UUID, rather than the name of one of your devices (see lsblk -f). Thanks. That seems to have done it. (It has been intermittent until this kernel.) I've had that entry in fstab for a long time -- probably two years. That's about when I first tried btrfs on /home. Is the use of /dev/sd* in the fstab racey in some way? -- Garry T. Williams ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] What Is Cannot Add Dependency Job?
What is Cannot add dependency job in my log and should I be fixing something? dmesg: -- [1.658225] systemd[1]: Cannot add dependency job for unit timers.target, ignoring: Unit timers.target failed to load: No such file or directory. See system logs and 'systemctl status timers.target' for details. [1.658239] systemd[1]: Cannot add dependency job for unit paths.target, ignoring: Unit paths.target failed to load: No such file or directory. See system logs and 'systemctl status paths.target' for details. This doesn't seem to help me either: garry@vfr$ systemctl status timers.target timers.target - Timers Loaded: loaded (/usr/lib/systemd/system/timers.target; static) Active: active since Sat 2013-04-27 11:41:54 EDT; 1h 14min ago Docs: man:systemd.special(7) Apr 27 11:42:00 vfr systemd[1]: Starting Timers. Apr 27 11:42:00 vfr systemd[1]: Reached target Timers. garry@vfr$ systemctl status paths.target paths.target - Paths Loaded: loaded (/usr/lib/systemd/system/paths.target; static) Active: active since Sat 2013-04-27 11:41:54 EDT; 1h 14min ago Docs: man:systemd.special(7) garry@vfr$ This is Fedora 18: garry@vfr$ uname -r 3.8.9-200.fc18.x86_64 garry@vfr$ rpm -q systemd systemd-201-2.fc18.2.x86_64 garry@vfr$ -- Garry T. Williams ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-readahead and often used applications
On 4-13-13 23:24:22 Reindl Harald wrote: Am 13.04.2013 23:08, schrieb Kok: A lot of things are possible and would help this: - change your system to auto-logon your account and start the applications for you. This is possible without any coding. well, that's a no-go You might be interested to know that when I set the option to log into a locked KDE desktop, I see all of the KDE desktop-related files in systemd-readahead analyze after two boots without changing the OnActiveSec=10s. This is truly effective. (I know this may not be possible for you, but I just wanted to note that the suggestion worked well here where I almost always log into the desktop. The rare occasion when I do not want that now means I am forced to log out immediately.) $ cat /etc/kde/kdm/kdmrc ... [X-:0-Core] AutoLoginEnable=true AutoLoginLocked=true AutoLoginUser=garry -- Garry T. Williams ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] How to Test systemd on F14?
I installed systemd on Fedora 14 and added init=/bin/systemd to my kernel boot parameters. Initially I had no problems: boot to graphical.target is fine. I wanted to run through the test cases I found at http://fedoraproject.org/wiki/QA:Testcase_initialization_basic http://fedoraproject.org/wiki/QA:Testcase_initialization_tools I encountered a problem that makes me think I'm missing something. ln -sf /lib/systemd/system/multi-user.target /etc/systemd/system/default.target reboot and now in terminal: ga...@vfr$ runlevel N 3 ga...@vfr$ But... [r...@vfr ~]# telinit 5 telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused [r...@vfr ~]# init 5 init: Failed to connect to socket /com/ubuntu/upstart: Connection refused [r...@vfr ~]# Now relink graphical.target, but reboot still to terminal. :-( Tried systemctl start graphical.target and got (in log): Dec 29 15:15:11 vfr systemd[1]: ge...@tty1.service/stop would stop a running service. Dec 29 15:15:11 vfr systemd[1]: Deleting ge...@tty1.service/stop to minimize impact. Is this supposed to work? How do I get back to the graphical target? -- Garry T. Williams ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to Test systemd on F14?
On Thursday, December 30, 2010 12:03:13 Tomasz Torcz wrote: On Thu, Dec 30, 2010 at 05:04:25PM +0100, Michał Piotrowski wrote: Hi, AFAIK systemd is not supported on F14 and now nobody cares. I think that if you want to test it on F14 you need to build a few things: - systemd - initscripts - udev - kernel (perhaps) Not really. I'm using systemd on most of my F14 machines. Packaged version (v10) is quite old and prone to bugs, but it works most of the time. Original poster problems can be solved by installing sysvinit-systemd package instead of sysvinit-upstart. Ah, I take it that I need to upgrade to rawhide if I want to do any meaningful testing. Thanks. -- Garry T. Williams ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
