This is strange. About mid-afternoon today while I was at work, my system at home did the same thing. I haven't noticed anything odd in the logs, but I think I'll investigate a little more.
Does anyone have the actual filename for the RPM or should I go off searching?
Bryanarkman wrote:
>
> Mark,
> Kind of strange, but I had the exact same thing happen to me
> on either sunday night or monday morning. This is a pretty
> important module so you won't be able to do much. This is how
> I fixed mine (sorry I don't have all the details at work
> right now):
> 1. Used Google to search for the libc.so.5 module. You will
> get a match with rpmfind.net (you could just go straight
> there if you like).
> 2. Find the rpm that contains the libc.so.5 module it is one
> of the ones for glibc. Get the correct version for the system
> you are running. It will be a redhat rpm and is probably for
> redhat 6.x for a 4.0/4.01 e-smith system. (Like I said above
> the exact file name is at home, but you should be able to
> find it.)
> 3. Get it onto your e-smith machine (difficult if your
> network is down) and use rpm to do an upgrade.
>
> This worked for me, but I don't gurantee it. I have no idea
> if this is the best course of action or not, but I was
> desperate and took a chance that appears to have worked.
>
> Did anything strange happen on your server to cause the
> libc.so.5 problem? Was it working before or was this a clean
> install?
>
> Noah