Re[2]: [squid-users] fake_auth exiting with signal 11

From: George G. Zavyalov <[email protected]>
Date: Tue, 8 Jan 2002 13:22:46 +0300

Glad to greet you, Robert.

You wrote 26 December 2001., 15:44:40:

..........
>> The problem is that fake_auth crashes with signal 11 PERIODICALLY,
>> with this sort of diagnostics ( -X squid option):
>>
..........
>>
>> From one hand the tandem "squid - fake_auth" is all that we
>> need now. This exeption situation is controlled by the parent
RC> process, reloading
>> the child, when it terminates abnormally. From the other hand, i
>> must find network event, that caused fake_auth crash. We are
>> waiting the ranging of our network to the number of about one
RC> hundred
>> http-clients. And i need the interpretation of that
RC> "ntlmGetString: insane: l:0 o:64"
>> diagnostics. What is this "insane" packet?
..........
RC> fakeauth can be made more robust, and I'll do something for this bug
RC> shortly. Can you tell me the info I've asked for above?

 It looks like that after some experiments we found this critical
 periodical network event. That is automatic (and non-automatic)
 renewation of antivirus database of Antiviral Toolkit
 Pro (http://www.avp.ru - English HTML version is also available).
 For example:

bash-2.05$ zcat /var/log/messages.0.gz|grep 'signal 11'
Dec 29 12:31:03 proxy /kernel: pid 51002 (fakeauth_auth), uid 1000: exited on signal 11
Dec 29 13:13:26 proxy /kernel: pid 51247 (fakeauth_auth), uid 1000: exited on signal 11
Dec 29 13:31:03 proxy /kernel: pid 51439 (fakeauth_auth), uid 1000: exited on signal 11
Dec 29 19:31:06 proxy /kernel: pid 51568 (fakeauth_auth), uid 1000: exited on signal 11
Dec 31 19:31:04 proxy /kernel: pid 52614 (fakeauth_auth), uid 1000: exited on signal 11
Jan 1 19:31:10 proxy /kernel: pid 64029 (fakeauth_auth), uid 1000: exited on signal 11 (core dumped)
Jan 2 19:31:06 proxy /kernel: pid 66367 (fakeauth_auth), uid 1000: exited on signal 11
Jan 3 19:31:06 proxy /kernel: pid 75975 (fakeauth_auth), uid 1000: exited on signal 11 (core dumped)
Jan 4 12:31:04 proxy /kernel: pid 76440 (fakeauth_auth), uid 1000: exited on signal 11
Jan 4 13:31:05 proxy /kernel: pid 79816 (fakeauth_auth), uid 1000: exited on signal 11
Jan 4 19:31:12 proxy /kernel: pid 80057 (fakeauth_auth), uid 1000: exited on signal 11
bash-2.05$ cat /var/log/messages|grep 'signal 11'
Jan 6 19:31:09 proxy /kernel: pid 81129 (fakeauth_auth), uid 1000: exited on signal 11
Jan 7 19:31:07 proxy /kernel: pid 92379 (fakeauth_auth), uid 1000: exited on signal 11
Jan 8 10:31:09 proxy /kernel: pid 96986 (fakeauth_auth), uid 1000: exited on signal 11
Jan 8 10:52:15 proxy /kernel: pid 140 (fakeauth_auth), uid 1000: exited on signal 11
 
During two periods - first: from Dec 29 till Jan 3 and the second: from Jan 4
till Jan 7 - only renewation on domain server was started. At the other
days renewation on client machines was started additionally.

Event with timestamp Jan 8 10:52:15 was initiated manually.

And do you need produced fakeauth_auth.core dump ?

-- 
Respectfully,
 George                          mailto:squid-mailing@altervita.com.ru
Received on Tue Jan 08 2002 - 03:22:42 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:05:41 MST