[Summary-Talk] recurring database corruption

[LynuxWorks Webmaster <webmaster@xxxxxxxx>]

A little over a week ago, I started getting database corruption on most 
processing runs.  It seems to occur usually at the end of a processing 
run, but not always.  Summary doesn't crash per se, it just gives 
eternal "Processing, database not available messages" to the web window 
once it stops functioning.

When this started, I was using 2.3.9 (Linux), but upgraded to 2.3.10 
just in case it might help (it didn't).

I've done lots of testing and at one point came to the conclusion that 
one of my log files was somehow corrupted, but when I tried to generate 
a report using just that one log by itself, it worked fine, so I'm still 
scratching my head.

Then I thought there was maybe a problem in the DNS lookups since 
reports were often intact while calcualtions were ongoing, and the 
reports only became inaccessible at the end of a processing run.

However, the behaviour is not consistent, so I'm at a bit of loss as to 
how to best describe what's going on.  For example, this morning's 
attempt at a processing run didn't get any further than "Load/initialize 
binary database,"  which is not typical of what I've been seeing over 
the past week.

I've been erasing the report.dat and curvisits.gz files and rebooting my 
system most of the time.

This problem just came out of nowhere and is a little weird since 
Summary has done really well with handling two years worth of logs, and 
now I can't even get reports for last month.

What else should I look for that might help diagnose this?

Thanks,
Kevin Cook
-------------
Go to <http://summary.net/list.html> to update subscription info.