Your problem is that your out of ram and the system is trying to free up memory in an aggressive manner which in turn is thrashing the system.
Get some ram or start redoing your config to use less memory per thread and such. Adam Gregoire On Mon, 2002-03-25 at 03:41, [EMAIL PROTECTED] wrote: > over the weekend i indexed at about 2800 different websites. > the problem is, that index two times crashed. the first time i could kill > it and restarted it. an index -D got all the new search results. so > everything > was ok. the second time the complete servers stopps responding... > i am not sure what exactly was the problem, it didn't really stopped it more > went absolutly slow. when you tried to telnet the server it last minutes > until > the first line of text (servename, linux-kernel version and stuff) then the > whole > thing timedout. > no service (http, ftp, telnet) was responding anymore. in the syslog i could > see lots of lines like > > kernal VM: killing http.... > > i am using suse linux 6.3, aspseek.129pre, there is enough space on harddisk > memoy 256 MB... > any hints how i could find the error.... > this was the second time now, my provider had to reboot the system.... > > Markus Rietzler > * kommunikation & online service > * RZF NRW > * Tel: 0211.4572-130 >
