How do I stop named from logging unwanted status messages to /usr/adm/syslog? - SCO

This is a discussion on How do I stop named from logging unwanted status messages to /usr/adm/syslog? - SCO ; I have a client with SCO 5.0.7 getting a boatload of named messages that are filling up /usr/adm/syslog and mean nothing to anyone: Jun 21 10:46:58 qipp named[442]: NSTATS 1182440818 1178729083 Jun 21 10:46:58 qimpp named[442]: XSTATS 1182440818 1178729083 RR=13 ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: How do I stop named from logging unwanted status messages to /usr/adm/syslog?

  1. How do I stop named from logging unwanted status messages to /usr/adm/syslog?

    I have a client with SCO 5.0.7 getting a boatload of named messages that
    are filling up /usr/adm/syslog and mean nothing to anyone:

    Jun 21 10:46:58 qipp named[442]: NSTATS 1182440818 1178729083
    Jun 21 10:46:58 qimpp named[442]: XSTATS 1182440818 1178729083 RR=13 RNXD=0 RFwdR=6 RDupR=3 RFail=0 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=7 SAns=0 SFwdQ=0 SDupQ=9 SErr=0 RQ=0 RIQ=0
    RFwdQ=0 RDupQ=0 RTCP=0 SFwdR=6 SFail=0
    Jun 21 10:46:58 qipp named[442]: Cleaned cache of 0 RRsets
    Jun 21 11:46:58 qipp named[442]: USAGE 1182444418 1178729083 CPU=0u/0s CHILDCPU=0
    Jun 21 11:46:58 qipp named[442]: NSTATS 1182444418 1178729083
    Jun 21 11:46:58 qipp named[442]: XSTATS 1182444418 1178729083 RR=13 RNXD=0 RFwdR=6 RDupR=3 RFail=0 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=7 SAns=0 SFwdQ=0 SDupQ=9 SErr=0 RQ=0 RIQ=0
    RFwdQ=0 RDupQ=0 RTCP=0 SFwdR=6 SFail=0
    Jun 21 11:46:58 qipp named[442]: Cleaned cache of 0 RRsets
    Jun 21 12:46:58 qipp named[442]: USAGE 1182448018 1178729083 CPU=0u/0s CHILDCPU=0
    Jun 21 12:46:58 qipp named[442]: NSTATS 1182448018 1178729083
    Jun 21 12:46:58 qipp named[442]: XSTATS 1182448018 1178729083 RR=13 RNXD=0 RFwdR=6 RDupR=3 RFail=0 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=7 SAns=0 SFwdQ=0 SDupQ=9 SErr=0 RQ=0 RIQ=0
    RFwdQ=0 RDupQ=0 RTCP=0 SFwdR=6 SFail=0
    Jun 21 12:46:58 qipp named[442]: Cleaned cache of 0 RRsets
    Jun 21 13:46:58 qipp named[442]: USAGE 1182451618 1178729083 CPU=0u/0s CHILDCPU=0
    Jun 21 13:46:58 qipp named[442]: NSTATS 1182451618 1178729083
    Jun 21 13:46:58 qipp named[442]: XSTATS 1182451618 1178729083 RR=13 RNXD=0 RFwdR=6 RDupR=3 RFail=0 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=7 SAns=0 SFwdQ=0 SDupQ=9 SErr=0 RQ=0 RIQ=0
    RFwdQ=0 RDupQ=0 RTCP=0 SFwdR=6 SFail=0
    Jun 21 13:46:58 qipp named[442]: Cleaned cache of 0 RRsets
    Jun 21 14:46:58 qipp named[442]: USAGE 1182455218 1178729083 CPU=0u/0s CHILDCPU=0
    Jun 21 14:46:58 qipp named[442]: NSTATS 1182455218 1178729083
    Jun 21 14:46:58 qipp named[442]: XSTATS 1182455218 1178729083 RR=13 RNXD=0 RFwdR=6 RDupR=3 RFail=0 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=7 SAns=0 SFwdQ=0 SDupQ=9 SErr=0 RQ=0 RIQ=0
    RFwdQ=0 RDupQ=0 RTCP=0 SFwdR=6 SFail=0
    Jun 21 14:46:58 qipp named[442]: Cleaned cache of 0 RRsets
    Jun 21 19:52:16 qipp sshd[19956]: Accepted publickey for smf from 66.142.21.94 port 1340 ssh2



    Since there is no logging directive in /etc/named.con, named must be using the default
    logging values.

    Current /etc/named.conf:

    > // generated by named-bootconf.pl
    > //
    > // @(#) named.conf.ca 68.2 98/01/14
    > //
    >
    > options {
    > directory "/etc/named.d";
    > /*
    > * If there is a firewall between you and nameservers you want
    > * to talk to, you might need to uncomment the query-source
    > * directive below. Previous versions of BIND always asked
    > * questions using port 53, but BIND 8.1 uses an unprivileged
    > * port by default.
    > */
    > // query-source address * port 53;
    > };
    >
    > zone "." {
    > type hint;
    > file "root.cache";
    > };
    >
    > zone "0.0.127.in-addr.arpa" {
    > type master;
    > file "named.local";
    > };




    In the /etc/named.d/named.conf example file there is a section on logging
    running from line 290 to 464.

    > 290 logging {
    > 291 /*
    > 292 * All log output goes to one or more "channels"; you can make as
    > 293 * many of them as you want.
    > 294 */
    > 295
    > 296 channel syslog_errors { // this channel will send errors or
    > ....
    > 457 * channel may be assigned to each of them, and it must be a
    > 458 * file channel. If you don't define them yourself, they default to
    > 459 *
    > 460 * category eventlib { default_debug; };
    > 461 *
    > 462 * category packet { default_debug; };
    > 463 */
    > 464 };




    Too much info for someone with no experience configuring named!!!

    What do I have to add to /etc/named.conf (or /etc/syslog.conf) to stop the
    messages from filling syslog?

  2. Re: How do I stop named from logging unwanted status messages to /usr/adm/syslog?

    In article ,
    Steve M. Fabac, Jr. wrote:
    >I have a client with SCO 5.0.7 getting a boatload of named messages that
    >are filling up /usr/adm/syslog and mean nothing to anyone:


    >In the /etc/named.d/named.conf example file there is a section on logging
    >running from line 290 to 464.
    >
    > > 290 logging {
    > > 291 /*
    > > 292 * All log output goes to one or more "channels"; you can make as
    > > 293 * many of them as you want.
    > > 294 */
    > > 295
    > > 296 channel syslog_errors { // this channel will send errors or
    > > ....
    > > 457 * channel may be assigned to each of them, and it must be a
    > > 458 * file channel. If you don't define them yourself, they default to
    > > 459 *
    > > 460 * category eventlib { default_debug; };
    > > 461 *
    > > 462 * category packet { default_debug; };
    > > 463 */
    > > 464 };

    >
    >
    >
    >Too much info for someone with no experience configuring named!!!
    >
    >What do I have to add to /etc/named.conf (or /etc/syslog.conf) to stop the
    >messages from filling syslog?


    You can set various categories to null:

    logging {
    category lame-servers { null; };
    };

    See named.conf(SFF) for category names.

    John
    --
    John DuBois spcecdt@armory.com KC6QKZ/AE http://www.armory.com/~spcecdt/

  3. Re: How do I stop named from logging unwanted status messages to/usr/adm/syslog?

    John DuBois wrote:
    > In article ,
    > Steve M. Fabac, Jr. wrote:
    >> I have a client with SCO 5.0.7 getting a boatload of named messages that
    >> are filling up /usr/adm/syslog and mean nothing to anyone:

    >
    >> In the /etc/named.d/named.conf example file there is a section on logging
    >> running from line 290 to 464.
    >>
    >>> 290 logging {
    >>> 291 /*
    >>> 292 * All log output goes to one or more "channels"; you can make as
    >>> 293 * many of them as you want.
    >>> 294 */
    >>> 295
    >>> 296 channel syslog_errors { // this channel will send errors or
    >>> ....
    >>> 457 * channel may be assigned to each of them, and it must be a
    >>> 458 * file channel. If you don't define them yourself, they default to
    >>> 459 *
    >>> 460 * category eventlib { default_debug; };
    >>> 461 *
    >>> 462 * category packet { default_debug; };
    >>> 463 */
    >>> 464 };

    >>
    >>
    >> Too much info for someone with no experience configuring named!!!
    >>
    >> What do I have to add to /etc/named.conf (or /etc/syslog.conf) to stop the
    >> messages from filling syslog?

    >
    > You can set various categories to null:
    >
    > logging {
    > category lame-servers { null; };
    > };
    >
    > See named.conf(SFF) for category names.
    >
    > John


    John,

    Thanks for the pointer.

    However, looking at named.conf(Sff) is still confusing to me.
    It is another example of a document that the author finds complete
    but a first time reader is still lost and does not have a clue on
    how to make a simple change.

    Can you post the exact code that I can cut and paste into named.conf
    to recast the default category as lame-servers?

    Once I see that, I should have a chance to extend the code to include
    all categories.

  4. Re: How do I stop named from logging unwanted status messages to/usr/adm/syslog?

    Steve M. Fabac, Jr. wrote:
    > John DuBois wrote:
    >> In article ,
    >> Steve M. Fabac, Jr. wrote:
    >>> I have a client with SCO 5.0.7 getting a boatload of named messages that
    >>> are filling up /usr/adm/syslog and mean nothing to anyone:

    >>
    >>> In the /etc/named.d/named.conf example file there is a section on
    >>> logging
    >>> running from line 290 to 464.
    >>>
    >>>> 290 logging {
    >>>> 291 /*
    >>>> 292 * All log output goes to one or more "channels";
    >>>> you can make as
    >>>> 293 * many of them as you want.
    >>>> 294 */
    >>>> 295
    >>>> 296 channel syslog_errors { // this channel will
    >>>> send errors or
    >>>> ....
    >>>> 457 * channel may be assigned to each of them, and it
    >>>> must be a
    >>>> 458 * file channel. If you don't define them
    >>>> yourself, they default to
    >>>> 459 *
    >>>> 460 * category eventlib { default_debug; };
    >>>> 461 *
    >>>> 462 * category packet { default_debug; };
    >>>> 463 */
    >>>> 464 };
    >>>
    >>>
    >>> Too much info for someone with no experience configuring named!!!
    >>>
    >>> What do I have to add to /etc/named.conf (or /etc/syslog.conf) to
    >>> stop the
    >>> messages from filling syslog?

    >>
    >> You can set various categories to null:
    >>
    >> logging {
    >> category lame-servers { null; };
    >> };
    >>
    >> See named.conf(SFF) for category names.
    >>
    >> John

    >
    > John,
    >
    > Thanks for the pointer.
    >
    > However, looking at named.conf(Sff) is still confusing to me.
    > It is another example of a document that the author finds complete
    > but a first time reader is still lost and does not have a clue on
    > how to make a simple change.
    >
    > Can you post the exact code that I can cut and paste into named.conf
    > to recast the default category as lame-servers?
    >
    > Once I see that, I should have a chance to extend the code to include
    > all categories.


    While waiting on John, I tired the following and it solved the problem:

    logging {
    category default { null; };
    };

    > Jun 21 11:46:58 qipp named[442]: Cleaned cache of 0 RRsets
    > Jun 21 12:46:58 qipp named[442]: USAGE 1182448018 1178729083 CPU=0u/0s CHILDCPU=0
    > Jun 21 12:46:58 qipp named[442]: NSTATS 1182448018 1178729083
    > Jun 21 12:46:58 qipp named[442]: XSTATS 1182448018 1178729083 RR=13 RNXD=0 RFwdR=6 RDupR=3 RFail=0 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=7 SAns=0 SFwdQ=0 SDupQ=9 SErr=0 RQ=0 RIQ=0 RFwdQ=0 RDupQ=0 RTCP=0 SFwdR=6 SFail=0




  5. Re: How do I stop named from logging unwanted status messages to/usr/adm/syslog?

    In article ,
    Steve M. Fabac, Jr. wrote:
    >John DuBois wrote:
    >> In article ,
    >> Steve M. Fabac, Jr. wrote:
    >>> I have a client with SCO 5.0.7 getting a boatload of named messages that
    >>> are filling up /usr/adm/syslog and mean nothing to anyone:

    >>
    >>> In the /etc/named.d/named.conf example file there is a section on logging
    >>> running from line 290 to 464.
    >>>
    >>>> 290 logging {
    >>>> 291 /*
    >>>> 292 * All log output goes to one or more "channels"; you can make as
    >>>> 293 * many of them as you want.
    >>>> 294 */
    >>>> 295
    >>>> 296 channel syslog_errors { // this channel will send errors or
    >>>> ....
    >>>> 457 * channel may be assigned to each of them, and it must be a
    >>>> 458 * file channel. If you don't define them yourself, they default to
    >>>> 459 *
    >>>> 460 * category eventlib { default_debug; };
    >>>> 461 *
    >>>> 462 * category packet { default_debug; };
    >>>> 463 */
    >>>> 464 };
    >>>
    >>>
    >>> Too much info for someone with no experience configuring named!!!
    >>>
    >>> What do I have to add to /etc/named.conf (or /etc/syslog.conf) to stop the
    >>> messages from filling syslog?

    >>
    >> You can set various categories to null:
    >>
    >> logging {
    >> category lame-servers { null; };
    >> };
    >>
    >> See named.conf(SFF) for category names.
    >>
    >> John

    >
    >John,
    >
    >Thanks for the pointer.


    >However, looking at named.conf(Sff) is still confusing to me.
    >It is another example of a document that the author finds complete
    >but a first time reader is still lost and does not have a clue on
    >how to make a simple change.


    Considering that O'Reilly has a full book - several hundred pages -
    on DNS/BIND the man pages/sample-conf-files are good references
    for configuration, but not meant to be a tutorial.

    Bill
    --
    Bill Vermillion - bv @ wjv . com

+ Reply to Thread