We use Squid with samba for NTLM authentication. Last night I started to see a few entries here and there , then they started to show more and more: [2006/04/05 21:29:56, 3] utils/ntlm_auth.c:winbind_pw_check(427) Login for user [domainname]\[username]@[computername] failed due to [No logon servers] [2006/04/05 21:30:05, 3] libsmb/ntlmssp.c:debug_ntlmssp_flags(62) Got NTLMSSP neg_flags=0xa208b207 Then eventually I got this: 2006/04/05 21:30:52| WARNING: All ntlmauthenticator processes are busy. 2006/04/05 21:30:52| WARNING: up to 30 pending requests queued And finally: 2006/04/05 21:31:23| WARNING: All ntlmauthenticator processes are busy. 2006/04/05 21:31:23| WARNING: up to 78 pending requests queued 2006/04/05 21:31:23| Consider increasing the number of ntlmauthenticator processes to at least 108 in your config file. 2006/04/05 21:31:53| WARNING: All ntlmauthenticator processes are busy. 2006/04/05 21:31:53| WARNING: up to 104 pending requests queued 2006/04/05 21:31:53| Consider increasing the number of ntlmauthenticator processes to at least 134 in your config file. 2006/04/05 21:32:24| WARNING: All ntlmauthenticator processes are busy. 2006/04/05 21:32:24| WARNING: up to 122 pending requests queued 2006/04/05 21:32:24| Consider increasing the number of ntlmauthenticator processes to at least 152 in your config file. 2006/04/05 21:32:57| WARNING: All ntlmauthenticator processes are busy. 2006/04/05 21:32:57| WARNING: up to 141 pending requests queued 2006/04/05 21:32:57| Consider increasing the number of ntlmauthenticator processes to at least 171 in your config file. 2006/04/05 21:33:08| storeDirWriteCleanLogs: Starting... 2006/04/05 21:33:08| WARNING: Closing open FD 8 2006/04/05 21:33:08| 65536 entries written so far. 2006/04/05 21:33:08| 131072 entries written so far. 2006/04/05 21:33:08| 196608 entries written so far. 2006/04/05 21:33:08| 262144 entries written so far. 2006/04/05 21:33:08| 327680 entries written so far. 2006/04/05 21:33:08| 393216 entries written so far. 2006/04/05 21:33:08| 458752 entries written so far. 2006/04/05 21:33:08| Finished. Wrote 479124 entries. 2006/04/05 21:33:08| Took 0.2 seconds (2533144.4 entries/sec). FATAL: Too many queued ntlmauthenticator requests (151 on 30) Squid Cache (Version 2.5.STABLE12-20060308): Terminated abnormally. CPU Usage: 14647.640 seconds = 4194.872 user + 10452.768 sys Maximum Resident Size: 0 KB Page faults with physical i/o: 0 Memory usage for squid via mallinfo(): total space in arena: 70616 KB Ordinary blocks: 66415 KB 278 blks Small blocks: 0 KB 0 blks Holding blocks: 1832 KB 2 blks Free Small blocks: 0 KB Free Ordinary blocks: 4200 KB Total in use: 68247 KB 97% Total free: 4200 KB 6% 2006/04/05 21:33:12| Starting Squid Cache version 2.5.STABLE12-20060308 for i686-pc-linux-gnu... 2006/04/05 21:33:12| Process ID 29670 2006/04/05 21:33:12| With 8192 file descriptors available 2006/04/05 21:33:12| Performing DNS Tests... FATAL: ipcache_init: DNS name lookup tests failed. Squid Cache (Version 2.5.STABLE12-20060308): Terminated abnormally. CPU Usage: 0.004 seconds = 0.003 user + 0.001 sys Maximum Resident Size: 0 KB Page faults with physical i/o: 0 It then kept repeating the following for about 8 cycles then stopped: 2006/04/05 21:36:35| Starting Squid Cache version 2.5.STABLE12-20060308 for i686-pc-linux-gnu... 2006/04/05 21:36:35| Process ID 29684 2006/04/05 21:36:35| With 8192 file descriptors available 2006/04/05 21:36:35| Performing DNS Tests... FATAL: ipcache_init: DNS name lookup tests failed. Squid Cache (Version 2.5.STABLE12-20060308): Terminated abnormally. CPU Usage: 0.006 seconds = 0.003 user + 0.003 sys Maximum Resident Size: 0 KB Page faults with physical i/o: 0 This morning I got my alert and restarted and it worked fine. It appears it could not find a domain control or as the log states a DNS server. I cant see why, I have no record of it being down. Can anyone make light of this situation, or is it safe to assume that squid just couldn't see a DC/DNS and gave up. - Nick --------------------- Confidentiality note The information in this email and any attachment may contain confidential and proprietary information of VistaPrint and/or its affiliates and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may cause liability. In case you have received this message due to an error in transmission, please notify the sender immediately and to delete this email and any attachment from your system. ---------------------
