[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Libc.so.6 Problems
- Subject: Re: [cobalt-users] Libc.so.6 Problems
- From: "E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>
- Date: Thu Apr 24 10:01:01 2003
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
SY> Date: Fri, 25 Apr 2003 02:07:44 +1000
SY> From: Samuel Yeats
SY> Out of the blue one of our virtual hosting servers (raq 4)
SY> started spitting out these errors complaining about the
SY> libc.so.6 application
Uhoh. (It's a library, not an app, BTW.)
SY> HTTP still works. But I assume if we reboot the server will
SY> not come back.
There is a reasonable chance of that. Silly GNU/Linux has /bin
and /sbin binaries dynamically linked... yuck.
SY> Does anyone have any ideas?
Looks like libc is screwed up. This is a very bad thing. Can
you:
ls /usr/lib/libc*
ls /lib/libc*
and tell us what you get?
SY> I do remember a few months back a similar problem occurred,
SY> could it be possible that installing the offending drive into
SY> another server and copying the /lib/ directory back onto this
SY> server could fix it?
If you copy /lib and /usr/lib from another machine, remember to
update ld.so.cache, too. See the manpage for ldconfig(8).
You might be able to run 'ldconfig' as root and knock some sense
into the box. Then again, it SHOULDN'T help... unless you've
been upgrading libraries, particularly glibc, you shouldn't need
to do this.
Eddy
--
Brotsman & Dreger, Inc. - EverQuick Internet Division
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 (785) 865-5885 Lawrence and [inter]national
Phone: +1 (316) 794-8922 Wichita
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@xxxxxxxxx>, or you are likely to
be blocked.