That's what's logged on /var/log/messages while doing the restart: Oct 21 18:30:28 japot named[14010]: shutting down: flushing changes Oct 21 18:30:28 japot named[14010]: stopping command channel on 127.0.0.1#953 Oct 21 18:30:28 japot named[14010]: no longer listening on 127.0.0.1#53 Oct 21 18:30:28 japot named[14010]: no longer listening on 10.0.0.90#53 Oct 21 18:30:28 japot named[14010]: no longer listening on 10.0.0.1#53 Oct 21 18:30:28 japot named[14007]: exiting Oct 21 18:30:28 japot named[14185]: starting BIND 9.2.1 -u named Oct 21 18:30:28 japot named[14185]: using 1 CPU Oct 21 18:30:28 japot named[14188]: loading configuration from '/etc/named.conf' Oct 21 18:30:28 japot named[14188]: no IPv6 interfaces found Oct 21 18:30:28 japot named[14188]: listening on IPv4 interface lo, 127.0.0.1#53 Oct 21 18:30:28 japot named[14188]: listening on IPv4 interface eth0, 10.0.0.90#53 Oct 21 18:30:28 japot named[14188]: listening on IPv4 interface vmnet8, 10.0.0.1#53 Oct 21 18:30:28 japot named[14188]: command channel listening on 127.0.0.1#953 Oct 21 18:30:28 japot named[14188]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700 Oct 21 18:30:28 japot named[14188]: zone localhost/IN: loaded serial 42 Oct 21 18:30:28 japot named[14188]: running Oct 21 18:30:28 japot named: named startup succeeded And the "service named restart" output is the usual: Stopping named: Starting named: [ OK ] Alex On Mon, 2002-10-21 at 18:03, H M Kunzmann wrote: > On Mon, 2002-10-21 at 17:37, Alessandro Polverini wrote: > > Hello, > > I noticed a strange behaviour while restarting named. > > When it works I get: > > --- > > [root@xxx root]# service named restart > > Stopping named: > > Starting named: [ OK ] > > --- > > As you can see the [OK] is missing on the stopping procedure. > > But sometimes instead it happens that: > > --- > > [root@xxx root]# service named restart > > Stopping named: > > named: already running[root@xxx root]# > > --- > > and if I do it again: > > --- > > [root@xxx root]# service named restart > > Stopping named: rndc: connect failed: connection refused > > [FAILED] > > Starting named: [ OK ] > > --- > > > > So what it seems is that the first time the command "thinks" that named > > is running, while in reality it's not, and I have to run it again. > > > > That behaviour never showed on redhat 7.2 and 7.3. > > > > Can anybody confirm that? > > > > Looks to me that named doesn't successfully shutdown by the time that > 'service' tries to start it. As soon as the shutdown is completed, the > second call the restart has an error because now ndc is no longer > running. > > Whatever the reason, this shouldn't be happening. > Have you done a "tail -f /var/log/messages" and then the "service named > restart" ? > > > > > -- > Psyche-list mailing list > Psyche-list@redhat.com > https://listman.redhat.com/mailman/listinfo/psyche-list -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
