RE: Help to start BIND on boot

2004-06-02 Thread Nuno César Pires
FYI

The problem was solved when I installed the FreeBSD 4.10 release and setup
BIND 8.3.7; everything is working just fine.

Thanks a lot Matthew,
Nuno 


-Original Message-
From: Nuno César Pires 
Sent: terça-feira, 25 de Maio de 2004 10:20
To: 'Matthew Seaman'; Nuno César Pires
Cc: '[EMAIL PROTECTED]'
Subject: RE: Help to start BIND on boot

The problem is that this behaviour occurs also in a fresh installation
(4.9/8.3.6) in a different box (following the same installation checklist).

At this moment I'm considering to install and setup BIND 8.3.7 in the same
box that is running BIND 8.3.6 manually, i.e. not on boot. :-((

Thanks Matthew,
I will give you the feedback of this.
Nuno


-Original Message-
From: Matthew Seaman [mailto:[EMAIL PROTECTED] 
Sent: segunda-feira, 24 de Maio de 2004 14:09
To: Nuno César Pires
Cc: '[EMAIL PROTECTED]'
Subject: Re: Help to start BIND on boot

On Mon, May 24, 2004 at 12:29:55PM +0100, Nuno César Pires wrote:

 My question is: what solve the problem, the new FreeBSD 5.2.1 or the BIND
 8.3.7?

Good question.  It's unlikely to be the simple replacement of one OS
version or one BIND version for another -- we would know about it if
there was a general problem with people running BIND on FreeBSD.  

 How can I solve this strange behaviour in the FreeBSD 4.9/BIND 8.3.6
system?

Unfortunately, having made my best guess, I'm afraid I'm all out of
suggestions.  Other than this: take a close look at the way both of
those boxes are set up, and try and isolate the differences in
configuration between the two.  The answer should lie somewhere in
there -- something you did differently on one of the boxes.  Isolate
that, and you're home and dry.

Which is easy to say, but not necessarily easy to do.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK
 

CONFIDENCIALIDADE: Esta mensagem e quaisquer documentos em anexo são
confidenciais. Se não for o destinatário desta mensagem, agradecemos que
avise imediatamente o remetente e que a elimine sem a reproduzir, armazenar
ou divulgar a qualquer entidade.

CONFIDENTIALITY: This  e-mail  and  any attachments are confidential and may
be privileged. If  you are not a named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for
any purpose or store or copy the information in any medium.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: Help to start BIND on boot

2004-05-25 Thread Nuno César Pires
The problem is that this behaviour occurs also in a fresh installation
(4.9/8.3.6) in a different box (following the same installation checklist).

At this moment I'm considering to install and setup BIND 8.3.7 in the same
box that is running BIND 8.3.6 manually, i.e. not on boot. :-((

Thanks Matthew,
I will give you the feedback of this.
Nuno


-Original Message-
From: Matthew Seaman [mailto:[EMAIL PROTECTED] 
Sent: segunda-feira, 24 de Maio de 2004 14:09
To: Nuno César Pires
Cc: '[EMAIL PROTECTED]'
Subject: Re: Help to start BIND on boot

On Mon, May 24, 2004 at 12:29:55PM +0100, Nuno César Pires wrote:

 My question is: what solve the problem, the new FreeBSD 5.2.1 or the BIND
 8.3.7?

Good question.  It's unlikely to be the simple replacement of one OS
version or one BIND version for another -- we would know about it if
there was a general problem with people running BIND on FreeBSD.  

 How can I solve this strange behaviour in the FreeBSD 4.9/BIND 8.3.6
system?

Unfortunately, having made my best guess, I'm afraid I'm all out of
suggestions.  Other than this: take a close look at the way both of
those boxes are set up, and try and isolate the differences in
configuration between the two.  The answer should lie somewhere in
there -- something you did differently on one of the boxes.  Isolate
that, and you're home and dry.

Which is easy to say, but not necessarily easy to do.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK
 

CONFIDENCIALIDADE: Esta mensagem e quaisquer documentos em anexo são
confidenciais. Se não for o destinatário desta mensagem, agradecemos que
avise imediatamente o remetente e que a elimine sem a reproduzir, armazenar
ou divulgar a qualquer entidade.

CONFIDENTIALITY: This  e-mail  and  any attachments are confidential and may
be privileged. If  you are not a named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for
any purpose or store or copy the information in any medium.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: Help to start BIND on boot

2004-05-24 Thread Nuno César Pires
Hi,

I have defined de 'rand_irqs' settings in rc.conf as you suggested but
unfortunately the result was the same.

Meanwhile I setup a fresh installation, of the new FreeBSD 5.2.1 release
with the BIND 8.3.7, in other box.
I setup the BIND and the system with the same settings as the other and
defined to start BIND on boot.
The result was that the boot process was ok (it took the normal time) and
the output of ndc status was: The server is up and running ;-
instead of the boring message server is initializing itself.

My question is: what solve the problem, the new FreeBSD 5.2.1 or the BIND
8.3.7?
How can I solve this strange behaviour in the FreeBSD 4.9/BIND 8.3.6 system?

Many Thanks,
Nuno


-Original Message-
From: Matthew Seaman [mailto:[EMAIL PROTECTED] 
Sent: sexta-feira, 21 de Maio de 2004 13:15
To: Nuno César Pires
Cc: '[EMAIL PROTECTED]'
Subject: Re: Help to start BIND on boot

On Fri, May 21, 2004 at 12:07:25PM +0100, Nuno César Pires wrote:

 I'm setting up a BIND/DNS server (recursive) and I'm facing a problem when
I
 try to start the named automatically on boot (named_enable=YES in
 rc.conf):
 
 First I noticed that the boot process takes a very long time in the
 Starting Standard Daemons phase.
 
 After boot I have looked to the named messages and apparently it was
 everything ok i.e.:
 
  
 
 First message:  starting (etc/namedb/named.conf). named
 8.3.6-REL .
 
 Second message:  limit files set to fdlimit (1024)
 
 Third message:  Ready to answer queries.
 
  
 
 But the problem is the output of ndc status: (server is initializing
 itself) and then nothing happen.
 
  
 
 Starting or restarting the named manually works just fine, the ndc
status
 output is server is up and running and the queries answers are as
 expected.
 
 The result after comment the kern_securelevel=2 and
 kern_securelevel_enable=YES lines in the rc.conf and reboot was the same
 as described above.
 
  
 
 The ROOT SERVERS file was updated and there is a permanent network
 connection
 
  
 
 Releases:
 
 FreeBSD 4.9
 
 BIND 8.3.6

I usually see this effect with things like sshd(8), but it could
affect BIND as well.  I wonder if named(8) is blocking trying to read
/dev/random to obtain a quantity of random data.  If the system does
not have sufficient suitable random data available, it will wait until
it has acquired enough before replying.  Sources of randomness are
things like timing the gaps between key presses or between the arrival
of network packets -- either of which may not be very effective around
reboot time.

Check your setting for 'rand_irqs' in /etc/rc.conf -- you need to set
it to a list of IRQs that fire quite frequently and that have timings
that can be used to harvest randomness from.  To get a list of
suitable IRQs use:

% vmstat -i

So for instance on my system that returns:

interrupt   total   rate
acpi0 irq9  1  0
pcm0 irq10  39644  0
mux irq1112139824 77
mux irq15  854820  5
atkbd0 irq1 49505  0
psm0 irq12 389549  2
sio1 irq3   81928  0
clk irq0157097139   1000
rtc irq8 20105805128
Total   190758215   1214

Choose the IRQs that fire most often, but not the clk (clock) or rtc
(real time clock) IRQs -- as those fire at regular intervals.  In this
case good choices are irq1 (atkbd -- the keyboard), irq11 and irq15
(mux -- the TCP multiplexor (ie network traffic)), irq12 (psm -- the
mouse).

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK
 

CONFIDENCIALIDADE: Esta mensagem e quaisquer documentos em anexo são
confidenciais. Se não for o destinatário desta mensagem, agradecemos que
avise imediatamente o remetente e que a elimine sem a reproduzir, armazenar
ou divulgar a qualquer entidade.

CONFIDENTIALITY: This  e-mail  and  any attachments are confidential and may
be privileged. If  you are not a named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for
any purpose or store or copy the information in any medium.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Help to start BIND on boot

2004-05-24 Thread Matthew Seaman
On Mon, May 24, 2004 at 12:29:55PM +0100, Nuno César Pires wrote:

 My question is: what solve the problem, the new FreeBSD 5.2.1 or the BIND
 8.3.7?

Good question.  It's unlikely to be the simple replacement of one OS
version or one BIND version for another -- we would know about it if
there was a general problem with people running BIND on FreeBSD.  

 How can I solve this strange behaviour in the FreeBSD 4.9/BIND 8.3.6 system?

Unfortunately, having made my best guess, I'm afraid I'm all out of
suggestions.  Other than this: take a close look at the way both of
those boxes are set up, and try and isolate the differences in
configuration between the two.  The answer should lie somewhere in
there -- something you did differently on one of the boxes.  Isolate
that, and you're home and dry.

Which is easy to say, but not necessarily easy to do.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgpFD9N3WcROG.pgp
Description: PGP signature


Help to start BIND on boot

2004-05-21 Thread Nuno César Pires
Hello list,

 

I'm setting up a BIND/DNS server (recursive) and I'm facing a problem when I
try to start the named automatically on boot (named_enable=YES in
rc.conf):

First I noticed that the boot process takes a very long time in the
Starting Standard Daemons phase.

After boot I have looked to the named messages and apparently it was
everything ok i.e.:

 

First message:  starting (etc/namedb/named.conf). named
8.3.6-REL .

Second message:  limit files set to fdlimit (1024)

Third message:  Ready to answer queries.

 

But the problem is the output of ndc status: (server is initializing
itself) and then nothing happen.

 

Starting or restarting the named manually works just fine, the ndc status
output is server is up and running and the queries answers are as
expected.

The result after comment the kern_securelevel=2 and
kern_securelevel_enable=YES lines in the rc.conf and reboot was the same
as described above.

 

The ROOT SERVERS file was updated and there is a permanent network
connection

 

Releases:

FreeBSD 4.9

BIND 8.3.6

 

Can you please help me on this? I'm beginner in FreeBSD.

 

Thanks in advance,

Nuno

 

CONFIDENCIALIDADE: Esta mensagem e quaisquer documentos em anexo são
confidenciais. Se não for o destinatário desta mensagem, agradecemos que
avise imediatamente o remetente e que a elimine sem a reproduzir, armazenar
ou divulgar a qualquer entidade.

CONFIDENTIALITY: This  e-mail  and  any attachments are confidential and may
be privileged. If  you are not a named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for
any purpose or store or copy the information in any medium.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Help to start BIND on boot

2004-05-21 Thread Matthew Seaman
On Fri, May 21, 2004 at 12:07:25PM +0100, Nuno César Pires wrote:

 I'm setting up a BIND/DNS server (recursive) and I'm facing a problem when I
 try to start the named automatically on boot (named_enable=YES in
 rc.conf):
 
 First I noticed that the boot process takes a very long time in the
 Starting Standard Daemons phase.
 
 After boot I have looked to the named messages and apparently it was
 everything ok i.e.:
 
  
 
 First message:  starting (etc/namedb/named.conf). named
 8.3.6-REL .
 
 Second message:  limit files set to fdlimit (1024)
 
 Third message:  Ready to answer queries.
 
  
 
 But the problem is the output of ndc status: (server is initializing
 itself) and then nothing happen.
 
  
 
 Starting or restarting the named manually works just fine, the ndc status
 output is server is up and running and the queries answers are as
 expected.
 
 The result after comment the kern_securelevel=2 and
 kern_securelevel_enable=YES lines in the rc.conf and reboot was the same
 as described above.
 
  
 
 The ROOT SERVERS file was updated and there is a permanent network
 connection
 
  
 
 Releases:
 
 FreeBSD 4.9
 
 BIND 8.3.6

I usually see this effect with things like sshd(8), but it could
affect BIND as well.  I wonder if named(8) is blocking trying to read
/dev/random to obtain a quantity of random data.  If the system does
not have sufficient suitable random data available, it will wait until
it has acquired enough before replying.  Sources of randomness are
things like timing the gaps between key presses or between the arrival
of network packets -- either of which may not be very effective around
reboot time.

Check your setting for 'rand_irqs' in /etc/rc.conf -- you need to set
it to a list of IRQs that fire quite frequently and that have timings
that can be used to harvest randomness from.  To get a list of
suitable IRQs use:

% vmstat -i

So for instance on my system that returns:

interrupt   total   rate
acpi0 irq9  1  0
pcm0 irq10  39644  0
mux irq1112139824 77
mux irq15  854820  5
atkbd0 irq1 49505  0
psm0 irq12 389549  2
sio1 irq3   81928  0
clk irq0157097139   1000
rtc irq8 20105805128
Total   190758215   1214

Choose the IRQs that fire most often, but not the clk (clock) or rtc
(real time clock) IRQs -- as those fire at regular intervals.  In this
case good choices are irq1 (atkbd -- the keyboard), irq11 and irq15
(mux -- the TCP multiplexor (ie network traffic)), irq12 (psm -- the
mouse).

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgpCbEJrmSvah.pgp
Description: PGP signature


RE: Start BIND on boot

2004-05-19 Thread Nuno César Pires
Hi,

Sorry not to give my feedback related with your suggestions sooner, but I
was absent.
I have looked to the named messages after boot and apparently it was
everything ok i.e.:

First message:  starting (etc/namedb/named.conf). named 8.3.6-REL .
Second message: limit files set to fdlimit (1024)
Third message:  Ready to answer queries.

There is no messages related with the ROOT SERVERS, the file was updated and
there is a permanent network connection.

Running the ndc status the output is: server is initialising itself

After restarting the server manually, after boot, the status is: server is
up and running.

The result after comment the kern_securelevel=2 and
kern_securelevel_enable=YES lines in the rc.conf and reboot was the same
as described above.

Do you have any more suggestions to debug and solve this problem?

Thanks
Nuno


-Original Message-
From: Charles Swiger [mailto:[EMAIL PROTECTED] 
Sent: terça-feira, 11 de Maio de 2004 20:32
To: Nuno César Pires
Cc: '[EMAIL PROTECTED]'
Subject: Re: Start BIND on boot

On May 11, 2004, at 1:13 PM, Nuno César Pires wrote:
[ ... ]
  The result is that the boot process takes a very long time in the 
 Starting
 Standard Daemons phase. After boot the result of ndc status is: 
 (server is
 initialising itself) and then nothing happen.

 Starting de named manually works just fine.

Hmm.  There isn't enough information available to say what's going on 
for certain, but what you are doing ought to work fine.

Do you have a permanent network connection which is available when your 
system boots?  If the network isn't available, named can't talk to 
other nameservers and it will probably cause a very long delay which 
matches your description.

Check /var/log/messages after a system reboot for messages relating to 
named.  You ought to see something like this:

May 11 15:21:19 daemon.notice pi named[9319]: starting 
(/etc/named.conf).  nam
ed 8.3.7-REL Tue Dec  2 14:40:53 EST 2003   
[EMAIL PROTECTED]:/usr/obj/usr/s
rc/usr.sbin/named
May 11 15:21:19 daemon.warn pi named[9319]: limit files set to 
fdlimit (1024)
May 11 15:21:19 daemon.notice pi named[9320]: Ready to answer queries.
May 11 15:21:19 daemon.warn pi named[9320]: check_hints: A records 
for B.ROOT-
SERVERS.NET class 1 do not match hint records

If there were problems with your named.conf file or one of the zone 
files, you'd see warning messages which ought to be fixed.

-- 
-Chuck
 

CONFIDENCIALIDADE: Esta mensagem e quaisquer documentos em anexo são
confidenciais. Se não for o destinatário desta mensagem, agradecemos que
avise imediatamente o remetente e que a elimine sem a reproduzir, armazenar
ou divulgar a qualquer entidade.

CONFIDENTIALITY: This  e-mail  and  any attachments are confidential and may
be privileged. If  you are not a named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for
any purpose or store or copy the information in any medium.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Start BIND on boot

2004-05-11 Thread Nuno César Pires
Hello list,

 

I'm setting up a BIND/DNS server (recursive) and I'm facing a problem when I
try to start the named automatically on boot (named_enable=YES in
rc.conf):

The result is that the boot process takes a very long time in the Starting
Standard Daemons fase. After boot the result of ndc status is: (server is
initialising itself) and then nothing happen.

Starting de named manually works just fine.

 

Releases:

FreeBSD 4.9

BIND 8.3.6

 

Can you please help me on this? I'm beginner in FreeBSD.

Sorry for the English.

 

Thanks in advance,

Nuno

 

CONFIDENCIALIDADE: Esta mensagem e quaisquer documentos em anexo são
confidenciais. Se não for o destinatário desta mensagem, agradecemos que
avise imediatamente o remetente e que a elimine sem a reproduzir, armazenar
ou divulgar a qualquer entidade.

CONFIDENTIALITY: This  e-mail  and  any attachments are confidential and may
be privileged. If  you are not a named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for
any purpose or store or copy the information in any medium.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Start BIND on boot

2004-05-11 Thread Charles Swiger
On May 11, 2004, at 1:13 PM, Nuno César Pires wrote:
[ ... ]
 The result is that the boot process takes a very long time in the 
Starting
Standard Daemons [ph]ase. After boot the result of ndc status is: 
(server is
initialising itself) and then nothing happen.

Starting de named manually works just fine.
Hmm.  There isn't enough information available to say what's going on 
for certain, but what you are doing ought to work fine.

Do you have a permanent network connection which is available when your 
system boots?  If the network isn't available, named can't talk to 
other nameservers and it will probably cause a very long delay which 
matches your description.

Check /var/log/messages after a system reboot for messages relating to 
named.  You ought to see something like this:

May 11 15:21:19 daemon.notice pi named[9319]: starting 
(/etc/named.conf).  nam
ed 8.3.7-REL Tue Dec  2 14:40:53 EST 2003   
[EMAIL PROTECTED]:/usr/obj/usr/s
rc/usr.sbin/named
May 11 15:21:19 daemon.warn pi named[9319]: limit files set to 
fdlimit (1024)
May 11 15:21:19 daemon.notice pi named[9320]: Ready to answer queries.
May 11 15:21:19 daemon.warn pi named[9320]: check_hints: A records 
for B.ROOT-
SERVERS.NET class 1 do not match hint records

If there were problems with your named.conf file or one of the zone 
files, you'd see warning messages which ought to be fixed.

--
-Chuck
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Start BIND on boot

2004-05-10 Thread Nuno César Pires
Hello list,

 

I'm setting up a BIND/DNS server (recursive) and I'm facing a problem when I
try to start the named automatically on boot (named_enable=YES in
rc.conf):

The result is that the boot process takes a very long time in the Starting
Standard Daemons fase. After boot the result of ndc status is: (server is
initialising itself) and then nothing happen.

Starting de named manually works just fine.

 

FreeBSD 4.9

BIND 8.3.6

 

Can you please help me on this? I'm beginner in FreeBSD.

Sorry for the English.

 

Thanks in advance,

Nuno

 

CONFIDENCIALIDADE: Esta mensagem e quaisquer documentos em anexo são
confidenciais. Se não for o destinatário desta mensagem, agradecemos que
avise imediatamente o remetente e que a elimine sem a reproduzir, armazenar
ou divulgar a qualquer entidade.

CONFIDENTIALITY: This  e-mail  and  any attachments are confidential and may
be privileged. If  you are not a named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for
any purpose or store or copy the information in any medium.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]