Marco Berizzi wrote:
> Hello everybody.
> This morning squid-2.5STABLE6 has crashed because
> all ntlm authenticator processes were busy. This is
> the relevant log's part:
>
> 08:47:36| WARNING: All ntlmauthenticator processes are busy.
> 08:47:36| WARNING: up to 40 pending requests queued
> 08:48:54| WARNING: All ntlmauthenticator processes are busy.
> 08:48:54| WARNING: up to 42 pending requests queued
> 08:48:54| Consider increasing the number of ntlmauthenticator processes
> to at least 82 in your config file.
> 09:04:34| WARNING: All ntlmauthenticator processes are busy.
> 09:04:34| WARNING: up to 44 pending requests queued
> 09:07:53| WARNING: All ntlmauthenticator processes are busy.
> 09:07:53| WARNING: up to 45 pending requests queued
> 09:07:53| Consider increasing the number of ntlmauthenticator processes
> to at least 85 in your config file.
> 09:08:28| WARNING: All ntlmauthenticator processes are busy.
> 09:08:28| WARNING: up to 47 pending requests queued
> 09:08:28| Consider increasing the number of ntlmauthenticator processes
> to at least 87 in your config file.
> 09:18:04| WARNING: All ntlmauthenticator processes are busy.
> 09:18:04| WARNING: up to 49 pending requests queued
> 09:23:22| WARNING: All ntlmauthenticator processes are busy.
> 09:23:22| WARNING: up to 50 pending requests queued
> 09:37:58| WARNING: All ntlmauthenticator processes are busy.
> 09:37:58| WARNING: up to 51 pending requests queued
> 09:38:28| WARNING: All ntlmauthenticator processes are busy.
> 09:38:28| WARNING: up to 52 pending requests queued
> 09:38:28| Consider increasing the number of ntlmauthenticator processes
> to at least 92 in your config file.
> 09:38:59| WARNING: All ntlmauthenticator processes are busy.
> 09:38:59| WARNING: up to 54 pending requests queued
> 09:38:59| Consider increasing the number of ntlmauthenticator processes
> to at least 94 in your config file.
> 09:39:30| WARNING: All ntlmauthenticator processes are busy.
> 09:39:30| WARNING: up to 56 pending requests queued
> 09:39:30| Consider increasing the number of ntlmauthenticator processes
> to at least 96 in your config file.
> 09:40:00| WARNING: All ntlmauthenticator processes are busy.
> 09:40:00| WARNING: up to 59 pending requests queued
> 09:40:00| Consider increasing the number of ntlmauthenticator processes
> to at least 99 in your config file.
> 09:40:31| WARNING: All ntlmauthenticator processes are busy.
> 09:40:31| WARNING: up to 60 pending requests queued
> 09:40:31| Consider increasing the number of ntlmauthenticator processes
> to at least 100 in your config file.
> 09:41:12| WARNING: All ntlmauthenticator processes are busy.
> 09:41:12| WARNING: up to 62 pending requests queued
> 09:41:12| Consider increasing the number of ntlmauthenticator processes
> to at least 102 in your config file.
> 09:42:27| WARNING: All ntlmauthenticator processes are busy.
> 09:42:27| WARNING: up to 65 pending requests queued
> 09:42:27| Consider increasing the number of ntlmauthenticator processes
> to at least 105 in your config file.
> 09:43:31| WARNING: All ntlmauthenticator processes are busy.
> 09:43:31| WARNING: up to 66 pending requests queued
> 09:43:31| Consider increasing the number of ntlmauthenticator processes
> to at least 106 in your config file.
> 09:44:58| WARNING: All ntlmauthenticator processes are busy.
> 09:44:58| WARNING: up to 68 pending requests queued
> 09:44:58| Consider increasing the number of ntlmauthenticator processes
> to at least 108 in your config file.
> 09:45:34| WARNING: All ntlmauthenticator processes are busy.
> 09:45:34| WARNING: up to 70 pending requests queued
> 09:45:34| Consider increasing the number of ntlmauthenticator processes
> to at least 110 in your config file.
> 09:46:13| WARNING: All ntlmauthenticator processes are busy.
> 09:46:13| WARNING: up to 72 pending requests queued
> 09:46:13| Consider increasing the number of ntlmauthenticator processes
> to at least 112 in your config file.
> 09:46:51| WARNING: All ntlmauthenticator processes are busy.
> 09:46:51| WARNING: up to 74 pending requests queued
> 09:46:51| Consider increasing the number of ntlmauthenticator processes
> to at least 114 in your config file.
> 09:47:28| WARNING: All ntlmauthenticator processes are busy.
> 09:47:28| WARNING: up to 76 pending requests queued
> 09:47:28| Consider increasing the number of ntlmauthenticator processes
> to at least 116 in your config file.
> 09:48:14| WARNING: All ntlmauthenticator processes are busy.
> 09:48:14| WARNING: up to 78 pending requests queued
> 09:48:14| Consider increasing the number of ntlmauthenticator processes
> to at least 118 in your config file.
> 09:48:49| WARNING: All ntlmauthenticator processes are busy.
> 09:48:49| WARNING: up to 81 pending requests queued
> 09:48:49| Consider increasing the number of ntlmauthenticator processes
> to at least 121 in your config file.
> 09:49:23| WARNING: All ntlmauthenticator processes are busy.
> 09:49:23| WARNING: up to 88 pending requests queued
> 09:49:23| Consider increasing the number of ntlmauthenticator processes
> to at least 128 in your config file.
> 09:49:54| WARNING: All ntlmauthenticator processes are busy.
> 09:49:54| WARNING: up to 93 pending requests queued
> 09:49:54| Consider increasing the number of ntlmauthenticator processes
> to at least 133 in your config file.
> 09:50:25| WARNING: All ntlmauthenticator processes are busy.
> 09:50:25| WARNING: up to 95 pending requests queued
> 09:50:25| Consider increasing the number of ntlmauthenticator processes
> to at least 135 in your config file.
> 09:50:56| WARNING: All ntlmauthenticator processes are busy.
> 09:50:56| WARNING: up to 96 pending requests queued
> 09:50:56| Consider increasing the number of ntlmauthenticator processes
> to at least 136 in your config file.
> 09:51:26| WARNING: All ntlmauthenticator processes are busy.
> 09:51:26| WARNING: up to 97 pending requests queued
> 09:51:26| Consider increasing the number of ntlmauthenticator processes
> to at least 137 in your config file.
> 09:51:57| WARNING: All ntlmauthenticator processes are busy.
> 09:51:57| WARNING: up to 101 pending requests queued
> 09:51:57| Consider increasing the number of ntlmauthenticator processes
> to at least 141 in your config file.
> 09:52:27| WARNING: All ntlmauthenticator processes are busy.
> 09:52:27| WARNING: up to 102 pending requests queued
> 09:52:27| Consider increasing the number of ntlmauthenticator processes
> to at least 142 in your config file.
> 09:53:07| WARNING: All ntlmauthenticator processes are busy.
> 09:53:07| WARNING: up to 104 pending requests queued
> 09:53:07| Consider increasing the number of ntlmauthenticator processes
> to at least 144 in your config file.
> 09:53:37| WARNING: All ntlmauthenticator processes are busy.
> 09:53:37| WARNING: up to 110 pending requests queued
> 09:53:37| Consider increasing the number of ntlmauthenticator processes
> to at least 150 in your config file.
> 09:55:15| WARNING: All ntlmauthenticator processes are busy.
> 09:55:15| WARNING: up to 116 pending requests queued
> 09:55:15| Consider increasing the number of ntlmauthenticator processes
> to at least 156 in your config file.
> 09:55:56| WARNING: All ntlmauthenticator processes are busy.
> 09:55:56| WARNING: up to 117 pending requests queued
> 09:55:56| Consider increasing the number of ntlmauthenticator processes
> to at least 157 in your config file.
> 09:56:31| WARNING: All ntlmauthenticator processes are busy.
> 09:56:31| WARNING: up to 118 pending requests queued
> 09:56:31| Consider increasing the number of ntlmauthenticator processes
> to at least 158 in your config file.
> 09:57:24| WARNING: All ntlmauthenticator processes are busy.
> 09:57:24| WARNING: up to 119 pending requests queued
> 09:57:24| Consider increasing the number of ntlmauthenticator processes
> to at least 159 in your config file.
> 09:57:58| WARNING: All ntlmauthenticator processes are busy.
> 09:57:58| WARNING: up to 121 pending requests queued
> 09:57:58| Consider increasing the number of ntlmauthenticator processes
> to at least 161 in your config file.
> 09:59:32| WARNING: All ntlmauthenticator processes are busy.
> 09:59:32| WARNING: up to 123 pending requests queued
> 09:59:32| Consider increasing the number of ntlmauthenticator processes
> to at least 163 in your config file.
> 10:00:17| WARNING: All ntlmauthenticator processes are busy.
> 10:00:17| WARNING: up to 124 pending requests queued
> 10:00:17| Consider increasing the number of ntlmauthenticator processes
> to at least 164 in your config file.
> 10:00:56| WARNING: All ntlmauthenticator processes are busy.
> 10:00:56| WARNING: up to 126 pending requests queued
> 10:00:56| Consider increasing the number of ntlmauthenticator processes
> to at least 166 in your config file.
> 10:01:30| WARNING: All ntlmauthenticator processes are busy.
> 10:01:30| WARNING: up to 128 pending requests queued
> 10:01:30| Consider increasing the number of ntlmauthenticator processes
> to at least 168 in your config file.
> 10:02:00| WARNING: All ntlmauthenticator processes are busy.
> 10:02:00| WARNING: up to 129 pending requests queued
> 10:02:00| Consider increasing the number of ntlmauthenticator processes
> to at least 169 in your config file.
> 10:03:40| WARNING: All ntlmauthenticator processes are busy.
> 10:03:40| WARNING: up to 133 pending requests queued
> 10:03:40| Consider increasing the number of ntlmauthenticator processes
> to at least 173 in your config file.
> 10:06:06| WARNING: All ntlmauthenticator processes are busy.
> 10:06:06| WARNING: up to 134 pending requests queued
> 10:06:06| Consider increasing the number of ntlmauthenticator processes
> to at least 174 in your config file.
> 10:07:01| WARNING: All ntlmauthenticator processes are busy.
> 10:07:01| WARNING: up to 136 pending requests queued
> 10:07:01| Consider increasing the number of ntlmauthenticator processes
> to at least 176 in your config file.
> 10:07:32| WARNING: All ntlmauthenticator processes are busy.
> 10:07:32| WARNING: up to 138 pending requests queued
> 10:07:32| Consider increasing the number of ntlmauthenticator processes
> to at least 178 in your config file.
> 10:08:02| WARNING: All ntlmauthenticator processes are busy.
> 10:08:02| WARNING: up to 139 pending requests queued
> 10:08:02| Consider increasing the number of ntlmauthenticator processes
> to at least 179 in your config file.
> 10:08:33| WARNING: All ntlmauthenticator processes are busy.
> 10:08:33| WARNING: up to 140 pending requests queued
> 10:08:33| Consider increasing the number of ntlmauthenticator processes
> to at least 180 in your config file.
> 10:09:04| WARNING: All ntlmauthenticator processes are busy.
> 10:09:04| WARNING: up to 141 pending requests queued
> 10:09:04| Consider increasing the number of ntlmauthenticator processes
> to at least 181 in your config file.
> 10:09:34| WARNING: All ntlmauthenticator processes are busy.
> 10:09:34| WARNING: up to 143 pending requests queued
> 10:09:34| Consider increasing the number of ntlmauthenticator processes
> to at least 183 in your config file.
> 10:10:05| WARNING: All ntlmauthenticator processes are busy.
> 10:10:05| WARNING: up to 144 pending requests queued
> 10:10:05| Consider increasing the number of ntlmauthenticator processes
> to at least 184 in your config file.
> 10:11:30| WARNING: All ntlmauthenticator processes are busy.
> 10:11:30| WARNING: up to 145 pending requests queued
> 10:11:30| Consider increasing the number of ntlmauthenticator processes
> to at least 185 in your config file.
> 10:12:26| WARNING: All ntlmauthenticator processes are busy.
> 10:12:26| WARNING: up to 146 pending requests queued
> 10:12:26| Consider increasing the number of ntlmauthenticator processes
> to at least 186 in your config file.
> 10:14:01| WARNING: All ntlmauthenticator processes are busy.
> 10:14:01| WARNING: up to 147 pending requests queued
> 10:14:01| Consider increasing the number of ntlmauthenticator processes
> to at least 187 in your config file.
> 10:14:32| WARNING: All ntlmauthenticator processes are busy.
> 10:14:32| WARNING: up to 150 pending requests queued
> 10:14:32| Consider increasing the number of ntlmauthenticator processes
> to at least 190 in your config file.
> 10:17:57| WARNING: All ntlmauthenticator processes are busy.
> 10:17:57| WARNING: up to 152 pending requests queued
> 10:17:57| Consider increasing the number of ntlmauthenticator processes
> to at least 192 in your config file.
> 10:18:28| WARNING: All ntlmauthenticator processes are busy.
> 10:18:28| WARNING: up to 154 pending requests queued
> 10:18:28| Consider increasing the number of ntlmauthenticator processes
> to at least 194 in your config file.
> 10:18:58| WARNING: All ntlmauthenticator processes are busy.
> 10:18:58| WARNING: up to 158 pending requests queued
> 10:18:58| Consider increasing the number of ntlmauthenticator processes
> to at least 198 in your config file.
> 10:19:29| WARNING: All ntlmauthenticator processes are busy.
> 10:19:29| WARNING: up to 166 pending requests queued
> 10:19:29| Consider increasing the number of ntlmauthenticator processes
> to at least 206 in your config file.
> 10:20:00| WARNING: All ntlmauthenticator processes are busy.
> 10:20:00| WARNING: up to 169 pending requests queued
> 10:20:00| Consider increasing the number of ntlmauthenticator processes
> to at least 209 in your config file.
> 10:20:30| WARNING: All ntlmauthenticator processes are busy.
> 10:20:30| WARNING: up to 175 pending requests queued
> 10:20:30| Consider increasing the number of ntlmauthenticator processes
> to at least 215 in your config file.
> 10:21:01| WARNING: All ntlmauthenticator processes are busy.
> 10:21:01| WARNING: up to 178 pending requests queued
> 10:21:01| Consider increasing the number of ntlmauthenticator processes
> to at least 218 in your config file.
> 10:21:31| WARNING: All ntlmauthenticator processes are busy.
> 10:21:31| WARNING: up to 185 pending requests queued
> 10:21:31| Consider increasing the number of ntlmauthenticator processes
> to at least 225 in your config file.
> 10:22:02| WARNING: All ntlmauthenticator processes are busy.
> 10:22:02| WARNING: up to 189 pending requests queued
> 10:22:02| Consider increasing the number of ntlmauthenticator processes
> to at least 229 in your config file.
> 10:22:32| WARNING: All ntlmauthenticator processes are busy.
> 10:22:32| WARNING: up to 190 pending requests queued
> 10:22:32| Consider increasing the number of ntlmauthenticator processes
> to at least 230 in your config file.
> 10:23:13| WARNING: All ntlmauthenticator processes are busy.
> 10:23:13| WARNING: up to 193 pending requests queued
> 10:23:13| Consider increasing the number of ntlmauthenticator processes
> to at least 233 in your config file.
> 10:24:05| WARNING: All ntlmauthenticator processes are busy.
> 10:24:05| WARNING: up to 195 pending requests queued
> 10:24:05| Consider increasing the number of ntlmauthenticator processes
> to at least 235 in your config file.
> 10:24:37| WARNING: All ntlmauthenticator processes are busy.
> 10:24:37| WARNING: up to 199 pending requests queued
> 10:24:37| Consider increasing the number of ntlmauthenticator processes
> to at least 239 in your config file.
> 10:24:50| storeDirWriteCleanLogs: Starting...
> 10:24:50| WARNING: Closing open FD 6
> 10:24:50| Finished. Wrote 0 entries.
> 10:24:50| Took 0.0 seconds ( 0.0 entries/sec).
> FATAL: Too many queued ntlmauthenticator requests (201 on 40)
> Squid Cache (Version 2.5.STABLE6): Terminated abnormally.
>
> I don't understand why there are so many pending
> requests queued (up to 199?!?!): there are only
> 10 clients connected to squid.
>
> Is there any way to find the crazy system doing
> this crap from squid's logs? Increasing cache.log
> level perhaps?
>
>
Could you possibly have had issues with your domain controllers where
the helper was hanging trying to connect to it and requests to browse
the web just piled up instead of being denied or allowed?
Billy
Received on Wed Sep 15 2004 - 00:13:32 MDT
This archive was generated by hypermail pre-2.1.9 : Fri Oct 01 2004 - 12:00:02 MDT