Jukka Pakkanen wrote: > Danny Mayer <[EMAIL PROTECTED]> kirjoitti : > >> Jukka Pakkanen wrote: >>> I get the same message in all our Windows server with P2, reported that a >>> week ago but haven't heard anything about it yet. Also the P2 crashes >>> several times a day even in a low-load server, hopefully the "very >> soon to >>> be released" fixed windows version is coming soon. >>> >>> >>> ----- Original Message ----- >>> From: "Andrey G. Sergeev (AKA Andris)" <[EMAIL PROTECTED]> >>> To: <[email protected]> >>> Sent: Saturday, August 09, 2008 12:16 PM >>> Subject: 9.5.0-P2 under Win XP: warnings about the 'files' limit in Event >>> Log >>> >>> >>> Hello fellow list users, >>> >>> >>> I'm using BIND under the FreeBSD and Windows to build a reliable DNS >>> infrastructure in my home and lab network. Today I've upgraded one of >>> the Windows XP installations of BIND from 9.5.0-P1 to -P2. Everything >>> works like a charm except that there is a one suspicious warning entry >>> with ID 2 in the Event Log saying that >>> ------------------------------[Cut]------------------------------ >>> the 'files' limit (204 is less than FD_SETSIZE (16384), increase >>> 'files' in named.conf or recompile with a smaller FD_SETSIZE. >>> ------------------------------[Cut]------------------------------ >>> >>> There is no "files" directive in my named.conf under the >> "options" >>> section. It seems to me that the nature of the warning described above >>> seems to be strange because the default setting for the "files" >> is >>> "unlimited". >>> >>> I've tried to subsequently set the "files" option to >> "16384" and >>> "unlimited" but it doesn't help. >>> >>> Could anyone confirm this and suggest the possible trick to avoid the >>> problem? >>> >>> Thanks. >>> >>> >> What is the error that you see? There are several possible errors that >> you might be seeing. >> >> Danny > > When the 9.5.0-P2 crashes (freezes) there's no errors or anything in the > event viewer. Only message is the above mentioned FD_SETSIZE when restarting > the service. > > The named service keeps growing in memory size, and then randomly stops > responding to anything. At that point the service stops growing as well. But > the service itself is still active (task manager lists it). We have set our > network monitor make a dns status query every minute, and if there's no > response to restart the service. > > Usually the named crashes few times a day. One of our recursive servers > crashed 4 hours ago and after restart named was about 28M of size. Now after > hour hours it's already 126 megs, 2195 handles and 9 threads. And this is not > very busy server. > > Another observation, one of our not-so-busy caching-only servers was running > 9.5.1b1, it run days without crashing, but was eating memory. After 5 days of > running named was using over 2 gigs of RAM and the server was running out of > memory. Now installed 9.5.0-P2 to this server 4 hours ago, and it has crashed > 8 times by now... named just stops responding and we need to restart the > service.
When you look at the number process how many handles and threads do you have? You need to add those columns to task manager via the view->select columns... menu. They are not there by default. Danny
