Re: [squid-users] A way/hack to force squid to die?

On 10/06/11 20:41, Tom Tux wrote:
> Mmm...
>
> Now I were able to force squid to die (with gdb):
>
> From cache.log:
> --- SNIP ---
> (squid)(death+0x37)[0x564d37]
> /lib64/libpthread.so.0(+0xf5d0)[0x7f99ebe705d0]
> FATAL: Received Segment Violation...dying.
> 2011/06/10 10:37:28.408| storeDirWriteCleanLogs: Starting...
> 2011/06/10 10:37:28.409| assertion failed: comm.cc:301: "data ==
> COMMIO_FD_READCB(fd)"
> --- SNAP ---
>
> But there is no mail sent to the mailaddress defined on the
> "cache_mgr"-directive. I made also a tcpdump on port 25 to check, if
> there even a mail is sent. But no packets on port 25, no mail.
>

Hmm,
  - check for a file /tmp/squid-XXXXXX
  - check that the command line:
    "$mail_program $cache_mgr </tmp/squid-XXXXXX"
  works as per the mail_program directive requirements.
  - check that your mail system accepts email from
squid@$unique_hostname and squid@$visible_hostname

  ** Email spam filters is one of several reasons why hostname must be a
FQDN with working rDNS.

Amos

>
> 2011/6/10 Helmut Hullen<Hullen_at_t-online.de>:
>> Hallo, Tom,
>>
>> Du meintest am 10.06.11:
>>
>>> From squid.conf.documented:
>>> -+- SNIP ---
>>> # TAG: cache_mgr
>>> # Email-address of local cache manager who will receive
>>> # mail if the cache dies. The default is "webmaster."
>>
>> "if the cache dies"
>>
>> That's another thing than a dying squid.
>>
>> Viele Gruesse!
>> Helmut
>>

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.12
   Beta testers wanted for 3.2.0.8 and 3.1.12.2