LinuxQuestions.org - Help with Logging to a file

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - Help with Logging to a file (https://www.linuxquestions.org/questions/linux-general-1/help-with-logging-to-a-file-23903/)

Help with Logging to a file

Hello,

I have moved up to Red Hat 7.2 after i had been running 6.1 for
quite a while. Was running 8.2.3 but have now got 9.2.1

I had saved all my config files but when starting it is not liking the logging options in my named.conf file any longer. It essentially starts but is showing the following in my messages file :-

Jun 21 13:01:27 Echelon named[2214]: logging channel 'my_syslog' file '/var/log/named.log': permission denied
Jun 21 13:01:27 Echelon named[2214]: /etc/named.conf:34: unknown logging category 'panic' ignored
Jun 21 13:01:27 Echelon named[2214]: /etc/named.conf:35: unknown logging category 'packet' ignored
Jun 21 13:01:27 Echelon named[2214]: /etc/named.conf:36: unknown logging category 'eventlib' ignored
Jun 21 13:01:27 Echelon named[2214]: /etc/named.conf:40: unknown logging category 'load' ignored
Jun 21 13:01:27 Echelon named: named startup succeeded

Can anyone see anything that i should now be adding/changing or deleting ?? below

};
logging {
channel my_syslog{
file "/var/log/named.log" versions 3 size 5m;
severity debug;
print-category yes;
print-severity yes;
print-time yes;
};
category default{ my_syslog; };
category panic{ my_syslog; };
category packet{ my_syslog; };
category eventlib{ my_syslog; };
category xfer-in{ my_syslog; };
category xfer-out{ my_syslog; };
category security{ my_syslog; };
category load{ my_syslog; };
};

It had been working fine in the earlier version of bind

Regards

Andrew

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.371 / Virus Database: 206 - Release Date: 14/06/2002

The categories panic, packet, eventlib and load have been dropped in Bind9. The categories recognized by Bind9 are as follows:

Quote:

default - The default category defines the logging options for those categories where no specific configuration has been defined.

general - The catch-all. Many things still aren't classified into categories, and they all end up here.

database - Messages relating to the databases used internally by the name server to store zone and cache data.

security - Approval and denial of requests.

config - Configuration file parsing and processing.

resolver - DNS resolution, such as the recursive lookups performed on behalf of clients by a caching name server.

xfer-in - Zone transfers the server is receiving.

xfer-out - Zone transfers the server is sending.

notify - The NOTIFY protocol.

client - Processing of client requests.

unmatched - Messages that named was unable to determine the class of or for which there was no matching view. A one line summary is also logged to the client category. This category is best sent to a file or stderr, by default it is sent to the null channel.

network - Network operations.

update - Dynamic updates.

queries - Queries. Using the category queries will enable query logging.

dispatch - Dispatching of incoming packets to the server modules where they are to be processed.

dnssec - DNSSEC and TSIG protocol processing.

lame-servers - Lame servers. These are misconfigurations in remote servers, discovered by BIND 9 when trying to query those servers during resolution.

As far as the error on /var/log/named.log, you know the routine, check file permissions, etc.

Hope this shed some light on your problems. -mk

Now that i am running the latest version of bind for RedHat 7.2 can i not restart named with a NDC restart/reload as i used to. I dont find it anywhere as a executable..

Also now that i have made some process with my logging of Bind i am getting the following. Any idea what this all means. I dont know what would be making it time out

Jun 22 03:24:18.556 notify: debug 1: zone eziekiel.com/IN: notify to 198.142.106.21#53 failed: timed out
Jun 22 03:24:24.306 notify: debug 1: zone eziekiel.com/IN: notify to 212.100.224.80#53 failed: timed out
Jun 22 03:24:33.576 notify: debug 1: zone eziekiel.com/IN: notify to 198.142.106.21#53 failed: timed out
Jun 22 03:24:48.596 notify: debug 1: zone eziekiel.com/IN: notify to 198.142.106.21#53 failed: timed out
Jun 22 03:25:03.616 notify: debug 1: zone eziekiel.com/IN: notify to 198.142.106.21#53 failed: timed out
Jun 22 03:25:03.617 notify: debug 1: zone eziekiel.com/IN: notify to 198.142.106.21#53: retries exceeded

The program name ndc has been changed to rndc, I think. To be sure do:

find / -name \*dnc -print

As far as your errors are concerned, it looks like it's failing on a zone transfer either to or from both 198.142.106.21 and 212.100.224.80. -mk