Re: [Summary-Talk] recurring database corruption

[Scott Marjason <scott@xxxxxxxxxxxxxxxxxx>]

I'm having this problem as well. After nothing working right with 
FreeBSD, I wiped the server and installed Linux. Still having the 
same problem, though it doesn't complain about quitting.

~/data/summary.log looks like:

...
Read 92,269 entries in 0:03!
1111 (of 1844860) IPs to be resolved, checking the DNS cache file.
6 corrupt lines in the DNS lookup cache were ignored.
Matched 0/1111 IPs from the cache file.
Saving binary report database.
Starting DNS lookups.
Running for 9 day(s) 6 hour(s) 34 minutes at Dec 12, 2003 03:52PM.
Running for 9 day(s) 7 hour(s) 4 minutes at Dec 12, 2003 04:22PM.
Processing didn't start: Processing currently in progress!
Set web browser to "http://my.server.com:8000/".
Running for 9 day(s) 7 hour(s) 34 minutes at Dec 12, 2003 04:52PM.
Running for 9 day(s) 8 hour(s) 4 minutes at Dec 12, 2003 05:22PM.
Processing didn't start: Processing currently in progress!
Set web browser to "http://my.server.com:8000/".
Running for 9 day(s) 8 hour(s) 34 minutes at Dec 12, 2003 05:52PM.
Running for 9 day(s) 9 hour(s) 4 minutes at Dec 12, 2003 06:22PM.
Processing didn't start: Processing currently in progress!
...

  /var/logs/messages makes no mention of summary. I am using 2.3.10.

It has been taking about 8-9 days for it to start giving "Unable to 
acquire database access, please try again in a moment!" when trying 
to access a report. This is pretty new hardware and I've already 
tried running a RAM test, which turned out fine.



>On 12/15/03 1:39 PM LynuxWorks Webmaster (webmaster@lnxw.com) wrote:
>
>>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?
>
>It sounds like Summary's log processing or DNS lookup thread is crashing
>or hanging up somehow, while the UI portion continues to work. Everything
>you describe is consistent with that. There is likely to be more
>information about what is going on in Summary's log file,
>"./data/summary.log" (Linux, Sun, OS X Command Line, Windows as a
>service). It is also worth checking your /var/log/messages file (Linux)
>to see if there is anything in there that matches up with the times when
>access locks up.
>
>Problems like this one can occur because of hardware problems, typically
>marginal RAM. They might also indicate a bug in Summary. Version 2.3.10
>has proven to be very stable, I would not expect to find a new problem in
>that version of Summary, but it is certainly possible. One good way to
>rule out hardware problems is to run Summary on the same logs on a
>different machine, if you have one available. If it also fails on the new
>machine then it is presumably a Summary problem.

-- 

Scott Marjason_____________________________
                             Insignia Design
                            1136 St. Gregory
                                   Suite 100
                        Cincinnati, OH 45202
                      www.insigniadesign.com
___________________________________________
513.784.1100 Phone
513.784.0011 Fax
-------------
Go to <http://summary.net/list.html> to update subscription info.