[Dxspider-support] spider generating dupes

Dirk Koopman djk at tobit.co.uk
Sat Nov 24 18:13:58 GMT 2001


On Sat, 2001-11-24 at 17:46, Filip Jonckers wrote:
> 
> spider is performing great until now during the cqww cw ...
> 
> but just now I'm having a problem I also had 2 weeks ago:
> I'm getting dupes - it started after spider locked up
> (all connections stopped responding)
> 

any idea why? This isn't something that happens very often. Do you have
ax25?

> I had to stop the cluster and remove the /spider/data/dupefile
> to solve the problem
> dupefile was 258048 bytes

The standard solution.

> 
> my own (duplicate) spider system has the same node connections
> (without ax25) and did'nt have this problem yet
> 
> both systems were upgraded to latest version 1.49 yesterday
> but I don't think that has something to do with it
> 
> could this be a memory problem ?
> 

No, it is a known Berkeley DB 1.85 problem. I go to a great deal of
trouble to prevent it but it isn't successful in every case. If the
system locks it is likely that the dupefile is corrupt and should be
removed then the node restarted.

It is aledged that later versions of Berkeley don't have these problems
and since most RPM based things now have DB 3.xx available I may go onto
that.

Dirk




More information about the Dxspider-support mailing list