weird errors

[Ranjan_2]

While booting up my Linux box today I got the following error





messages; Enabling swap space:





sh:/bin/grep:too many open files in system





sh:/bin/grep:too many open files in system





sh:/bin/grep:too many open files in system grep:error while loading shared libraries:libc.so.6:cannot open





shared object file:Error 23 After I logged on, nothing seemed to be out of place until I tried





the





top command which gave the following error top: error while loading shared libraries libncurses.so.4:cannot open





shared object file :no such file or directory Also if I try using the locate command i get this error message:





locate :usr/var/locatedb :no such file or directory When i tried dmesg the only messages i got were the following:





sh:/bin/grep:too many open files in system





sh:/bin/grep:too many open files in system





sh:pipe error:too many open files in system Is there anyway I can repair my system? I suspect my system could have been attacked yesterday night.I got





several beeps each showing a message message from localhost.localdomain..........





localhost I checked my /var/spool/mail and it showed this among other messages Content-Type: message/rfc822 Return-Path:





Received: (from root@localhost)





by localhost.localdomain (8.11.6/8.11.6) id g4IAK5A03878





for bare@ubersource.net; Sat, 18 May 2002 04:20:05 -0600





Date: Sat, 18 May 2002 04:20:05 -0600





From: root





Message-Id: <200205181020.g4IAK5A03878@localhost.localdomain>





To: bare@ubersource.net





Subject: Tuxkit1.0 export DISPLAY=Skul1101; telnet # localhost.localdomain SSH: 5681





psyBNC: 5682























I dont know who bare@ubersource.net is .Is that a mail sent by the





system automatically. Can anyone help me get my system back on track? Thanks in advance

[U.SivaKumar_2]

hi,
There are reasons to think that Denial of service type of attack might have been carried out in your server making the following parameter to overflow.
file-max
Just check the value of that parameter currently.
#cat /proc/sys/kernel/file-max
if it shows less that 1024 then increase the value.
#echo "4096" >/proc/sys/kernel/file-max
and reboot the server.

regards,
U.SivaKumar