tisdagen den 23 september 2003 20.10 skrev Oden Eriksson:
> Hi.
>
> Anyone else seing this:
>
> # /etc/rc.d/init.d/named restart
> Stopping named:                                                 [FAILED]
> Starting named:                                                 [  OK  ]
>
> # /etc/rc.d/init.d/named restart
> Stopping named:                                                 [FAILED]
> Starting named:                                                 [  OK  ]
>
>
> # ps ax | grep named
> 25237 ?        S      0:00 named -u named -c /etc/named.conf -t
> /var/lib/named-chroot
> 25238 ?        S      0:00 named -u named -c /etc/named.conf -t
> /var/lib/named-chroot
> 25239 ?        S      0:00 named -u named -c /etc/named.conf -t
> /var/lib/named-chroot
> 25240 ?        S      0:00 named -u named -c /etc/named.conf -t
> /var/lib/named-chroot
> 25241 ?        S      0:00 named -u named -c /etc/named.conf -t
> /var/lib/named-chroot
> 25266 ?        S      0:00 named -u named -c /etc/named.conf -t
> /var/lib/named-chroot
> 25267 ?        S      0:00 named -u named -c /etc/named.conf -t
> /var/lib/named-chroot
> 25268 ?        S      0:00 named -u named -c /etc/named.conf -t
> /var/lib/named-chroot
> 25269 ?        S      0:00 named -u named -c /etc/named.conf -t
> /var/lib/named-chroot
> 25270 ?        S      0:00 named -u named -c /etc/named.conf -t
> /var/lib/named-chroot
>
> ???
>
> It's a fresh cooker box. Using my latest bind package, but that's not it
> because I have seen this before, I just have forgotten about it until now.


Hmmm, it's reproducable..., I just tried it at home:


# bind-chroot.sh --chroot /var/lib/named-chroot/

Updating SYSLOGD_OPTIONS in the /etc/sysconfig/syslog file.
Updating OPTIONS in /etc/sysconfig/named
Updating ROOTDIR in /etc/sysconfig/named

Chroot configuration for BIND is complete.
You should review your /var/lib/named-chroot//etc/named.conf
and make any necessary changes.

Run "/sbin/service named restart" when you are done.

# /etc/rc.d/init.d/named restart
Stopping named:                                                 [  OK  ]
Starting named:                                                 [  OK  ]

# /etc/rc.d/init.d/named restart
Stopping named:                                                 [FAILED]
Starting named:                                                 [  OK  ]

# /etc/rc.d/init.d/named restart
Stopping named:                                                 [FAILED]
Starting named:                                                 [  OK  ]


# ps ax|grep named
13938 ?        S      0:00 named -u named -c /etc/named.conf -t 
/var/lib/named-chroot/
13939 ?        S      0:00 named -u named -c /etc/named.conf -t 
/var/lib/named-chroot/
13940 ?        S      0:00 named -u named -c /etc/named.conf -t 
/var/lib/named-chroot/
13941 ?        S      0:00 named -u named -c /etc/named.conf -t 
/var/lib/named-chroot/
13942 ?        S      0:00 named -u named -c /etc/named.conf -t 
/var/lib/named-chroot/
13967 ?        S      0:00 named -u named -c /etc/named.conf -t 
/var/lib/named-chroot/
13968 ?        S      0:00 named -u named -c /etc/named.conf -t 
/var/lib/named-chroot/
13969 ?        S      0:00 named -u named -c /etc/named.conf -t 
/var/lib/named-chroot/
13970 ?        S      0:00 named -u named -c /etc/named.conf -t 
/var/lib/named-chroot/
13971 ?        S      0:00 named -u named -c /etc/named.conf -t 
/var/lib/named-chroot/
13980 pts/3    R      0:00 grep named


Sep 23 23:36:13 *** named[13969]: /etc/named.conf:12: couldn't add command 
channel 127.0.0.1#953: address in use

???

(too tired to understand...)


Reply via email to