Using the CONLOG Utility

The CONLOG utility enables you to capture all console messages generated at the server while CONLOG is loaded and write the messages to the default SYS:\ETC\CONSOLE.LOG file or to another file of your choice.

You can use the CONSOLE.LOG file to check that all modules have been loaded without any errors during the startup of the Novell Internet Access Server. To view the CONSOLE.LOG file, load NIASCFG and follow this path:

Select Configure NIAS > Protocols and Routing > View Configuration > Console Messages

To load CONLOG, type the following command at the server prompt:

load conlog [file= log filename ] [save= backup filename ] [maximum= max file size ] [archive= yes ] [next= hh:mm ] [entire= yes ] | help

where

file=log filename is the name of the file you want to use as the log file. CONLOG writes console messages to this file instead of CONSOLE.LOG. The log filename parameter must be used with
SFT III^TM servers, whose three engines must each write to a different log file.

save=backup filename is the name of the file in which you want to save the preexisting console log. This enables the AUTOEXEC.NCF file to load CONLOG without overwriting the previous console log. Use this parameter if you want to examine the old console log for troubleshooting purposes.

maximum=max file size is the maximum size of the log file in kilobytes. If the log file exceeds max file size , it is deleted---or renamed if backup filename was specified. In either case, logging is restarted with an empty log file.

archive=yes saves logs numerically. Instead of saving the console log into a file called CONSOLE.BAK, CONLOG creates CONSOLE.000, CONSOLE.001, ..., CONSOLE.999. After creating CONSOLE.999, if all 1,000 console log files exist, CONLOG reuses the number of the oldest file.

next=hh:mm archives the console log at the 24-hour time specified. If no time is specified, the console log is saved when it reaches the length limit.

entire=yes captures the lines already on the window at the time CONLOG is loaded. Without this parameter, CONLOG starts logging with the next output to the console after it is loaded.

help displays a description of each CONLOG command parameter.

The load conlog command is typically added to the AUTOEXEC.NCF file, as shown in the following example:

You can view the console log in one of three ways:

• Loading NIASCFG and following this path:

  Select Configure NIAS > Protocols and Routing > View Configuration > Console Messages

  NIASCFG enables you view the log file any time, even while the CONLOG.NLM is loaded.

• Using the EDIT.NLM utility by typing the following command:

  load edit sys:\etc\console.log

  The EDIT.NLM utility does not let you view the log file if the CONLOG.NLM is loaded. If you want to see the log file using the EDIT.NLM utility, unload CONLOG first.

• Using any text editor from a LAN workstation to open the file (if CONLOG is not loaded). If you attempt to view the console.log file with a text editor while CONLOG is loaded, the file will appear empty.

Console messages can reveal errors that occur during system initialization. Table 2 shows how to use CONLOG.

Table 2. How to Use CONLOG