Sudden unexplained crash, strange behavior

I recently upgraded to 1.1.22 on my BSD/OS 3.1 system, and after about
12 days of uptime, it died with the following error:

1998/07/28 09:16:02| www.koelner-dom.de(195.14.230.74) marked bad
1998/07/28 09:16:02| ERR_CONNECT_FAIL: http://www.koelner-dom.de/
FATAL: Received Segment Violation...dying.
1998/07/28 09:16:25| storeWriteCleanLog: Starting...

This is a switch from the previous crashes -- usually it would just
run into the maxdsiz limit and die due to an xmalloc() failure.
Turning off memory pools seems to have helped with that particular
problem.

It spent the next several minutes writing the log, but stopped at
192512 lines out of 276459, but continued to chew CPU time for another
half hour -- it seemed to still be handling requests - there was only
a couple of calls from the users, though nothing was appearing in
access.log...

1998/07/28 09:16:51| 192512 lines written so far.

Half an hour later, I sent it a TERM signal, and it said this:

1998/07/28 09:16:51| Preparing for shutdown after 825909 connections
1998/07/28 09:16:51| Waiting 30 seconds for active connections to finish

And then a couple of minutes after this, I sent it *another* TERM
signal, and it said this:

1998/07/28 09:48:39| Pinger exiting.

Then RunCache kicked in and started another instance:

1998/07/28 09:48:49| Starting Squid Cache version 1.1.22 for i386-pc-bsdi3.1...
1998/07/28 09:48:49| With 13196 file descriptors available
1998/07/28 09:48:49| Performing DNS Tests...
1998/07/28 09:48:49| Successful DNS name lookup tests...
1998/07/28 09:48:49| Started 3 'dnsserver' processes

and it proceeded to start up normally. There doesn't seem to be a
core file anywhere - I looked in /usr/local/squid/*, my cache
directory, and the log directory.

Any ideas why it might have crashed? Any ideas why it didn't complete
the log write correctly (there was plenty of disk space)? Thanks for
any suggestions you might have.

        -Mike Pelletier.
Received on Tue Jul 28 1998 - 07:25:22 MDT