Bug 698198
| Summary: | FIXED_IN_GIT: systemd reexec needs to be synchronous | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Richard W.M. Jones <rjones> | ||||||
| Component: | systemd | Assignee: | Lennart Poettering <lpoetter> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 15 | CC: | an0nym, andrei.ilie, carenas, clonnerz, eddie, fedoration, fred.new2911, gholms, hongjiu.lu, jakub, johannbg, jones.peter.busi, joshua, j, laurent.rineau__fedora, lemenkov, linux.n.pkd, lpoetter, mads, metherid, mschmidt, notting, philipp, plautrba, rambler8, ramez.hanna, rda, ricardo.arguello, robatino, rtguille, schwab, stijn, udovdh, xjtu_chdongsh | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | systemd-26-10.fc15 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-09-09 17:07:46 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Richard W.M. Jones
2011-04-20 12:31:45 UTC
Sorry, pressed the "enter" key at the wrong time. This is a non-fatal error, but you'll get it if you install F15 beta, then upgrade glibc in the ordinary way. It's probably not important, but I thought I would mention it anyway in case it is a symptom of something bad going on underneath. Non-fatal POSTIN scriptlet failure in rpm package glibc-2.13.90-9.x86_64 /usr/sbin/glibc_post_upgrade: While trying to execute /sbin/service child exited with exit code 1 warning: %post(glibc-2.13.90-9.x86_64) scriptlet failed, exit status 1 What's the /sbin/service line that is triggering this? Any more output on this? On my machine there is no /usr/sbin/glibc_post_upgrade? /usr/sbin/glibc_post_upgrade.{i686,x86_64} are static binaries.
I had a look at the code for this binary and the only reference
to /sbin/service is this:
/* Check if we can safely condrestart sshd. */
if (access ("/sbin/service", X_OK) == 0
&& access ("/usr/sbin/sshd", X_OK) == 0
&& access ("/etc/rc.d/init.d/sshd", X_OK) == 0
&& access ("/bin/bash", X_OK) == 0)
{
if (check_elf ("/usr/sbin/sshd"))
verbose_exec (-121, "/sbin/service", "/sbin/service", "sshd", "condrestart");
}
I think this is a dup of some other bug, don't remember the bug number though. The problem is that /sbin/service <servicename> condrestart must exit with zero exit status both when the service has been running and has been successfully restarted, or when it has not been running (that's why it is condrestart, conditional restart). But condrestart should work like that already since a while. The other bug was closed. And verifying this manually, this works completely fine here. # systemctl stop sshd.service # systemctl condrestart sshd.service ; echo $? 0 # service sshd condrestart ; echo $? Restarting sshd (via systemctl): [ OK ] 0 # systemctl start sshd.service # systemctl condrestart sshd.service ; echo $? 0 # service sshd condrestart ; echo $? Restarting sshd (via systemctl): [ OK ] 0 So condrestart returns 0 both when sshd is running and when it is not. As it should be. No idea what is going on here. Richard, is there any other output generated when this happens? Just the output shown, apart from the usual yum/rpm output obviously. Also on this machine 'service sshd condrestart' appears to work OK: $ sudo service sshd condrestart ; echo $? Restarting sshd (via systemctl): [ OK ] 0 $ sudo service sshd stop ; echo $? Stopping sshd (via systemctl): [ OK ] 0 $ sudo service sshd condrestart ; echo $? Restarting sshd (via systemctl): [ OK ] 0 Any output in syslog when this happens? These are messages from around the same time. /var/log/yum.log: Apr 20 13:29:47 Updated: glibc-2.13.90-9.x86_64 Apr 20 13:30:01 Updated: glibc-common-2.13.90-9.x86_64 /var/log/messages: [I will attach it as it's large] Nothing else in other logs that looks relevant, but here is the complete list of log files in case you want me to fish out one of them: drwxr-xr-x. 16 root root 4096 Apr 20 13:12 . drwxr-xr-x. 18 root root 4096 Apr 20 12:39 .. drwxr-xr-x. 2 root root 4096 Apr 20 13:10 ConsoleKit -rw-r--r--. 1 root root 28022 Apr 20 13:36 Xorg.0.log -rw-r--r--. 1 root root 28022 Apr 20 13:11 Xorg.9.log drwxr-xr-x. 2 root root 4096 Apr 20 12:58 anaconda drwxr-x---. 2 root root 4096 Apr 20 13:10 audit drwxr-xr-x. 2 494 491 4096 Feb 8 07:27 bittorrent -rw-r--r--. 1 root root 2150 Apr 20 13:10 boot.log -rw-------. 1 root 22 384 Apr 20 13:11 btmp -rw-r--r--. 1 root root 92 Apr 20 13:10 cron drwxr-xr-x. 2 lp sys 4096 Feb 25 13:38 cups -rw-r--r--. 1 root root 93818 Apr 20 12:58 dracut.log drwxrwx--T. 2 root 42 4096 Apr 20 13:11 gdm -rw-r--r--. 1 root root 146292 Apr 20 13:30 lastlog drwxr-xr-x. 2 root root 4096 Apr 20 12:34 mail -rw-------. 1 root root 540 Apr 20 13:10 maillog -rw-------. 1 root root 98739 Apr 20 13:36 messages drwxr-xr-x. 2 38 38 4096 Feb 9 01:56 ntpstats -rw-rw-r--. 1 root root 0 Apr 20 13:11 pm-powersave.log drwx------. 2 root root 4096 Feb 9 16:30 ppp drwxr-xr-x. 2 root root 4096 Nov 23 23:39 prelink drwx------. 3 root root 4096 Apr 20 11:06 samba -rw-------. 1 root root 3485 Apr 20 13:36 secure drwxr-xr-x. 2 root root 4096 Mar 1 16:06 setroubleshoot drwx------. 2 root root 4096 Mar 16 03:31 speech-dispatcher -rw-------. 1 root root 0 Apr 20 11:03 spooler drwxr-x---. 2 root root 4096 Mar 24 19:38 sssd -rw-------. 1 root root 0 Apr 20 10:15 tallylog -rw-rw-r--. 1 root 22 7680 Apr 20 13:36 wtmp -rw-------. 1 root root 1826 Apr 20 13:34 yum.log Created attachment 495430 [details]
/var/log/messages during update
Ah, here's my guess what is going on: glibc asks systemd to reexec and quickly after that asks it to restart sshd. The reexec is async, and the sshd restart might be issued at a time where systemd isn't responsive to requests yet. Jakub, am I assuming right that this upgrade tool sends SIGTERM to PID 1, and afterwards restarts sshd? To fix this we'd have to make the reexec synchronours. That's everything but trivial... Urks. Indeed it is the case that the call to telinit immediately
precedes the call to service condrestart. The exact code is:
if (check_elf ("/proc/1/exe"))
verbose_exec (116, "/sbin/telinit", "/sbin/telinit", "u");
/* Check if we can safely condrestart sshd. */
if (access ("/sbin/service", X_OK) == 0
&& access ("/usr/sbin/sshd", X_OK) == 0
&& access ("/etc/rc.d/init.d/sshd", X_OK) == 0
&& access ("/bin/bash", X_OK) == 0)
{
if (check_elf ("/usr/sbin/sshd"))
verbose_exec (-121, "/sbin/service", "/sbin/service", "sshd", "condrestart");
}
Yeah, glibc_post_upgrade spawns /sbin/telinit u too (the reason for that is to avoid unclean shut downs and make sure init uses the newly installed libc). OK, found a nice way to make reeexecutions synchronous. "telinit u" will know wait until the new systemd is fully up before returning. This should fix the bug. systemd-26-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/systemd-26-1.fc15 systemd-26-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. I had update systemd-26-1, but problem isn't solved , and update to glibc-2.13.90-10, the same error exist : Updating : glibc-2.13.90-10.x86_64 2/12 Non-fatal POSTIN scriptlet failure in rpm package glibc-2.13.90-10.x86_64 /usr/sbin/glibc_post_upgrade: While trying to execute /sbin/service child exited with exit code 1 warning: %post(glibc-2.13.90-10.x86_64) scriptlet failed, exit status 1 *** Bug 702357 has been marked as a duplicate of this bug. *** Interesting that bugzilla did not find this bug while searching for the exact error. Oh well. In my case I got systemd-26-1 in the same upgrade as glibc-2.13.90-10 so I can only confirm the fix after yet another glibc upgrade. Or is it safe to downgrade only glibc? (seems like asking for trouble). *** Bug 702377 has been marked as a duplicate of this bug. *** Reopening. The bug is still present in systemd-26-1.fc15.
# telinit u; service sshd condrestart; echo $?
Restarting sshd (via systemctl): Failed to get D-Bus connection: Connection terminated during authentication.
[SELHALO]
1
But this works:
# systemctl daemon-reexec; service sshd condrestart; echo $?
Restarting sshd (via systemctl): [ OK ]
0
This contradicts what "man telinit" says:
u, U
Serialize state, reexecute daemon and deserialize state again.
This is equivalent to systemctl daemon-reexec.
Oh, dang. I far "telinit u" is probaly not fixable, since the old SysV telinit fifo is used in a fire-and-forget way. i.e. the command just writes a blob to the fifo and quits. There is not back channel that could be used to return the information about completion back. What we can do probably is ensure that telinit u always uses dbus to communicate instead of /dev/initctl Isn't a bigger problem that during restarting of systemd service fails? I mean, even if you make telinit u synchronous instead of asynchronous, if somebody simultaneously with telinit u calls service <someservice> condrestart, it will fail, instead of waiting till systemd is back up and handles that request. Sure, there should be some timeout to avoid waiting forever... *** Bug 708683 has been marked as a duplicate of this bug. *** *** Bug 711399 has been marked as a duplicate of this bug. *** # yum history info 511
Loaded plugins: auto-update-debuginfo, presto, refresh-packagekit
Transaction ID : 511
Begin time : Sat Jun 25 07:21:28 2011
Begin rpmdb : 2160:036f87d0abf0cb0bb989d2530af7aa979bd24d0e
End time : 07:24:27 2011 (179 seconds)
End rpmdb : 2160:083f4c75662a0ad91ba64e77139bb8f3ef34a968
User : Udo <udo>
Return-Code : Success
Command Line : update
Transaction performed with:
Installed rpm-4.9.0-9.fc15.x86_64
Installed yum-3.2.29-6.fc15.noarch
Installed yum-presto-0.6.2-3.fc15.noarch
Packages Altered:
Updated autofs-1:5.0.5-35.fc15.x86_64
Update 1:5.0.5-38.fc15.x86_64
Updated device-mapper-1.02.63-2.fc14.x86_64
Update 1.02.63-3.fc15.x86_64
Updated device-mapper-devel-1.02.63-2.fc14.x86_64
Update 1.02.63-3.fc15.x86_64
Updated device-mapper-event-1.02.63-2.fc14.x86_64
Update 1.02.63-3.fc15.x86_64
Updated device-mapper-event-libs-1.02.63-2.fc14.x86_64
Update 1.02.63-3.fc15.x86_64
Updated device-mapper-libs-1.02.63-2.fc14.x86_64
Update 1.02.63-3.fc15.x86_64
Updated firefox-4.0.1-2.fc15.x86_64
Update 5.0-1.fc15.x86_64
Updated gimp-2:2.6.11-15.fc15.x86_64
Update 2:2.6.11-16.fc15.x86_64
Updated gimp-devel-2:2.6.11-15.fc15.x86_64
Update 2:2.6.11-16.fc15.x86_64
Updated gimp-devel-tools-2:2.6.11-15.fc15.x86_64
Update 2:2.6.11-16.fc15.x86_64
Updated gimp-help-browser-2:2.6.11-15.fc15.x86_64
Update 2:2.6.11-16.fc15.x86_64
Updated gimp-libs-2:2.6.11-15.fc15.x86_64
Update 2:2.6.11-16.fc15.x86_64
Updated gjs-0.7.14-3.fc15.x86_64
Update 0.7.14-6.fc15.x86_64
Updated glibc-2.14-2.i686
Updated glibc-2.14-2.x86_64
Update 2.14-3.i686
Update 2.14-3.x86_64
Updated glibc-common-2.14-2.x86_64
Update 2.14-3.x86_64
Updated glibc-devel-2.14-2.x86_64
Update 2.14-3.x86_64
Updated glibc-headers-2.14-2.x86_64
Update 2.14-3.x86_64
Updated gnome-python2-extras-2.25.3-31.fc15.x86_64
Update 2.25.3-32.fc15.x86_64
Updated gnome-python2-gtkhtml2-2.25.3-31.fc15.x86_64
Update 2.25.3-32.fc15.x86_64
Updated gnome-python2-gtkspell-2.25.3-31.fc15.x86_64
Update 2.25.3-32.fc15.x86_64
Updated gnome-python2-libegg-2.25.3-31.fc15.x86_64
Update 2.25.3-32.fc15.x86_64
Updated gnome-shell-3.0.2-1.fc15.x86_64
Update 3.0.2-3.fc15.x86_64
Updated js-1:1.8.5-4.fc15.x86_64
Update 1:1.8.5-6.fc15.x86_64
Updated libreport-2.0.3-1.fc15.x86_64
Update 2.0.4-1.fc15.x86_64
Updated libreport-gtk-2.0.3-1.fc15.x86_64
Update 2.0.4-1.fc15.x86_64
Updated libva-1.0.12-1.fc15.x86_64
Update 1.0.13-2.fc15.x86_64
Updated lvm2-2.02.84-2.fc14.x86_64
Update 2.02.84-3.fc15.x86_64
Updated lvm2-libs-2.02.84-2.fc14.x86_64
Update 2.02.84-3.fc15.x86_64
Updated motion-3.2.12-1.fc14.x86_64
Update 3.3.0-trunkREV528.fc15.x86_64
Updated nscd-2.14-2.x86_64
Update 2.14-3.x86_64
Updated python-xlib-0.15-0.4.rc1.fc15.noarch
Update 0.15-0.5.rc1.fc15.noarch
Updated vcdimager-0.7.23-13.fc13.1.x86_64
Update 0.7.24-1.fc15.x86_64
Updated vcdimager-libs-0.7.23-13.fc13.1.x86_64
Update 0.7.24-1.fc15.x86_64
Updated xulrunner-2.0.1-1.fc15.x86_64
Update 5.0-2.fc15.x86_64
Scriptlet output:
1 /usr/sbin/glibc_post_upgrade: While trying to execute /sbin/service child exited with exit code 1
2 warning: %post(glibc-2.14-3.x86_64) scriptlet failed, exit status 1
3 warning: /etc/motion/motion.conf created as /etc/motion/motion.conf.rpmnew
history info
# rpm -q systemd
systemd-26-4.fc15.x86_64
Created attachment 509892 [details]
/var/log/messages during glibc update
Hello. After today update of glibc I got same warning:
Non-fatal POSTIN scriptlet failure in rpm package glibc-2.14-3.x86_64
/usr/sbin/glibc_post_upgrade: While trying to execute /sbin/service child exited with exit code 1
warning: %post(glibc-2.14-3.x86_64) scriptlet failed, exit status 1
I hope you find my /var/log/mesasges snippet useful.
*** Bug 716597 has been marked as a duplicate of this bug. *** *** Bug 716736 has been marked as a duplicate of this bug. *** Got the same problem as in comment 27 recently. While the bug is being fixed, can anyone explain what the error during update meant (what was done and what wasn't?) and how can we (should we?) fix it by hand instead of waiting for an update? *** Bug 716944 has been marked as a duplicate of this bug. *** an0nym: The post-installation scriptlet just tries to restart sshd. You can restart it manually with
service sshd restart
(I haven't taught myself the systemctl syntax, yet.)
i am seeing an issue that i think is same i use yum to create a chrot of fedora so basically it runs yum --installroot $INSTALL_ROOT -y --nogpgcheck yum initscripts passwd rsyslog vim-minimal dhclient chkconfig rootfiles policycoreutils then it stops with this log Installing : glibc-common-2.14-4.x86_64 12/156 Non-fatal POSTIN scriptlet failure in rpm package glibc-common-2.14-4.x86_64 Non-fatal <unknown> scriptlet failure in rpm package glibc-common-2.14-4.x86_64 lxc-fedora.in: line 100: 1278 Segmentation fault $YUM install $PKG_LIST [root@xanax var]# rpm -qa systemd
systemd-26-8.fc15.x86_64
[root@xanax var]# uname -a
Linux xanax 2.6.38.8-35.fc15.x86_64 #1 SMP Wed Jul 6 13:58:54 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
[root@xanax var]#
Date: Wed, 20 Jul 2011 15:45:01 -0400
From: Cron Daemon <root@xanax>
To: root@xanax
Subject: Cron <root@xanax> /bin/systemctl restart dhcpd.service ; /bin/systemctl reload-or-try-restart shorewall.service 2>&1 >
/dev/null
Failed to get D-Bus connection: Connection terminated during authentication.
Failed to get D-Bus connection: Connection terminated during authentication.
Date: Wed, 20 Jul 2011 15:00:01 -0400
From: Cron Daemon <root@xanax>
To: root@xanax
Subject: Cron <root@xanax> /sbin/service snortd restart 2>&1 > /dev/null
Failed to get D-Bus connection: Connection terminated during authentication.
root@xanax var]# date
Wed Jul 20 16:05:10 EDT 2011
[root@xanax var]# grep -i d-bus /var/log/messages
Jul 18 23:21:33 xanax systemd-initctl[9126]: Failed to get D-Bus connection: Connection terminated during authentication.
Jul 18 23:21:33 xanax systemd-initctl[9128]: Failed to get D-Bus connection: Connection terminated during authentication.
Jul 18 23:21:33 xanax systemd-initctl[9130]: Failed to get D-Bus connection: Connection terminated during authentication.
Jul 18 23:21:33 xanax systemd-initctl[9132]: Failed to get D-Bus connection: Connection terminated during authentication.
Jul 18 23:21:33 xanax systemd-initctl[9134]: Failed to get D-Bus connection: Connection terminated during authentication.
Jul 18 23:21:33 xanax systemd-initctl[9136]: Failed to get D-Bus connection: Connection terminated during authentication.
[root@xanax var]#
[root@xanax var]# file /var/run/dbus/system_bus_socket
/var/run/dbus/system_bus_socket: socket
[root@xanax var]# ls -las /var/run/dbus/system_bus_socket
0 srwxrwxrwx 1 root root 0 Jul 18 23:32 /var/run/dbus/system_bus_socket
[root@xanax var]# kill -1 1213
[root@xanax var]# lsof | grep /var/run/dbus/system_bus_socket
systemd 1 root 17u unix 0xffff880037ab8d00 0t0 14784 /var/run/dbus/system_bus_socket
dbus-daem 1213 dbus 3u unix 0xffff880037ab8d00 0t0 14784 /var/run/dbus/system_bus_socket
dbus-daem 1213 dbus 8u unix 0xffff8800b73163c0 0t0 17997 /var/run/dbus/system_bus_socket
dbus-daem 1213 dbus 9u unix 0xffff880037abb740 0t0 17998 /var/run/dbus/system_bus_socket
dbus-daem 1213 dbus 10u unix 0xffff8800b7316080 0t0 17999 /var/run/dbus/system_bus_socket
dbus-daem 1213 dbus 11u unix 0xffff8800b5d67a80 0t0 22032 /var/run/dbus/system_bus_socket
dbus-daem 1213 dbus 12u unix 0xffff880037202d80 0t0 21141 /var/run/dbus/system_bus_socket
dbus-daem 1213 dbus 14u unix 0xffff88000e412a40 0t0 1031652 /var/run/dbus/system_bus_socket
[root@xanax var]# tail -f /var/log/messages &
[1] 19012
[root@xanax var]# Jul 20 16:00:07 xanax xenconsoled: Failed to contact xenstore (No such file or directory). Is it running?
Jul 20 16:00:12 xanax systemd[1]: Too many concurrent connections.
Jul 20 16:00:12 xanax systemd[1]: Too many concurrent connections.
Jul 20 16:03:19 xanax rsyslogd-2177: imuxsock lost 112 messages from pid 18826 due to rate-limiting
Jul 20 16:05:01 xanax systemd[1]: Too many concurrent connections.
Jul 20 16:05:01 xanax systemd[1]: Too many concurrent connections.
Jul 20 16:05:07 xanax xenconsoled: Failed to contact xenstore (No such file or directory). Is it running?
Jul 20 16:05:12 xanax systemd[1]: Too many concurrent connections.
Jul 20 16:05:12 xanax systemd[1]: Too many concurrent connections.
Jul 20 16:08:58 xanax dbus-daemon: [system] Reloaded configuration
[root@xanax var]# ps auwwJul 20 16:10:01 xanax systemd[1]: Too many concurrent connections.
Jul 20 16:10:01 xanax systemd[1]: Too many concurrent connections.
wx | grep Jul 20 16:10:06 xanax xenconsoled: Failed to contact xenstore (No such file or directory). Is it running?
18826
root 19076 0.0 0.0 109100 832 pts/0 S+ 16:10 0:00 grep --color=auto 18826
You have new mail in /var/spool/mail/root
[root@xanax var]# Jul 20 16:10:12 xanax systemd[1]: Too many concurrent connections.
[root@xanax var]# chkconfig xenconsoled off
Jul 20 16:10:58 xanax systemd[1]: Too many concurrent connections.
[root@xanax var]# systemctl stop xenconsoled.service
Failed to get D-Bus connection: Connection terminated during authentication.
Jul 20 16:11:11 xanax systemd[1]: Too many concurrent connections.
You have new mail in /var/spool/mail/root
[root@xanax var]# service gpm restart
Restarting gpm (via systemctl): Failed to get D-Bus connection: Connection terminated during authentication.
Jul 20 16:11:57 xanax systemd[1]: Too many concurrent connections.
[FAILED]
[root@xanax var]# service samba restart
samba: unrecognized service
[root@xanax var]# service smb restart
Restarting smb (via systemctl): Jul 20 16:12:15 xanax systemd[1]: Too many concurrent connections.
Failed to get D-Bus connection: Connection terminated during authentication.
[FAILED]
You have mail in /var/spool/mail/root
[root@xanax var]#
Hello there,
I subscribe to this bug: just installed stable F15 and performed a yum update and this is what I got:
Non-fatal POSTIN scriptlet failure in rpm package glibc-2.14-4.x86_64
/usr/sbin/glibc_post_upgrade: While trying to execute /sbin/service child exited with exit code 1
warning: %post(glibc-2.14-4.x86_64) scriptlet failed, exit status 1
----------------------------------------------------
andrei@cofee:~$ yum -C list systemd
Installed Packages
systemd.x86_64 version = 26-8.fc15
----------------------------------------------------
PS: Pretty hard to find your installed systemd version :)
andrei@cofee:~$ systemd -v
systemd: invalid option -- 'v'
Unknown option code ?
andrei@cofee:~$ systemd --version
systemd: unrecognized option '--version'
Unknown option code ?
*** Bug 730578 has been marked as a duplicate of this bug. *** *** Bug 731953 has been marked as a duplicate of this bug. *** Urks, this was actually a trivial mistake: "telinit u" first did the fully synchronous reexecution of PID 1, but then repeated this asynchronously via sending SIGTERM to PID1 which was intended as fallback only but got executed unconditionally. Fixed now in git. systemd-35-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/systemd-35-1.fc16 Package systemd-35-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-35-1.fc16' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/systemd-35-1.fc16 then log in and leave karma (feedback). Will there be following an update for F15 as well shortly? systemd-35-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. systemd-26-10.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/systemd-26-10.fc15 systemd-26-10.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 786934 has been marked as a duplicate of this bug. *** It looks like this is still a problem on Fedora 15 #rpm -q systemd systemd-26-16.fc15.i686 Updating : glibc-2.14.1-6.i686 Non-fatal POSTIN scriptlet failure in rpm package glibc-2.14.1-6.i686 /usr/sbin/glibc_post_upgrade: While trying to execute /sbin/service child exited with exit code 1 warning: %post(glibc-2.14.1-6.i686) scriptlet failed, exit status 1 |