I have Centro 5.4 it named starts at bootup but fails to restart when I give command service named restart and it there is no any error in syslog messages.
With reload command I get the following message in syslog :- Nov 25 14:03:30 unitedinfotechs named[2201]: using default UDP/IPv4 port range: [1024, 65535] Nov 25 14:03:30 unitedinfotechs named[2201]: using default UDP/IPv6 port range: [1024, 65535] Nov 25 14:16:03 unitedinfotechs named[2201]: loading configuration from '/etc/named.conf' Nov 25 14:16:03 unitedinfotechs named[2201]: using default UDP/IPv4 port range: [1024, 65535] Nov 25 14:16:03 unitedinfotechs named[2201]: using default UDP/IPv6 port range: [1024, 65535]
I shall highly appreciate any hint.
Tariq Ismail Dalvi wrote:
I have Centro 5.4 it named starts at bootup but fails to restart when I give command service named restart and it there is no any error in syslog messages.
With reload command I get the following message in syslog :-
You running *restart* or *reload* as they are often different things.
Your subject says restart your text above says reload.
reload uses ndc and restart uses start/stop
I prefer restart myself, ndc doesn't work well with my configuration for whatever reason.
nate
Hello Nate,
In my case reload works fine but if i use restart the it show Stopping named OK Starting named: [FAILED] and syslog message shows following entry:- Nov 26 01:23:15 localhost named[4413]: starting BIND 9.3.6-P1-RedHat-9.3.6-4.P1.el5 -u named -D -t /var/named/chroot Nov 26 01:23:15 localhost named[4413]: adjusted limit on open files from 1024 to 1048576 Nov 26 01:23:15 localhost named[4413]: found 1 CPU, using 1 worker thread Nov 26 01:23:15 localhost named[4413]: using up to 4096 sockets Nov 26 01:23:15 localhost named[4413]: loading configuration from '/etc/named.conf' Nov 26 01:23:15 localhost named[4413]: using default UDP/IPv4 port range: [1024, 65535] Nov 26 01:23:15 localhost named[4413]: using default UDP/IPv6 port range: [1024, 65535] Nov 26 01:23:15 localhost named[4413]: listening on IPv4 interface lo, 127.0.0.1#53 Nov 26 01:23:15 localhost named[4413]: listening on IPv4 interface eth0, 192.168.1.12#53 Nov 26 01:23:15 localhost named[4413]: listening on IPv4 interface eth0:0, 192.168.1.16#53 Nov 26 01:23:15 localhost named[4413]: listening on IPv4 interface eth0, 192.168.1.10#53 Nov 26 01:23:15 localhost named[4413]: command channel listening on 127.0.0.1#953 Nov 26 01:23:15 localhost named[4413]: command channel listening on 192.168.1.12#953 Nov 26 01:23:15 localhost named[4413]: zone 0.in-addr.arpa/IN/internal: loaded serial 42 Nov 26 01:23:15 localhost named[4413]: zone 0.0.127.in-addr.arpa/IN/internal: loaded serial 1 Nov 26 01:23:15 localhost named[4413]: zone 168.192.in-addr.arpa/IN/internal: loaded serial 6 Nov 26 01:23:15 localhost named[4413]: zone 255.in-addr.arpa/IN/internal: loaded serial 42 Nov 26 01:23:15 localhost named[4413]: zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN/internal: loaded serial 1997022700 Nov 26 01:23:15 localhost named[4413]: zone example4.in/IN/internal: loaded serial 6 Nov 26 01:23:15 localhost named[4413]: zone example1.in/IN/internal: loaded serial 6 Nov 26 01:23:15 localhost named[4413]: zone localdomain/IN/internal: loaded serial 42 Nov 26 01:23:15 localhost named[4413]: zone localhost/IN/internal: loaded serial 42 Nov 26 01:23:15 localhost named[4413]: zone example3.net/IN/internal: loaded serial 6 Nov 26 01:23:15 localhost named[4413]: zone example2.net/IN/internal: loaded serial 6 Nov 26 01:23:15 localhost named[4413]: zone 83.57.in-addr.arpa/IN/external: loaded serial 6 Nov 26 01:23:15 localhost named[4413]: zone example4.in/IN/external: loaded serial 1 Nov 26 01:23:15 localhost named[4413]: zone example1.in/IN/external: loaded serial 6 Nov 26 01:23:15 localhost named[4413]: zone example3.net/IN/external: loaded serial 1 Nov 26 01:23:15 localhost named[4413]: zone example2.net/IN/external: loaded serial 6
one more error i have noticed in Service configuration panel while trying to start named is :- rndc: connect failed: 127.0.0.1#953: connection refused named is stopped.
Best regards.
On Wed, Nov 25, 2009 at 1:54 PM, nate centos@linuxpowered.net wrote:
Tariq Ismail Dalvi wrote:
I have Centro 5.4 it named starts at bootup but fails to restart when I give command service named restart and it there is no any error in syslog messages.
With reload command I get the following message in syslog :-
You running *restart* or *reload* as they are often different things.
Your subject says restart your text above says reload.
reload uses ndc and restart uses start/stop
I prefer restart myself, ndc doesn't work well with my configuration for whatever reason.
nate
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I have changed it to reflect port 953 in named conf Control still the same problem
On Wed, Nov 25, 2009 at 4:36 PM, Lars Hecking lhecking@users.sourceforge.net wrote:
rndc: connect failed: 127.0.0.1#953: connection refused named is stopped.
Missing control statement for rndc port.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Lars Hecking -
nate -
Tariq Ismail Dalvi