BUG: Named timeout with lots of domains

[zylon]

Description:
Once I get more than a few hundred domains on any of my servers, I get a timeout on some locations. I can still reproduce it with the latest v.1.32.2

Running the commands manually from the command-line interface does not give errors.

How to reproduce:
1. Get a lot of domains on your server, causing named start/reload to take more than a few seconds.
2. Restart/reload named via server monitor.
3. Get error:

An error has occurred

Details

/sbin/service named reload 2>&1

 

[chatwizrd]

You need to look in /var/log/messages after doing a /sbin/service named reload there are probably errors.

 

[nobaloney]

We've got many thousands of domains on some of our nameservers, and we can restart without issue.

I don't see how a timeout can cause a BIND reload to error out.

Are you saying that running

/sbin/service named reload</code]
works without error?

Jeff

 

[empowering]

And this is a bug with DirectAdmin how?

 

[floyd]

I have over 41,000 zones in one name server.

Have changed the timeout setting for DirectAdmin to accommodate longer reload times?

And just because DirectAdmin timed out doesn't mean that named did not reload successfully.

 

[marsdl]

me too have this error .
after start name service , da Gived to me error :
An error has occurred

Details

/sbin/service named start 2>&1

Please Help.

 

[floyd]

Did you check the log to see if named actually restarted?