Seems like something weirds happened on your system. Probably this is a problem with the kernel, or hardware.
Anyway, in such situations try # strace -p <pid_of_some_index_thread> first, to see where it hangs. Also, I recommend everybody to run a program from www.memtest86.org, for at least half a day. Gregory Kozlovsky wrote: > Hello, ASPseekers, > > I started an index yesterday and today have found that it have hanged. The > index processes > were still running, but no new documents were indexed. When I tried to stop > the index with > index -E, this command also hanged and failed to stop the indexing > processes. There > were messages like this: > > Read pipe in resolver process 4827 is broken, exiting > Read pipe in resolver process 4832 is broken, exiting > Read pipe in resolver process 4830 is broken, exiting > > Then I tried "killall index" without any result. And then kill -9 on > individual threads, which > also failed to kill the threads. Finally, the only option was to reboot the > machine. I did not > find any indications I can understand in the dlog (by the way, dlog has no > timestamps and > it is impossible to know when a message was written). > > Anyway, may be the developers or other users know how this situation can > arise and > what to do about it. > > Gregory Kozlovsky > > Project Manager for Information Systems Tel: +41 (0)1 632 63 > 70 > International Relations and Security Network (ISN) Fax: +41 (0)1 632 14 > 13 > Center for Security Studies and Conflict Research Email: > [EMAIL PROTECTED] > Swiss Federal Institute of Technology (ETH) http://www.isn.ch > Leonhardshalde 21, ETH-Zentrum / LEH > CH-8092 Z�rich, Switzerland > > -- [EMAIL PROTECTED] 7551596@ICQ [EMAIL PROTECTED] Dream like you'll live forever...Love like you've never been hurt... Work like you don't need the money...and Dance like nobody is watching! -- Satchel Paige
