Bind problem

[chenn]

Hi,
currently my Bind (Buggy Internet Name Daemon) keeps running out of resources. I upgraded due to security madness to 8.2.3, and now I'm faced with that (excerpt from logfile):
named[13745]: db_load could not open: db.cache: Resource temporarily unavailable
Problem seems to be running out of filedescriptors, so I set an ulimit in the /etc/rc2.d/S73named (ulimit -n 1024). The problem doesn't occur since then, but I'm not too sure about this solution.
So my question: Did anyone out there experience something like that and what was/is your solution? (Any comment about successfully using tinydns is also appreciated)

Thanks for your postings! regards
chenn

 

[MikeLacey]

Chenn,

The ulimit solution would please me. Is there a problem with it? Mike
michael.j.lacey@ntlworld.com
Email welcome if you're in a hurry or something -- but post in tek-tips as well please, and I will post my reply here as well.

 

[chenn]

Hi Mike,
Actually setting the ulimit didn't change that much, named keeps running out of resources. The last thing I did was setting a filedescriptor limit in /etc/system, which can't be a good solution at all, thus being global...
I never experienced problems like that before, Bind kept running without any problem or outages at all... (I'm only semi-responsible for the DNS stuff but I hate service outages in general) I can not remember any named showing that behaviour before + truss -p <PID> or lsof didn't give any further hints.

Thanks anyway! regards
chenn