[squid 0005163]: squid 3.4.4 crashes on Solaris 10
Mantis Bug Tracker via bug-notifications
bug-notifications at lists.opencsw.org
Fri May 2 15:52:38 CEST 2014
A NOTE has been added to this issue.
======================================================================
https://www.opencsw.org/mantis/view.php?id=5163
======================================================================
Reported By: hudesd
Assigned To: dam
======================================================================
Project: squid
Issue ID: 5163
Category: regular use
Reproducibility: have not tried
Severity: crash
Priority: normal
Status: feedback
======================================================================
Date Submitted: 2014-04-11 23:13 CEST
Last Modified: 2014-05-02 15:52 CEST
======================================================================
Summary: squid 3.4.4 crashes on Solaris 10
Description:
I have been using Squid 3.1 for quite awhile with no problem. I recently
upgraded all my CSW packages and Squid 3.4.4 came with it, no option
otherwise it's in stable/unstable/testing.
The problem is that it is NOT stable: it exits after awhile.
It's running as a service (cswsquid) as per the package.
This on a T2000 Solaris 10 148888-05 with 8GB RAM and about 600GB of
available disk space .
I had made no change to the configuration between 3.1 and 3.4. I
subsequently have tried both aufs and my original ufs (diskd isn't
available) to no avail.
I increased the size of the disk and memory cache to no avail.
Squid will run happily as long as users are only tunneling through it; once
some caching gets going with regular http it exits.
I'm not finding any core dumps in /var/opt/csw/squid/cache or the 00
directory under that.
I can provide squid config files and log files.
======================================================================
----------------------------------------------------------------------
(0010815) dam (administrator) - 2014-05-02 15:52
https://www.opencsw.org/mantis/view.php?id=5163#c10815
----------------------------------------------------------------------
I have now an idea what goes wrong: when retreiving something via FTP squid
dumps core. Here is the stacktrace:
pstack core.squid.8044
core 'core.squid.8044' of 8044: (squid-1) -D
fe6c8e07 _lwp_kill (1, 6, feffe248, fe670ff1) + 7
fe670ffd raise (6, 0, feffe298, fe6487ad) + 25
fe6487cd abort (0, 1, 2b, 8647430, fe766c80, fe762000) + f5
082a2b2d _Z5deathi (b, 0, feffe3e0, fe69e537, fdf72a40, fe762000) + 1cd
fe6c4b05 __sighndlr (b, 0, feffe3e0, 82a2960) + 15
fe6b7eae call_user_handler (b) + 2d2
fe6b8346 sigacthandler (b, 0, feffe3e0) + ee
--- called from signal handler with signal 11 (SIGSEGV) ---
083434c5 _ZNK2Ip7Address4portEv (4, fe762000, feffe998, fe661667, 965adf0,
fe762000) + 15
081c7c01 ???????? (913fdac, 845f909, feffea08, fe6bd29c, 97bb4a0,
fe762000)
081c97bf ???????? (913bca0, 25, 913fda8, feffeabc, b9, 25)
081c8bd9 _ZN12FtpStateData18handleControlReplyEv (913bca0, 94c2048,
832f25b, 94c2040, 94c2020) + 149
081ce2a2 _ZN13CommCbMemFunTI12FtpStateData14CommIoCbParamsE6doDialEv
(94c203c, 94c2020, feffeb28, 81cdc03, 94c2040, fe762000) + 32
081ce013 _ZN9JobDialerI12FtpStateDataE4dialER9AsyncCall (94c203c, 94c2020,
feffeb58, fe661c5a, fe763098, 84a4020) + 33
081ce178
_ZN10AsyncCallTI13CommCbMemFunTI12FtpStateData14CommIoCbParamsEE4fireEv
(94c2020, 84a137f, feff1b7f, 81a9daf, 88000000, 4056e1fc) + 18
0832d42d _ZN9AsyncCall4makeEv (94c2020, feffecc4, e650d871, fe76930c,
cf5d3200, 8) + 3bd
083317b6 _ZN14AsyncCallQueue8fireNextEv (86b1a70, feffecdc, feffec08,
82a0d4a, 86086f0, 0) + 1f6
08331ba0 _ZN14AsyncCallQueue4fireEv (86b1a70, feffecb0, 1, 842e5f9, 40,
402e0000) + 30
081aadd4 _ZN9EventLoop7runOnceEv (feffecdc, 402e0000, 1, feffecb0, 0,
feffecb4) + 104
081aaf70 _ZN9EventLoop3runEv (feffecdc, feffecb4, 0, 0, 402e0000, 1) + 20
0822b2d4 _Z9SquidMainiPPc (2, feffed60, 84a4020, feffed1c, feffed3c,
fe7fa8bc) + 14b4
08430c7d main (2, feffed60, feffed6c) + 1d
0811f2e0 _start (2, feffee38, feffee42, 0, 86b60b0, feffee5d) + 80
dam at unstable10s [unstable10s]:/home/dam/tmp > cat yyy |
/opt/SUNWspro/bin/c++filt
core 'core.squid.8044' of 8044: (squid-1) -D
fe6c8e07 _lwp_kill (1, 6, feffe248, fe670ff1) + 7
fe670ffd raise (6, 0, feffe298, fe6487ad) + 25
fe6487cd abort (0, 1, 2b, 8647430, fe766c80, fe762000) + f5
082a2b2d death(int) (b, 0, feffe3e0, fe69e537, fdf72a40, fe762000) + 1cd
fe6c4b05 __sighndlr (b, 0, feffe3e0, 82a2960) + 15
fe6b7eae call_user_handler (b) + 2d2
fe6b8346 sigacthandler (b, 0, feffe3e0) + ee
--- called from signal handler with signal 11 (SIGSEGV) ---
083434c5 Ip::Address::port() const (4, fe762000, feffe998, fe661667,
965adf0, fe762000) + 15
081c7c01 ???????? (913fdac, 845f909, feffea08, fe6bd29c, 97bb4a0,
fe762000)
081c97bf ???????? (913bca0, 25, 913fda8, feffeabc, b9, 25)
081c8bd9 FtpStateData::handleControlReply() (913bca0, 94c2048, 832f25b,
94c2040, 94c2020) + 149
081ce2a2 CommCbMemFunT<FtpStateData, CommIoCbParams>::doDial() (94c203c,
94c2020, feffeb28, 81cdc03, 94c2040, fe762000) + 32
081ce013 JobDialer<FtpStateData>::dial(AsyncCall&) (94c203c, 94c2020,
feffeb58, fe661c5a, fe763098, 84a4020) + 33
081ce178 AsyncCallT<CommCbMemFunT<FtpStateData, CommIoCbParams> >::fire()
(94c2020, 84a137f, feff1b7f, 81a9daf, 88000000, 4056e1fc) + 18
0832d42d AsyncCall::make() (94c2020, feffecc4, e650d871, fe76930c,
cf5d3200, 8) + 3bd
083317b6 AsyncCallQueue::fireNext() (86b1a70, feffecdc, feffec08, 82a0d4a,
86086f0, 0) + 1f6
08331ba0 AsyncCallQueue::fire() (86b1a70, feffecb0, 1, 842e5f9, 40,
402e0000) + 30
081aadd4 EventLoop::runOnce() (feffecdc, 402e0000, 1, feffecb0, 0,
feffecb4) + 104
081aaf70 EventLoop::run() (feffecdc, feffecb4, 0, 0, 402e0000, 1) + 20
0822b2d4 SquidMain(int, char**) (2, feffed60, 84a4020, feffed1c, feffed3c,
fe7fa8bc) + 14b4
08430c7d main (2, feffed60, feffed6c) + 1d
0811f2e0 _start (2, feffee38, feffee42, 0, 86b60b0, feffee5d) + 80
Digging further.
More information about the bug-notifications
mailing list