DNS server won't start/restart

[PaulR]

OK - got another one...  DNS service will not start or restart.  I've tried disabling and re-enabling the module, even tried removing and re-installing it.  No change, can not start it back up.  Here is the result of a restart, the ebox.log file and a run of dig at the local host:

paulr@houseserver:/var/log/ebox$ sudo invoke-rc.d ebox dns restart
 * Restarting eBox module: dns                                           [ OK ]
paulr@houseserver:/var/log/ebox$ cat ebox.log
2009/09/19 12:46:21 INFO> Service.pm:619 EBox::Module::Service::restartService - Restarting service for module: dns
2009/09/19 12:46:25 DEBUG> LogFiltering.pm:70 EBox::Events::Model::Watcher::LogFiltering::new - Missing argument: tableInfo
2009/09/19 12:46:25 WARN> Events.pm:526 EBox::Events::__ANON__ - model EBox::Events::Model::Watcher::LogFiltering cannot be instantiated
paulr@houseserver:/var/log/ebox$ dig @127.0.0.1

; <<>> DiG 9.4.2-P2 <<>> @127.0.0.1
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached


As before, any help is greatly appreciated.
Thanks,
Paul

[dragonslayr]

Hmm, not answering?
telnet localhost 53

Has it got a pid?
pgrep -f named

Do you see anything in /var/log/syslog
grep named /var/log/syslog

Be aware, I've never used dns (bind) on ebox. Though, I am familiar with bind9.

[PaulR]

well, don't see a pid, the logs are clean, but... if I try to restart it, it appears to go cleanly, still see nothing, and get the same results I listed up above.

Very confused...
Paul

[dragonslayr]

Ok, I went and installed it.

I do have a pid of course, I do have a log entry

This is what I get in my /var/log/syslog, just so you can see one working.
/etc/init.d/bind9 restart

Code: [Select]

Sep 20 07:04:58 eboxpdc init: ebox.bind9 main process ended, respawning
Sep 20 07:04:58 eboxpdc kernel: [37785.171563] audit(1253448298.743:29): type=1503 operation="inode_permission" requested_mask="w::" denied_mask="w::" name="/var/run/slapd/ldapi" pid=15742 profile="/usr/sbin/named" namespace="default"
Sep 20 07:04:58 eboxpdc kernel: [37785.180479] audit(1253448298.751:30): type=1503 operation="inode_permission" requested_mask="w::" denied_mask="w::" name="/var/run/slapd/ldapi" pid=15742 profile="/usr/sbin/named" namespace="default"
Sep 20 07:04:58 eboxpdc kernel: [37785.193580] audit(1253448298.762:31): type=1503 operation="capable" name="sys_resource" pid=15743 profile="/usr/sbin/named" namespace="default"
dig @localhost does not work. Though it does on my bind box.
dig @localhost eboxtest.com (which is my ebox I added in dns) works. Have you added a domain in dns?

I'm running out of ideas..
There should be a file in /var/run/bind/run called named.pid if it's running.

If you have a missing dot or something in the named.local file you should still get some logging..

When you reinstalled dns did you purge it first?
Probably apt-get remove --purge ebox-dns

Your just having all kinds of fun.. Sorry I'm not more helpful.

[PaulR]

Hey you are being helpful... at least giving me some direction to go poke around.  I really appreciate it.  I think my issues are the result of the fact that I did not do a full install, but just selected what I needed.  Not sure the config engine is handling those cases all that well.

Anyhow, I'll do some more digging around with the info you just sent, and I'll let you know what I turn up.

Again, thanks for all the help.
Paul

[PaulR]

OK - Did a remove and install again, this time making sure I used the purge option.  Went smoothly, but.... here is the tail end of the install information:

 * Starting domain name service... bind                                  [fail]

Setting up ebox-dns (1.2.2-0ubuntu1~ppa1~hardy1) ...
 * Restarting eBox module: dns                                           [ OK ]

Processing triggers for ebox ...
 * Restarting eBox module: apache                                        [ OK ]

I'll go dig up the logs next.

Thanks again,
Paul

[PaulR]

Here is the pertinent portion of the log:

Sep 20 09:41:34 houseserver init: ebox.bind9 main process (24283) terminated with status 1
Sep 20 09:41:34 houseserver init: ebox.bind9 main process ended, respawning
Sep 20 09:41:35 houseserver init: ebox.bind9 main process (24337) terminated with status 1
Sep 20 09:41:35 houseserver init: ebox.bind9 main process ended, respawning
Sep 20 09:41:35 houseserver init: ebox.bind9 main process (24389) terminated with status 1
Sep 20 09:41:35 houseserver init: ebox.bind9 main process ended, respawning
Sep 20 09:41:35 houseserver init: ebox.bind9 main process (24441) terminated with status 1
Sep 20 09:41:35 houseserver init: ebox.bind9 main process ended, respawning
Sep 20 09:41:35 houseserver init: ebox.bind9 main process (24493) terminated with status 1
Sep 20 09:41:35 houseserver init: ebox.bind9 main process ended, respawning
Sep 20 09:41:35 houseserver init: ebox.bind9 main process (24545) terminated with status 1
Sep 20 09:41:35 houseserver init: ebox.bind9 main process ended, respawning
Sep 20 09:41:35 houseserver smbd_audit: paul|192.168.100.98|open|ok|r|2009/Andys End of Year Parties/DSC_0048.JPG
Sep 20 09:41:36 houseserver init: ebox.bind9 main process (24597) terminated with status 1
Sep 20 09:41:36 houseserver init: ebox.bind9 main process ended, respawning
Sep 20 09:41:36 houseserver init: ebox.bind9 main process (24649) terminated with status 1
Sep 20 09:41:36 houseserver init: ebox.bind9 main process ended, respawning
Sep 20 09:41:36 houseserver init: ebox.bind9 main process (24701) terminated with status 1
Sep 20 09:41:36 houseserver init: ebox.bind9 main process ended, respawning
Sep 20 09:41:36 houseserver init: ebox.bind9 main process (24753) terminated with status 1
Sep 20 09:41:36 houseserver init: ebox.bind9 main process ended, respawning
Sep 20 09:41:36 houseserver init: ebox.bind9 respawning too fast, stopped

[dragonslayr]

Your getting pids. Yeh!  haha

I'd try to disable, then enable the dns module in ebox and other settings in the ebox menu now..

[PaulR]

Yup - one step ahead of you there....    Disabled, re-enabled... no change... still will not start.  I can configure it all just fine, all the options and settings are there, but the server is not running.

Scratching my head here...

Thanks again,
Paul

[dragonslayr]

Have to go do some stuff, but what happens when you try to run directly?
/usr/sbin/rndc reload

Or even
/etc/init.d/bind force-reload

[dragonslayr]

And another thought.
Wonder what would happened if you took ebox out of the picture. uninstall and purge ebox dns, then install bind9 on it's own.

[PaulR]

sudo: /usr/sbin/mdc: command not found
sudo: /etc/init.d/bind: command not found

Can't try the bind9 route directly tonight.  But I suppose I could give that a try failing anything else.  The sticker here is that it did work when first installed.  I originally did a full install, and it worked fine.  I then removed Asterix, and a few other modules.  NONE that are listed as dependancies.

Thanks again...
Paul

[dragonslayr]

/usr/sbin/rndc

and

/etc/init.d/bind9

If it's in a vm, maybe I could look at it. If not, maybe tomarrow or something I could ssh to it. We could invoke screen and you could see what I'm doing.

[PaulR]

Oh man... I guess I just need to bite the bullet and wear my glasses all the time...  here you go:

paulr@houseserver:~$ sudo /etc/init.d/bind9 force-reload
 * Reloading domain name service... bind                                        rndc: connect failed: 127.0.0.1#953: connection refused
                                                                         [fail]
paulr@houseserver:~$ sudo /usr/sbin/rndc reload
rndc: connect failed: 127.0.0.1#953: connection refused

[dragonslayr]

ok, that leans towards a simple configuration error.

Try running named directly with this command and it should point you in the right direction.

named -g -p 53

we may have to look at your named.conf named.conf.local and named.options files..