Hello, We're running analog 5.22, and are unfortunately running into a crash on a nightly basis.
Things were going OK with Analog 4.0x before, but our site has been getting busier, and after it hit 90 MB or so in process size, it would run out of memory and shut down. So I upgraded to 5.22 -- and now we get a crash. I suspect this is in the file report, but since the output hasn't been flushed, I'm not exactly sure how far it gets. Running on NetBSD/Alpha 1.4.1, 320 MB free (and 100-200 MB typically used by httpd processes). We are averaging (uncompressed) log file sizes of about 50 MB per day, with 50,000 pages and 400,000 hits served per day. We run analog from crontab daily for month to date and for the previous day. Everything was wonderfule for well over the year, until the traffic hit some magical limit recently. Neither one works now. :-( Is there some way to track down what's causing the segmentation fault? Tom Haapanen [EMAIL PROTECTED] +------------------------------------------------------------------------ | This is the analog-help mailing list. To unsubscribe from this | mailing list, go to | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | List archives are available at | http://www.mail-archive.com/[email protected]/ | http://lists.isite.net/listgate/analog-help/archives/ | http://www.tallylist.com/archives/index.cfm/mlist.7 +------------------------------------------------------------------------
