Re: [squid-users] assertion failed: errorpage.c:292: "mem->inmem_hi == 0" - squid exiting on signal 6

Please file a bug report per the instructions in the Squid FAQ.

Also include the exact Squid version you are using, including which
patches (if any) you have applied.

Regards
Henrik

On Tue, 15 Jun 2004, Gaylord Van Brocklin wrote:

> Ok.. it just crashed again after about 2 hours, around the same memory
> usage size:
>
> core trace:
>
> squid01# gdb squid squid.core
> GNU gdb 4.18 (FreeBSD)
> Copyright 1998 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and
> you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for
> details.
> This GDB was configured as "i386-unknown-freebsd"...
> Core was generated by `squid'.
> Program terminated with signal 6, Abort trap.
> Reading symbols from /usr/lib/libcrypt.so.2...done.
> Reading symbols from /usr/lib/libm.so.2...done.
> Reading symbols from /usr/lib/libc.so.4...done.
> Reading symbols from /usr/libexec/ld-elf.so.1...done.
> #0 0x68178b0c in kill () from /usr/lib/libc.so.4
> (gdb) where
> #0 0x68178b0c in kill () from /usr/lib/libc.so.4
> #1 0x681b8ef6 in abort () from /usr/lib/libc.so.4
> #2 0x80b5328 in death (sig=11) at tools.c:303
> #3 0xbfbfffac in ?? ()
> #4 0x80842e0 in httpStateFree (fd=457, data=0x9c2d710) at http.c:68
> #5 0x806ad0f in commCallCloseHandlers (fd=457) at comm.c:574
> #6 0x806af1e in comm_close (fd=457) at comm.c:656
> #7 0x80855b4 in httpReadReply (fd=457, data=0x9c2d710) at http.c:617
> #8 0x806cb1f in comm_poll (msec=8) at comm_select.c:445
> #9 0x8094d9e in main (argc=1, argv=0xbfbffdc4) at main.c:743
> #10 0x804a3e9 in _start ()
>
> From logs:
> FATAL: Received Segment Violation...dying.
> 2004/06/15 15:10:21| storeDirWriteCleanLogs: Starting...
> 2004/06/15 15:10:21| WARNING: Closing open FD 10
> 2004/06/15 15:10:21| 65536 entries written so far.
> 2004/06/15 15:10:21| 131072 entries written so far.
> 2004/06/15 15:10:22| 196608 entries written so far.
> 2004/06/15 15:10:22| 262144 entries written so far.
> 2004/06/15 15:10:22| 327680 entries written so far.
> 2004/06/15 15:10:22| 393216 entries written so far.
> 2004/06/15 15:10:22| 458752 entries written so far.
> 2004/06/15 15:10:22| 524288 entries written so far.
> 2004/06/15 15:10:22| 589824 entries written so far.
> 2004/06/15 15:10:22| 655360 entries written so far.
> 2004/06/15 15:10:23| 720896 entries written so far.
> 2004/06/15 15:10:23| 786432 entries written so far.
> 2004/06/15 15:10:23| 851968 entries written so far.
> 2004/06/15 15:10:23| 917504 entries written so far.
> 2004/06/15 15:10:23| Finished. Wrote 945384 entries.
> 2004/06/15 15:10:23| Took 2.1 seconds (453745.4 entries/sec).
> CPU Usage: 7377.764 seconds = 3850.927 user + 3526.837 sys
> Maximum Resident Size: 1015968 KB
> Page faults with physical i/o: 0
>
> Jun 15 15:11:18 s067sqd01 /kernel: pid 86715 (squid), uid 65534: exited
> on signal 6 (core dumped)
> Jun 15 15:11:18 s067sqd01 squid[76758]: Squid Parent: child process
> 86715 exited due to signal 6
>
> -gvb
>
> On Jun 15, 2004, at 2:10 PM, Henrik Nordstrom wrote:
>
> > On Tue, 15 Jun 2004, Gaylord Van Brocklin wrote:
> >
> >> I spoke to soon... we have a new issue. This just happened after
> >> running fine for a few hours:
> >>
> >> From cache.log:
> >> FATAL: Received Segment Violation...dying.
> >
> > On all Segmentation Violation errors please see the Squid FAQ on how to
> > report bugs. Back trace or reliable test case reproducing the problem
> > is
> > required to be able to process the bug report.
> >
> > Regards
> > Henrik
> >
>
Received on Tue Jun 15 2004 - 17:25:27 MDT