Environment
Novell DNS
Novell Open Enterprise Server (Linux based)
Novell SUSE Linux Enterprise Server 10
Novell openSUSE
Novell Open Enterprise Server (Linux based)
Novell SUSE Linux Enterprise Server 10
Novell openSUSE
Situation
To enable debug mode for named, bind, dns on Linux and OES Linux. The following examples show one way to set the services into debug mode. This document is not intended to include every method.
Resolution
In the following examples, debug level 10 is being used. 10 is the highest or most verbose debug level. Change it to something lower if desired.
Linux:
Edit the /etc/sysconfig/named file. Find NAMED_ARGS="" and change it to NAMED_ARGS="-d 10" Restart your named service.
To confirm the service is running in debug mode, look at the /var/log/messages file for something similar to the following:
starting BIND 9.3.4 -d 10 -t /var/lib/named -u named (emphasis added)
OES:
Option 1:
Start novell-named manually with the following command (or something similar):
/opt/novell/named/bin/novell-named -d 10
To confirm the service is running in debug mode, look at the /var/opt/novell/log/named/named.run file for something similar to the following:
general: main: notice: starting BIND 9.3.2 -d 10 (emphasis added)
Option 2:
Using rcnovell-named to manage the novell-named daemon takes care of a lot of things for you like file creation, location, and verification, as well as checking to see if novell-named is already running, etc.
typing rcnovell-named at the console as root will give you the syntax.
The most commonly used options are stop, start, and status.
rcnovell-named status will give you information about whether novell-named is running, how many zones are loaded, the current debug level, etc.
The debug logging level can be set in the /etc/init.d/novell-named shell script.
This is done by adding the -d option which sets the level of information to be logged to a value like, 10. If -d is specified, all the debug messages of type information /notice/warning/error/critical are logged for all categories. Setting the log level to higher number captures all the logging details over the preceding levels.
All of the messages are logged in the /var/opt/novell/log/named/named.run file. In a cluster setup the messages are logged in the same file but in the directory structure on the mount point specified with -V option.
The line that needs to be edited in the /etc/init.d/novell-named script looks like:
startproc -p ${NAMED_PID} ${NAMED_BIN} ${NAMED_ARGS} -u named -d10
By default there is no -d option on this line. Add a -d followed by the desired debug level (in this case 10) and save the file. Then do an rcnovell-named restart to start using the new debug level.
Doing an rcnovell-named status will allow you to check that the debug level has changed.
Linux:
Edit the /etc/sysconfig/named file. Find NAMED_ARGS="" and change it to NAMED_ARGS="-d 10" Restart your named service.
To confirm the service is running in debug mode, look at the /var/log/messages file for something similar to the following:
starting BIND 9.3.4 -d 10 -t /var/lib/named -u named (emphasis added)
OES:
Option 1:
Start novell-named manually with the following command (or something similar):
/opt/novell/named/bin/novell-named -d 10
To confirm the service is running in debug mode, look at the /var/opt/novell/log/named/named.run file for something similar to the following:
general: main: notice: starting BIND 9.3.2 -d 10 (emphasis added)
Option 2:
Using rcnovell-named to manage the novell-named daemon takes care of a lot of things for you like file creation, location, and verification, as well as checking to see if novell-named is already running, etc.
typing rcnovell-named at the console as root will give you the syntax.
The most commonly used options are stop, start, and status.
rcnovell-named status will give you information about whether novell-named is running, how many zones are loaded, the current debug level, etc.
The debug logging level can be set in the /etc/init.d/novell-named shell script.
This is done by adding the -d option which sets the level of information to be logged to a value like, 10. If -d is specified, all the debug messages of type information /notice/warning/error/critical are logged for all categories. Setting the log level to higher number captures all the logging details over the preceding levels.
All of the messages are logged in the /var/opt/novell/log/named/named.run file. In a cluster setup the messages are logged in the same file but in the directory structure on the mount point specified with -V option.
The line that needs to be edited in the /etc/init.d/novell-named script looks like:
startproc -p ${NAMED_PID} ${NAMED_BIN} ${NAMED_ARGS} -u named -d10
By default there is no -d option on this line. Add a -d followed by the desired debug level (in this case 10) and save the file. Then do an rcnovell-named restart to start using the new debug level.
Doing an rcnovell-named status will allow you to check that the debug level has changed.
Additional Information
keywords to improve search: bind dns named novell-named debug linux OES