Nsd 3.2.7-1 statistics signalling

NSD
1

Hi

I have two identical servers running stock debian lenny with kernel
2.6.32-bpo.3-amd64 and nsd 3.2.7-1.

They are both hosting just one zone but the zones are different.
One is big (+10M records) and the other bigger (+35M records).

Sending the USR1 signal to dump statistics works fine with the smaller
server but nothing happens when sending it to the bigger server.

I tried running the smaller zone on the "bad" server but it still does
not respond to my SIGUSR1.

Both are configured to generate statistics every 300s but that also
fails for the bigger server, it only generate XSTATS when zone is
updated and after nsec3-prepare.

Either I'm failing to run it in debug mode or nsd is very silent, coz it
gives me nothing.

Any help is much appreciated.

/Tias

2

Hi,

I have got two pointers for you:

NSD will only output stats if there is anything to report, so if all
stats are zero, no stats will be logged.

To increase logging, set the verbosity to a high number in nsd.conf.
Or build NSD with --enable-checking to get debug statements (note that
this will slow down the server).

Best regards,
  Matthijs

3

Hi

Hi,

I have got two pointers for you:

NSD will only output stats if there is anything to report, so if
all stats are zero, no stats will be logged.

Ouch, that's one way to do it...
I'll add it to my list of oddities in nsd.

It seems like stats are reset by an update of the zone, is that
expected also? What else resets the statistics, SIGUSR1?

To increase logging, set the verbosity to a high number in
nsd.conf.

Is there anything higher than 2?

Or build NSD with --enable-checking to get debug statements (note
that this will slow down the server).

Best regards, Matthijs

/Tias

4

Hi,

Hi

Hi,

I have got two pointers for you:

NSD will only output stats if there is anything to report, so if
all stats are zero, no stats will be logged.

Ouch, that's one way to do it... I'll add it to my list of oddities
in nsd.

It seems like stats are reset by an update of the zone, is that
expected also? What else resets the statistics, SIGUSR1?

I am seeing that behavior too (at zone updates), but I didn't expect
it. I'll look into it. Signals does not reset the statistics for me.

To increase logging, set the verbosity to a high number in
nsd.conf.

Is there anything higher than 2?

Computer says no: grep -r VERBOSITY *.c

Best regards,
  Matthijs

5

Mathias,

Hi,

Hi

Hi,

I have got two pointers for you:

NSD will only output stats if there is anything to report, so
if all stats are zero, no stats will be logged.

Ouch, that's one way to do it... I'll add it to my list of
oddities in nsd.

It seems like stats are reset by an update of the zone, is that
expected also? What else resets the statistics, SIGUSR1?

I am seeing that behavior too (at zone updates), but I didn't
expect it. I'll look into it. Signals does not reset the statistics
for me.

The stats are per child server. A reload triggers new children, so a
reload resets the stats.

Best regards,
  Matthijs