[Dxspider-support] dxcluster locked and eating all cpu power

[Dirk Koopman]

As a start, with silly weird problems like this that 'suddenly' appear
one day: remove the /spider/data/dupefile.

This sees to cure a lot of these problems.

After that, recreate the user file from backup by doing:

cd /spider/data
perl user_asc

It appears that the berkeley db 1.85/6 library on most machines is very
sensitive to computers crashing and leaving the file in some undefined
state. This has been long cured in later versions, these are not easily
available on (for instance) Windows boxes with perl bindings.

So until that happens we are stuck with the standard library with its
little foibles.

Dirk G1TLH

On Sat, 2003-07-12 at 17:47, Nuno Sucena Almeida wrote:
> hello,
> 
> 	I'm having a weird problem, but it's not new to me. I have the
> latest cvs version running and when the software starts and after updating
> the spots list it simply locks up and does not respond to connections, 
> although accepting them. Then it stays there, consuming all the cpu
> power. The system was working fine for about 2 weeks but today I had a 
> power failure. This machine is running debian with kernel 2.4.21 and a scsi 
> reiserfs disk.
> 	The strange thing is that I had this same problem with another
> machine, an old 486 running 2.4.16 / ide ext2 disk, but about one year ago, 
> also running the latest CVS version at that time.
> 	Is there any file or lock that was corrupted and I should be aware?
> 
> 			73,
> 				Nuno
-- 
Please Note: Some Quantum Physics Theories Suggest That When the
Consumer Is Not Directly Observing This Product, It May Cease to
Exist or Will Exist Only in a Vague and Undetermined State.