Assertion failure with Squid2.2-STABLE-2

After about a week of uptime... I got an assertion failure in the cache.log, and
it crumbled to nothing.

The Cache had lasted about a week, growing to some 106M process size, with 32M
cache ram assigned along with
200M disk cache sizes. The README had suggested the process size might grow to
some 3 times the size of the cache RAM.

Last few lines of cache.log were...

1999/05/14 15:23:31| sslReadClient: FD 29: read failure: (104) Connection reset
by peer
1999/05/14 15:23:31| sslReadClient: FD 38: read failure: (104) Connection reset
by peer
1999/05/14 15:23:31| sslReadClient: FD 24: read failure: (104) Connection reset
by peer
1999/05/14 15:23:44| sslReadClient: FD 19: read failure: (104) Connection reset
by peer
1999/05/14 15:23:44| sslReadClient: FD 28: read failure: (104) Connection reset
by peer
1999/05/14 15:37:54| sslReadClient: FD 41: read failure: (104) Connection reset
by peer
1999/05/14 15:38:13| sslReadClient: FD 38: read failure: (104) Connection reset
by peer
1999/05/14 16:18:27| urlParse: Illegal character in hostname 'teen chat'
1999/05/14 16:43:57| assertion failed: store.c:404: "e->store_status ==
STORE_PENDING"

Any ideas, folks?

Ted Rule,
Flextech Television.
Received on Fri May 14 1999 - 10:13:41 MDT