linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bradley Hook <bhook@kssb.net>
To: Tony Gogoi <tgogoi@cse.Buffalo.EDU>
Cc: linux-admin@vger.kernel.org
Subject: Re: DNS "named" question
Date: Tue, 24 Aug 2004 12:33:55 -0500	[thread overview]
Message-ID: <412B7C03.1050801@kssb.net> (raw)
In-Reply-To: <Pine.SOL.4.56.0408241252200.28863@hadar.cse.Buffalo.EDU>

Tony Gogoi wrote:
> Hello,
> 
> This question is more like hitting in the dark, I guess.
> 
> We have a primary and secondary DNS server. Twice or thrice so far since
> "named" automatically failed. Eg. on those times, I simply typed
> "/etc/rc.d/init/named restart" It showed "STOP - FAILED", "START - OK",
> after which things were normal.
> 
> I was wondering if anyone could give me pointers what could cause "named"
> to be down automatically simultaneously on both primary and secondary DNS
> servers.
> Individually each of the servers function properly. So, there should be
> some event (which got unlogged) which trigerred both servers to shut down
> "named"?
> 
> There was nothing abnormal in the log files. Also, "named" was down on
> both primary and secondary DNS servers on each occasion.
> 
> Thanks
> Tony
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Try running something like this:

# named -d 255 -u named -g > ~/named.log 2>&1 &

(note that you need a user called 'named' for that to work)

The next time named crashes, take a look at the last few lines of 
~/named.log and see if it gives you any clue as to where the problem is. 
You can always turn up the debug level (the 255) to get more information 
about what is going on.

~Bradley

  parent reply	other threads:[~2004-08-24 17:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-22 12:32 Linux based router for Gigabit traffic Anantha Kiran
2004-08-22 12:49 ` Neil Horman
2004-08-23  5:56   ` David S. Miller
2004-08-23  7:11     ` Mikael Abrahamsson
2004-08-23 13:10       ` Adam Lang
2004-08-23  7:58     ` urgrue
2004-08-23 11:17     ` Neil Horman
2004-08-23 11:36       ` urgrue
2004-08-25  7:48         ` Stephen Samuel
2004-08-23 15:31   ` Stephen J. Smoogen
2004-08-24 17:08     ` DNS "named" question Tony Gogoi
2004-08-24 17:21       ` DNS 'named' question Scott Taylor
2004-08-24 17:33       ` Bradley Hook [this message]
2004-08-22 15:07 ` Linux based router for Gigabit traffic Matti Aarnio
2004-08-27 18:01 ` neolozer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=412B7C03.1050801@kssb.net \
    --to=bhook@kssb.net \
    --cc=linux-admin@vger.kernel.org \
    --cc=tgogoi@cse.Buffalo.EDU \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).