<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 02/17/2012 09:08 AM, Patrick Horgan wrote:
<blockquote cite="mid:4F3E898A.5010005@dbp-consulting.com"
type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
On 02/17/2012 08:43 AM, Boris Epstein wrote:
<blockquote
cite="mid:CADeF1XFh85_-C2Oq1-LopkycVybYqY08e=i8xmPT5PbeKuxOzQ@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">On Fri, Feb 17, 2012 at 11:41 AM,
Patrick Horgan <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:phorgan1@gmail.com">phorgan1@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"> # uname
-r<br>
2.6.41.10-3.fc15.x86_64<br>
<br>
<br>
First there was an upgrade:<br>
<br>
Feb 12 05:09:27 s3 yum[14291]: Updated:
systemd-units-26-16.fc15.x86_64<br>
Feb 12 05:09:43 s3 systemd[1]: Reexecuting.<br>
Feb 12 05:09:44 s3 systemd[1]: systemd 26 running in system
mode. (+PAM<br>
+LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; fedora)<br>
Feb 12 05:09:44 s3 yum[14291]: Updated:
systemd-26-16.fc15.x86_64<br>
Feb 12 05:09:45 s3 yum[14291]: Updated:
systemd-sysv-26-16.fc15.x86_64<br>
Feb 12 05:09:50 s3 systemd[1]: Reloading.<br>
Feb 12 05:09:32 s3 yum[14291]: Updated:
kernel-headers-2.6.42.3-2.fc15.x86_64<br>
Feb 12 05:09:40 s3 yum[14291]: Installed:
kernel-2.6.42.3-2.fc15.x86_64<br>
<br>
<br>
Then, when a cron job noticed the new kernel and tried to do
a shutdown<br>
timed reboot via<br>
<br>
/sbin/shutdown -r +5<br>
<br>
in /var/log/messages I get:<br>
<br>
Feb 13 03:00:01 s3 systemd-shutdownd[2733]: Received message
without<br>
credentials. Ignoring.<br>
<br>
<br>
and the system does not reboot. Since it talked about
credentials, I<br>
double checked that selinux is not active on the machine:<br>
<br>
# /usr/sbin/sestatus<br>
SELinux status: disabled<br>
<br>
yum update is done every day, but the problem still
persists. The cron<br>
job notices every day that the running kernel is not the new
one and<br>
tries to schedule a reboot and the same error message gets
into the logs.<br>
<br>
I have been reading about systemd. I've read everything on
the wiki, the<br>
man pages, and on Lennart's blog. I've watched videos of
his<br>
presentation about systemd and I STILL don't have a clue.
My next<br>
choice is to use strace on the pid and see what happens when
I try the<br>
shutdown so I can see what it's trying to do that makes is
issue the log<br>
message, but I was hoping someone here would know;)<br>
<span class="HOEnZb"><font color="#888888"><br>
Patrick<br>
... elision of list sig by patrick ...</font></span></blockquote>
<div>Interesting. Does </div>
<div><br>
</div>
<div># init 5</div>
<div> <br>
</div>
<div>or </div>
<div><br>
</div>
<div># reboot</div>
<div><br>
</div>
<div>work?</div>
<div><br>
</div>
<div>Boris. <br>
</div>
</div>
</blockquote>
</blockquote>
reboot works, and I'm assuming it's because it doesn't have to use
the delayed shutdown service.<br>
<br>
<blockquote cite="mid:4F3E898A.5010005@dbp-consulting.com"
type="cite">... elision of message about not being able to try
reboot by patrick...</blockquote>
<br>
<blockquote cite="mid:4F3E898A.5010005@dbp-consulting.com"
type="cite"><br>
I was just reading the source for systemd, and the message is
issued here:<br>
<br>
if (msghdr.msg_controllen < CMSG_LEN(sizeof(struct
ucred)) ||<br>
control.cmsghdr.cmsg_level != SOL_SOCKET ||<br>
control.cmsghdr.cmsg_type != SCM_CREDENTIALS ||<br>
control.cmsghdr.cmsg_len != CMSG_LEN(sizeof(struct
ucred))) {<br>
log_warning("Received message without credentials.
Ignoring.");<br>
return 0;<br>
}<br>
<br>
They're getting credentials so that they can check to see if it's
uid 0 and if not fail. For some reason though, one of the things
that they're checking is not true. There's no way to tell which
from the message.<br>
</blockquote>
Still stuck. Another data point. Attaching to process 1 with
strace yields this:<br>
<br>
open("/sys/fs/cgroup/systemd/system/systemd-shutdownd.service/tasks",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)<br>
open("/sys/fs/cgroup/systemd/system/systemd-shutdownd.service",
O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file
or directory)<br>
sendmsg(14, {msg_name(0)=NULL,
msg_iov(2)=[{"l\4\1\1&\0\0\0\1\0\0\0o\0\0\0\1\1o\0\37\0\0\0/org/fre"...,
128}, {"!\0\0\0/system/systemd-shutdownd.se"..., 38}],
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 166<br>
<br>
We have another machine with the same hardware and software and it
weathered the same update fine and continues to automagically reboot
in the wee hours of the morning if it gets a new kernel.<br>
<br>
Sigh.<br>
<br>
Patrick<br>
</body>
</html>