FC3, portmap, syslogd, libc and libnst....hmmm

[nomo_green]

hello everybody, here's the story ( RH FC3 kernel: 2.6.9-1.681_FC3 ):

2 days ago everything was dandy. i ran apt-get update and then apt-get dist-upgrade to get up to date. the computer ran fine, no errors, no nothing. i use apt and freshrpms.net for updates (used them for a long time with no problems). i'm very certain i installed nothing else and wasn't even online that long. after i rebooted, i got portmap errors, syslogd errors, and complaints about libc and libnst. below are some of the messages:

Starting system logger: syslogd: error while loading shared libraries: libc.so.6: failed to map segment from shared object: Permission denied
[FAILED]
----------------------------------------------------------------------------------------------------------------------------------
tarting portmap: portmap: error while loading shared libraries: libnsl.so.1: failed to map segment from shared object: Permission denied
[FAILED]
----------------------------------------------------------------------------------------------------------------------------------


i see nothing relevant in the logs, no errant processes and no open ports. the system runs fine, but i'm worried something bad has happened. i even tried booting into an older kernel and still get the same failures.

can anyone shed some light as to what is going on? did they stop using syslogd and mess with portmap since the last update or did something bad happen?

thanks in advance,

nomo :eek:

[owakroeger]

You might try installing/running chkrootkit to see what it finds. Also, are you behind any sort of firewall? I'd get and configure firestarter, if you're not. I'd also get and configure clamscan, if you haven't already.
Except for seeing what chdrootkit finds, I don't have an answer.
owa

[tchung]

Hope this helps:

http://fcp.homelinux.org/modules/wffaq/article.php?t=23

Thomas

[nomo_green]

Thank you guys soooo much!!!! You saved me!!

You guys rock. The replies were timely and correct. Gotta love it. Anyways, Tchung thanks for the link. I searched earlier for it and it turned up squat. I did touch that file and rebooted and it works perfectly and it's even logging again. Whew, I was just about to say F'it and start over, but if I did that I would have had the same problem as I previously had.


Anyways thanks you guys for the timely comments, both of ya'll! I'll always come here first now.

nomo :)

[owakroeger]

Your thanks should really go to Tchung. Mine, too, 'cuz I had completely forgotten about that faq about selinux. My suggestions ref chkrootkit, firestarter, and clamscan still apply, though. They're all readily available via apt-get/synaptic or yum, and they work.
Thanks, Tchung.

owa