Bug 851741

It's certainly not "calling home"; the last thing a glibc update does is restart sshd via systemd.  The message you're receiving is from systemd.

What is the output of the following command:

/usr/sbin/sshd -f /etc/ssh/sshd_config 

And what are the contents of /lib/systemd/system/*ssh*?

No output from that command when run as root:

[root@rawhide ~]#  /usr/sbin/sshd -f /etc/ssh/sshd_config
[root@rawhide ~]# 

The sshd daemon is running because thats how I'm accessing this virtual host.


[root@rawhide ~]# ls /lib/systemd/system/*ssh*
/lib/systemd/system/anaconda-sshd.service  /lib/systemd/system/sshd.service
[root@rawhide ~]# cat /lib/systemd/system/*ssh*
[Unit]
Description=OpenSSH server daemon
Before=anaconda.target
After=syslog.target network.target

[Service]
EnvironmentFile=/etc/sysconfig/sshd
ExecStartPre=/usr/sbin/sshd-keygen
ExecStartPre=/usr/sbin/handle-sshpw
ExecStart=/usr/sbin/sshd -D $OPTIONS -f /etc/ssh/sshd_config.anaconda
ExecReload=/bin/kill -HUP $MAINPID
[Unit]
Description=OpenSSH server daemon
After=syslog.target network.target auditd.service

[Service]
EnvironmentFile=/etc/sysconfig/sshd
ExecStartPre=/usr/sbin/sshd-keygen
ExecStart=/usr/sbin/sshd -D $OPTIONS
ExecReload=/bin/kill -HUP $MAINPID

[Install]
WantedBy=multi-user.target
[root@rawhide ~]# 



BTW.  Selinux is in permissive mode.

BTW I was teasing, just a little about calling home.  But you have to admit that the error message could leave that impression.   

As a general issue,  I would really like to see better error messages in our modern Linux systems.

And as for Gnome's "Oh, no! Something has gone wrong."  - well that just makes me mad!

Does /etc/ssh/sshd_config.anaconda exist?

No.

This system was yum updated from an fc17 base originally.

That's probably related to the problem.  This almost certainly isn't a glibc issue, but I'm not sure who to assign it to yet :-)


What does the following report
rpm -q --whatprovides /lib/systemd/system/anaconda-sshd.service

Also is there a file /etc/rc.d/init.d/sshd and if so, what are its contents?

[root@rawhide ~]# rpm -q --whatprovides /lib/systemd/system/anaconda-sshd.service
anaconda-18.6-1.fc19.i686



[root@rawhide ~]# cat /etc/rc.d/init.d/sshd
cat: /etc/rc.d/init.d/sshd: No such file or directory

Thanks.  Looking at this a bit more, it can't be the restarting of sshd as that's guarded on the existence of /etc/rc.d/init.d/sshd (arguably that's a bug and the code needs to be updated to handle systemd).

This might be the %post script which mucks around with the nscd service.  Does
"/sbin/systemctl daemon-reload" report any errors?

Yes.   The PATH is wrong.

[root@rawhide ~]# /sbin/systemctl daemon-reload
-bash: /sbin/systemctl: No such file or directory

This PATH is quieter.

[root@rawhide ~]# /usr/bin/systemctl daemon-reload
[root@rawhide ~]#

OK.  I finally managed to reproduce this.  Can you confirm that:

/sbin/telinit u

Will trigger the same error message you saw when upgrading glibc?

Assuming yes, can you also confirm by running:

/usr/sbin/glibc_post_upgrade.i686

Both confirmed.

This seems to be related with 841451. Please try to reinstall polkit with 'yum reinstall polkit'

Re Comment #12.   I don't think so, or at least, not confirmed.

I did a 'yum reinstall polkit'

then,  '/sbin/telinit u' and '/usr/sbin/glibc_post_upgrade.i686'   still return the same error message.  Downgrading and re-upgrading glibc also still returns the same error message.

which version of systemd is this? Can you reproduce this on the newest version from F18?

systemd-188-3.fc18  (and systemd-188-3.fc19)

I still get the error message from the two test commands:
    /sbin/telinit u
    /usr/sbin/glibc_post_upgrade.i686
on both fc18 and fc19.

Both systems fully updated in the last 15min.

Hmm, this shoudl really work correctly now on more recent F18. Please reopen if problem continues to exist!