FS#40970 - [systemd] Units don't log their activity to the journal after systemd 214 upgrade
Attached to Project:
Arch Linux
Opened by Davor Rotim (drot) - Wednesday, 25 June 2014, 11:04 GMT
Last edited by Dave Reisner (falconindy) - Friday, 04 July 2014, 13:43 GMT
Opened by Davor Rotim (drot) - Wednesday, 25 June 2014, 11:04 GMT
Last edited by Dave Reisner (falconindy) - Friday, 04 July 2014, 13:43 GMT
|
Details
Description:
After upgrading to systemd 214 certain units like systemd-networkd or cups don't log their activity to the journal anymore (journalctl -u only shows entries before the systemd 214 update). Additional info: * package version(s) systemd 214-2 3.15.1-1-ARCH i686 * config and/or log files etc. journalctl -u systemd-journald.service: http://sprunge.us/LAUD journalctl -u systemd-networkd.service: http://sprunge.us/CLgC journalctl -u systemd-logind.service: http://sprunge.us/SHLU Steps to reproduce: I don't have reliable steps to reproduce this (besides upgrading to 214), but I did notice yesterday while doing a new install (with systemd 214 of course) that logging to journal worked normally at first (as you can see from the pasted logs) but then it somehow stopped after I set up systemd-networkd (before the connection was established with the dhcpcd.service). |
This task depends upon
Closed by Dave Reisner (falconindy)
Friday, 04 July 2014, 13:43 GMT
Reason for closing: Not a bug
Additional comments about closing: No evidence that this is anything but a user configuration issue. If there does turn out to be some tangible bug, please chase it down with upstream systemd.
Friday, 04 July 2014, 13:43 GMT
Reason for closing: Not a bug
Additional comments about closing: No evidence that this is anything but a user configuration issue. If there does turn out to be some tangible bug, please chase it down with upstream systemd.
Ownership / permissions issue?
Who owns your /var/log/journal and its subfolders?
Does the systemd-journal group exist?
pwck and grpck don't report any issues.
Fresh install
" I also don't get any notice when running systemctl enable <someunit>."
This is entirely unrelated, and already "fixed" upstream.
If there is an error with 214, a journal by 214 would be more helpful ;)
edit:
Wait...
"Jun 25 11:45:10 archvm systemd-udevd[179]: starting version 214"
Why is udev a different version?
edit 2:
Oh wait, virtualization. I'm an idiot. I also don't know how that might affect things, so I'm out, I guess. Sorry.
Because you didn't rebuild your initramfs after upgrading systemd.
/etc/group: http://sprunge.us/KAZO
/etc/passwd: http://sprunge.us/GSeh
journalctl -b: http://sprunge.us/GYfc
Jun 26 17:35:37 lambda grpck[185]: add group 'systemd-journal-gateway' to '/etc/gshadow'
Jun 26 17:35:39 lambda grpck[185]: add group 'systemd-timesync' to '/etc/gshadow'
Jun 26 17:35:40 lambda grpck[185]: add group 'systemd-network' to '/etc/gshadow'
Jun 26 17:35:42 lambda grpck[185]: add group 'systemd-bus-proxy' to '/etc/gshadow'
Jun 26 17:35:43 lambda grpck[185]: add group 'systemd-resolve' to '/etc/gshadow'
I use systemd-networkd (no netctl whatsoever).
I don't get any feedback in 'journalctl -f' when # systemctl restart systemd-timesyncd.service
However, when # systemctl status systemd-timesyncd.service ; I do get the correct launch time (Active: active (running) since Wed 2014-07-02 14:01:25 CEST; 38s ago).
Arch x86_64
- reboot
- rebuild the initramdisk (mkinitcpio -p linux-lts, mkinitcpio -p linux)
- reboot
-> my problem was fixed
I always have rebuilt my initramdisk before rebooting; so my udev version was 213...
So when heftig suggested this 2 weeks ago...