Date: Mon, 24 Jan 2005 22:22:46 -0700 From: "Justin England" <Justin@rapidcity.net> To: "Jonathan Franks" <daemon@taconic.net>, "Michael C. Shultz" <reso3w83@verizon.net> Cc: freebsd-questions@freebsd.org Subject: Re: "Too many open files" (Critical, have only one session left) Message-ID: <054801c5029d$e81e2d60$152ea8c0@killer> References: <200501202338.j0KNc3tM007836@mail-core.space2u.com><200501201559.23150.reso3w83@verizon.net> <20050124214909.65599df2.daemon@taconic.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>> > >> I have got it before and took appropriate steps using the ideas >> > >> and tips from you guys. Now I have it again: >> > >> >> > >> Current situation on my head-less system is that I do have a >> > >> single SSH session up. Unfortunately it's not authenticated as >> > >> ROOT but as an ordinary user. >> > >> >> > >> When I try a "ls" I get : >> > >> >> > >> $ ls >> > >> ls: .: Too many open files in system >> > >> >> > >> Trying a su gives: >> > >> $ su >> > >> /usr/libexec/ld-elf.so.1: Cannot open "/usr/lib/libutil.so.3" >> > >> I would like to add that depending on what the server is doing can determine the best way to attack your problem. I have had web servers go crazy at some point (my server has been /.'d (slashdot.com) once or twice) and pulling the network cable will allow my apache processes to time out and start dying off. After a few minutes, I can su and do a reboot (or whatever.) It doesn't quite "fix" the initial problem, but does allow me to enough CPU / resources to start the shutdown process. Just my $.02 from experience. Justin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?054801c5029d$e81e2d60$152ea8c0>