Re: [Summary-Talk] recurring database corruption

[LynuxWorks Webmaster <webmaster@xxxxxxxx>]

I've found that when something goes wrong in Summary, which isn't all 
that often, it's best to quit it and just reboot the system (Linux). 
Without rebooting, I've seen Summary sometimes give an invalid message 
when it's restarting, saying that it's already running.  I now take 
those "unable to acquire database" messages, if they persist, as a cue 
to reboot.

Last Friday, I corrected a problem with the DNS cache file in that root 
somehow took ownership of it, and then Summary was no longer able to 
access it.  I think that's what started off the problems I had.

Since then, there have been a couple of "One of our processes exited 
abnormally!" messages in the log, so i'm having our Linux guy take a 
closer look at the computer to see if maybe something's wrong inside 
(it's getting old).

I didn't get to testing my logs with Summary on my Windows box yet, 
since things look like they're stabilizing again.  So I'm hoping it's 
back to normal for this week...

Kevin





Scott Marjason said:

 >
 > 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.
 >
-------------
Go to <http://summary.net/list.html> to update subscription info.