On October 22, 1998 at 19:06, Jeff Breidenbach wrote:
Here's an update to the error code 139 incident described earlier.
(like you care!, but hey...)
After digging around more on the return code 139, it again it appears
to be database corruption, with a missing apostrophe in the DB file.
Unfortunately, there is no easy way to know what the problem is
unless it can be reproduced with a known set of steps.
Since it appears to happen to only 2 lists, maybe an examiniation of
the messages that go to lists may help. A simulator could be setup where
the original messages are piped into mhonarc (using a test archive) one
at time in a manner similiar to how mhonarc is invoked in production
to see if the problem occurs.
A check for abnormally large messages and.or bad rc file may bring
up something. Do you have process size limits in place? Are
there any temp files left around in the two archives causing you
BTW, could you compress some of the data you put up on your FTP
site? The .mhonarc.db file is huge, and compressing it will make
download muck quicker.
Earl Hood | University of California: Irvine
ehood(_at_)medusa(_dot_)acs(_dot_)uci(_dot_)edu | Electronic
http://www.oac.uci.edu/indiv/ehood/ | Dabbler of SGML/WWW/Perl/MIME