Red Hat Bugzilla – Bug 52615
sshd server won't start
Last modified: 2008-05-01 11:38:00 EDT
Description of Problem:
sshd server would not run due to wrong glibc version.
rebuild from source RPM solved problem.
Version-Release number of selected component (if applicable):
every time /etc/init.d/sshd was started
Steps to Reproduce:
1. /etc/init.d/sshd start
system was upgraded from RedHat 7.1 to Roswell beta 1 then
Roswell beta 2. sshd would no longer start.
Which version of sshd was installed when it would not restart? Equivalently,
what is the output of "rpm -q openssh-server"?
Binary openssh-server-2.9p2-5.i386.rpm from Roswell 7.1.94 ISO image
output from 'ldd usr/sbin/sshd':
usr/sbin/sshd: /lib/libc.so.6: version `GLIBC_2.2.4' not found (required by
libpam.so.0 => /lib/libpam.so.0 (0x40029000)
libdl.so.2 => /lib/libdl.so.2 (0x40032000)
libz.so.1 => /usr/lib/libz.so.1 (0x40036000)
libnsl.so.1 => /lib/libnsl.so.1 (0x40044000)
libutil.so.1 => /lib/libutil.so.1 (0x4005b000)
libcrypto.so.2 => /lib/libcrypto.so.2 (0x4005e000)
libc.so.6 => /lib/libc.so.6 (0x40121000)
'rpm --rebuild openssh-2.9p2-5.src.rpm' created a working
This looks like an RPM dependency error, probably due to the anonftp trigger
breaking the glibc upgrade. If you run "rpm -q glibc", do you get a version
other than "2.2.4-something"? If so, then this is actually a duplicate of bug
Doh. More accurately, a failed trigger causing an RPM upgrade of glibc to fail.
(44)% rpm -q glibc
This matches the version number on the Roswell ISO image.
Can I get you to also verify the contents of the package with:
rpm -y glibc glibc-common
You shouldn't get any output if you're running as root, and a few unverifiable
files as non-root due to file permissions.
That doesn't look good:
I did do the upgrade to the latest beta using 'rpm -F'
in single user mode. Maybe that's the cause?
This sounds more and more like a partially-successful glibc upgrade. Try
re-upgrading the glibc and glibc-devel packages, using "--force" if need be, and
see if you can get the same error starting sshd once the glibc upgrade is
finished and verifies cleanly.
Note: --force is equivalent to "--replacepkgs --replacefiles", and does not
include the "--nodeps" flag, which should not be needed to fix the glibc upgrade
That fixes sshd.
Excellent. Marking as fixed in Raw Hide, because the offending trigger has been