Re: [Cooker] bind's imortal
/Glen And you have the same setup as me? (as shown in the previous mail) Stopping named: [FAILED] Starting named: [ OK ] it's reproducable :-( I dont know what went right the first time! /Glen
Re: [Cooker] bind's imortal
On Wed, Sep 24, 2003 at 12:42:50AM +0200, Oden Eriksson wrote: besides bind-chroot scripts removes rndc conf from /etc, so root cannot use rndc anymore. great idea!!! It moves the file to the chroot /etc/ dir. You have to call it like: rndc -c /var/lib/named-chroot/etc/rndc.conf stop there is no reason for that. the bind daemon does not need rndc.conf to run, so it may as well stay in /etc, where it belongs. regards, L. -- Luca Berra -- [EMAIL PROTECTED] Communication Media Services S.r.l. /\ \ / ASCII RIBBON CAMPAIGN XAGAINST HTML MAIL / \
Re: [Cooker] bind's imortal
On Tue, 2003-09-23 at 20:10, Oden Eriksson wrote: Hi. Anyone else seing this: # /etc/rc.d/init.d/named restart Stopping named: [FAILED] Starting named: [ OK ] #/etc/init.d/named restart Stopping named: [ OK ] Starting named: [ OK ] nope /Glen
Re: [Cooker] bind's imortal
tisdagen den 23 september 2003 22.44 skrev Glen Kjærulff: On Tue, 2003-09-23 at 20:10, Oden Eriksson wrote: Hi. Anyone else seing this: # /etc/rc.d/init.d/named restart Stopping named: [FAILED] Starting named: [ OK ] #/etc/init.d/named restart Stopping named: [ OK ] Starting named: [ OK ] nope /Glen And you have the same setup as me? (as shown in the previous mail)
Re: [Cooker] bind's imortal
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/3R 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...)
Re: [Cooker] bind's imortal
On Tue, Sep 23, 2003 at 11:47:31PM +0200, Oden Eriksson wrote: 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 ] i never used bind-chroot myself anyway reading /etc/rc.d/init.d/function i found this piece of code in killproc function. # Avoid killing processes not running in the same root [ -n $pid ] pid=`inmyroot $pid` this might be the culprit. why don't we use rndc stop in the initscript for named? besides bind-chroot scripts removes rndc conf from /etc, so root cannot use rndc anymore. great idea!!! why the hell does bind-chroot have to muck with my syslogd.conf, since my chrooted bind syslogs without any problem? L. -- Luca Berra -- [EMAIL PROTECTED] Communication Media Services S.r.l. /\ \ / ASCII RIBBON CAMPAIGN XAGAINST HTML MAIL / \
Re: [Cooker] bind's imortal
onsdagen den 24 september 2003 00.08 skrev Luca Berra: On Tue, Sep 23, 2003 at 11:47:31PM +0200, Oden Eriksson wrote: 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 ] i never used bind-chroot myself anyway reading /etc/rc.d/init.d/function i found this piece of code in killproc function. # Avoid killing processes not running in the same root [ -n $pid ] pid=`inmyroot $pid` this might be the culprit. Aha, maybe that's why. This is a bug that has to be fixed before 9.2. why don't we use rndc stop in the initscript for named? That works. besides bind-chroot scripts removes rndc conf from /etc, so root cannot use rndc anymore. great idea!!! It moves the file to the chroot /etc/ dir. You have to call it like: rndc -c /var/lib/named-chroot/etc/rndc.conf stop
Re: [Cooker] bind's imortal
On Tue, 2003-09-23 at 23:42, Oden Eriksson wrote: onsdagen den 24 september 2003 00.08 skrev Luca Berra: On Tue, Sep 23, 2003 at 11:47:31PM +0200, Oden Eriksson wrote: 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 ] i never used bind-chroot myself anyway reading /etc/rc.d/init.d/function i found this piece of code in killproc function. # Avoid killing processes not running in the same root [ -n $pid ] pid=`inmyroot $pid` this might be the culprit. Aha, maybe that's why. This is a bug that has to be fixed before 9.2. Hahahahaha. You'll be lucky. -- adamw
