# uname -r 2.6.41.10-3.fc15.x86_64 First there was an upgrade: Feb 12 05:09:27 s3 yum[14291]: Updated: systemd-units-26-16.fc15.x86_64 Feb 12 05:09:43 s3 systemd[1]: Reexecuting. Feb 12 05:09:44 s3 systemd[1]: systemd 26 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; fedora) Feb 12 05:09:44 s3 yum[14291]: Updated: systemd-26-16.fc15.x86_64 Feb 12 05:09:45 s3 yum[14291]: Updated: systemd-sysv-26-16.fc15.x86_64 Feb 12 05:09:50 s3 systemd[1]: Reloading. Feb 12 05:09:32 s3 yum[14291]: Updated: kernel-headers-2.6.42.3-2.fc15.x86_64 Feb 12 05:09:40 s3 yum[14291]: Installed: kernel-2.6.42.3-2.fc15.x86_64 Then, when a cron job noticed the new kernel and tried to do a shutdown timed reboot via /sbin/shutdown -r +5 in /var/log/messages I get: Feb 13 03:00:01 s3 systemd-shutdownd[2733]: Received message without credentials. Ignoring. and the system does not reboot. Since it talked about credentials, I double checked that selinux is not active on the machine: # /usr/sbin/sestatus SELinux status: disabled yum update is done every day, but the problem still persists. The cron job notices every day that the running kernel is not the new one and tries to schedule a reboot and the same error message gets into the logs. I have been reading about systemd. I've read everything on the wiki, the man pages, and on Lennart's blog. I've watched videos of his presentation about systemd and I STILL don't have a clue. My next choice is to use strace on the pid and see what happens when I try the shutdown so I can see what it's trying to do that makes is issue the log message, but I was hoping someone here would know;) Patrick -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
