Henrik Nordstrom wrote:
>
>
> On Wed, 26 Jan 2005, Rivanor P. Soares wrote:
>
>> Hi fellows.
>> My first post.
>>
>> Squid proccess is exiting with signal 6 (abort).
>>
>> Squid Cache: Version 2.5.STABLE5 running in a FreeBSD 5.2.1-RELEASE.
>>
>> Some info from /usr/local/squid/logs/cache.log:
>>
>> [2005/01/26 15:52:34, 1] utils/ntlm_auth.c:manage_squid_request(1592)
>> fgets() failed! dying..... errno=0 (Unknown error: 0)
>
>
> You need to look further up for the cause. This just tells that
> ntlm_auth exited due to Squid asking it to shut down.
>
> As your Squid is exiting with a signal 6 there should be either a FATAL:
> or "assertion failed" error message indicating why Squid exited.
>
> Regards
> Henrik
>
Hi Henrik, people.
There's no previous messages telling me why Squid has just died.
I don't want to believe that is something related to the OS version.
All I can see, maybe related, is (cache.log):
2005/01/28 09:44:03| WARNING: Disk space over limit: 179742 KB > 102400 KB
2005/01/28 09:44:14| WARNING: Disk space over limit: 174590 KB > 102400 KB
2005/01/28 09:44:25| WARNING: Disk space over limit: 169406 KB > 102400 KB
2005/01/28 09:44:36| WARNING: Disk space over limit: 164220 KB > 102400 KB
But this happens just after starting Squid, when it has just died.
Previous messages in /var/log/messages are all about nmbd, kernel, etc,
as you can see below:
Jan 28 08:47:38 webproxy kernel: arplookup 192.168.50.3 failed: host is
not on local network
Jan 28 08:47:38 webproxy kernel: arplookup 192.168.50.3 failed: host is
not on local network
Jan 28 08:56:28 webproxy nmbd[384]: [2005/01/28 08:56:28, 0]
nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(350)
Jan 28 08:56:28 webproxy nmbd[384]: find_domain_master_name_query_fail:
Jan 28 08:56:28 webproxy nmbd[384]: Unable to find the Domain Master
Browser name DOMAIN<1b> for the workgroup DOMAIN.
Jan 28 08:56:28 webproxy nmbd[384]: Unable to sync browse lists in
this workgroup.
Jan 28 09:03:47 webproxy kernel: pid 69274 (squid), uid 100: exited on
signal 6
About disk space, I believe it's not the real problem:
Filesystem Size Used Avail Capacity Mounted on
/dev/ad0s1f 25G 18G 5.4G 76% /usr
Thanks!
Regards,
-- Rivanor P. Soares Knowledge is the power. [ aka web_knows ]Received on Fri Jan 28 2005 - 16:55:56 MST
This archive was generated by hypermail pre-2.1.9 : Mon Mar 07 2005 - 12:59:36 MST