Hi,

In our SMP enabled environnement, I have one kid to start giving the
fooloowing assertion :
2013/04/18 04:03:43 kid1| assertion failed: ufs/ufscommon.cc:706: "sde"

I guess it is something related with the store / store rebuiding.
Maybe a malformed object in the cache store?
here the part of the log :

2013/04/18 04:03:42 kid1| Store rebuilding is 5.57% complete
2013/04/18 04:03:42 kid1| Done reading /var/cache/squid/W1 swaplog
(18735 entries)
2013/04/18 04:03:43 kid1| Accepting SNMP messages on 0.0.0.0:3401
2013/04/18 04:03:43 kid1| Accepting HTTP Socket connections at
local=0.0.0.0:3128 remote=[::] FD 12 flags=1
2013/04/18 04:03:43 kid1| assertion failed: ufs/ufscommon.cc:706: "sde"


core file is generated, but it seems to be not valid : gdb says :

gdb /usr/local/squid/sbin/squid 004/core.758
GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-32.el5_6.2)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/local/squid/sbin/squid...done.
Attaching to program: /usr/local/squid/sbin/squid, process 4
ptrace: Opération non permise.
BFD: Warning: /root/004/core.758 is truncated: expected core file size
>= 58822656, found: 20480.
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging
symbols found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Failed to read a valid object file image from memory.
Core was generated by `(squid-1) -S -f /etc/squid/squid.conf'.
Program terminated with signal 6, Aborted.
#0  0x00002b6babe7a265 in ?? ()
(gdb) bt
Cannot access memory at address 0x7fff38b1cf98
(gdb) quit






Any clue on how to get a usable core file and/or on the meaning of the
assertion ?


Thanks
Alex

Reply via email to