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

On 14/06/11 18:42, Tom Tux wrote:
> 2011/6/10 Amos Jeffries<squid3_at_treenet.co.nz>:
>> 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
> This file is not existing. I searched the whole system for files like
> "squid-*", no usefull returns.
>
>> - check that the command line:
>> "$mail_program $cache_mgr</tmp/squid-XXXXXX"
>> works as per the mail_program directive requirements.
> This is working well. "mail_program" is set to "mail". And the command
> "mail test_at_example.com</etc/group" is working well.
>
>> - check that your mail system accepts email from squid@$unique_hostname and
>> squid@$visible_hostname
> Our mail system is accepting mails from squid in several ways
> (squid_at_squidbox, squid_at_squidbox.example.com...).
>>
>> ** Email spam filters is one of several reasons why hostname must be a FQDN
>> with working rDNS.
> This does not affect mails sending by our squid.

success then?

Amos

-- 
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