[Summary-Talk] Why is summary so unreliable?

[Bret Baptist <bbaptist@xxxxxxxxxxxxx>]

My company has posted many times to this list with problems of reliability 
from summary.  Usually it takes rerunning full stats multiple times to get a 
successful stats report, then summary will run for a few days, then we will 
get crashes and a corrupt database on restart.  This is just not acceptable.

My most current example is a new report we added, brand new site, no traffic, 
summary crashes running it's report.  I look in summary's logs, (which are 
extremely unhelpful) and find this:

 "summary: snaz/Process.cpp:2540: void Process(unsigned char, unsigned char, 
unsigned char): Assertion `!sets[sptr->h.name-1]' failed.

Ok... so I restart summary thinking that on the next run maybe the dice will 
roll in my favor, no luck, I now have a corrupt database after the restart.  
Great this means I get to run 15GB of logs again, really fun.


So I guess my question is what can be done to make summary less fragile?  I 
hesitate to even look at the thing for fear of it breaking, let alone adding 
or removing reports.


Sorry if this sound rantish, we were without website reporting from summary 
for almost a month while it crashed everynight until it mysteriously started 
working again.


-- 
Bret Baptist
Systems and Technical Support Specialist
bbaptist@iexposure.com
Internet Exposure, Inc.
http://www.iexposure.com
 
(612)676-1946 x17
Web Development-Web Marketing-ISP Services
------------------------------------------


Today is the tomorrow you worried about yesterday.
-------------
Go to <http://summary.net/list.html> to update subscription info.