I have a slack server that was running slack 8.1 with 2.4.18 until a couple of days ago, when i finally decided to go ahead with an upgrade that was way overdue. using swaret i installed slack current and i switched to 2.4.25.
apart from some minor problems everything went fine and i got the system up and running 2 days ago. but today when i came home the server was all messed up. when i try to run _any_ program i only get this error msg:
/lib/ld-linux.so.2: version `GLIBC_PRIVATE' not found (required by /lib/libc.so.6)
i have no automated swaret updates or such and have not done any manual upgrades since it last worked. and all the servers apart from ssh are up and running as normal (apache, mysql, postfix, pure-ftpd, vm-pop3d).
ssh gives this msg:
key_read: uudecode ***long hexstring, possibly the pub or priv key?*** failed
then crashes with the same GLIBC_PRIVATE msg as above when i try to login.
i havent restarted the server yet since i'm pretty sure it wont come back up in its current state and i dont want to do anything hasty before i have investigated further.
So, does anyone know if there is a way to solve this without a installing everything from scratch?
any ideas on what might have caused this?
after rebooting from a slack cd, I could make out that ld-linux.so.2 was pointing to libfoo.so. i tried changing it to ld-2.3.2.so but after running ldconfig it went back to libfoo. some closer examination of ld.so.conf showed that it contained /usr/i386-slackware-linux/lib instead of /usr/i486-slackware-linux/lib. after changing this I was able to boot the system as ususal.
i'm still not sure why i was able to boot the system in the first place though. and i'm still puzzled about what could have triggered the change, since no installations or such was done. had this occured right after the upgrade then it would have been easier to locate the source of the problem.