Error messages and other information about POA functioning are written to log files and can be displayed in the POA console. Log files can provide a wealth of information for resolving problems with POA functioning or message flow. This section covers the following subjects to help you get the most from POA log files:
The default location of the POA log files varies by platform:
|
Linux: |
/var/log/novell/groupwise/post_office_name.poa |
|
Windows: |
post_office\wpcsout\ofs |
You can change the location where the POA creates its log files, as described in Configuring POA Log Settings and Switches.
Most of the POA log settings you configure in the Administration Console, you will be able to see in POA console and even make changes to them. To toggle the options for Disk Logging, you will need to access the POA console.
When installing or troubleshooting the POA, a logging level of Verbose can be useful. However, when the POA is running smoothly, you can set the logging level down to Normal to conserve disk space occupied by log files.
In the GroupWise Administration Console, browse to and click the POA.
Click the Log Settings tab.
Set the desired settings for logging.
Log File Path: Browse to and select the folder where you want this POA to store its log files.
Log Level: Select the amount of data displayed on the POA console and written to the POA log file.
Normal: Displays only the essential information suitable for a smoothly running POA.
Verbose: Displays the essential information, plus additional information that can be helpful for troubleshooting.
Diagnostic: Turns on Extensive Logging Options and SOAP Logging Options on the POA console Log Settings page.
Maximum Log File Age: Specifies how many days to keep POA log files on disk. The default is 30 days.
Maximum Log Disk Space: Sets the maximum amount of disk space for all POA log files. When the specified disk space is consumed, the POA deletes existing log files, starting with the oldest. The default is 100 MB. The maximum allowable setting is 1000 MB (1 GB).
Corresponding Startup Switches: You can also use the ‑‑log, ‑‑loglevel, ‑‑logdays, ‑‑logmax, and ‑‑logdiskoff, switches in the POA startup file to configure logging.
For information about Log Level and Log Maintenance settings, see Configuring Log Settings in the Administration Console. Details for Disk Logging options are provided below.
Disk Logging: Enables logging of POA events in the Log Directory.
To configure Disk Logging:
Open the POA console, and navigate to Configuration > Log Settings.
Select the desired option:
On: Turns on disk logging and sets the logging level for the POA to its default of Verbose.
Off: Turns off disk logging. Logging information is still displayed in the POA console.
Live: Turns on live logging.
You can also use the startup switch to enable live logging. However, you will still need to access the POA Console to turn live logging off by changing the toggle option to On or Off.
For startup switch information, see --liveLogging.
WARNING:To minimize impact to disk storage and system performance, we recommend that you only use the Live logging option for temporary troubleshooting.
Select log criteria to show from Extensive Logging Options and SOAP Logging Options lists.
Click Submit.
You can view the contents of the POA log file in the POA console and, if on Linux, via the tail command.
To view the POA login the POA Console:
In the POA console, click Log Files.
To view a log file, choose a log-type filter (poa, soa, or xml), select the log file, and then click View Events.
To search for a specific string, choose a log-type filter (poa, soa, or xml), select the log files to search, specify the string in the Events Containing field, and then click View Events.
HINT:To search all log files, select Select All.
To undo a selection of log items, click Reset.
To create a new log file, click Cycle Log.
On Linux, you can use the tail command to monitor a file named poa.currentlog, where poa is the name of the POA eDirectory object. This file is a symbolic link to the current POA log file, so you do not need to keep track of the exact POA log file name, which includes the log file creation date and an incrementing extension for multiple log files created on the same date.
By viewing the current log with the tail command, you can troubleshoot the POA startup using the Live Logging. For more information, see Disk Logging.
WARNING:To minimize impact to disk storage and system performance, we recommend that you only use the Live logging option for temporary troubleshooting.
On startup, the POA records the POA settings currently in effect. Thereafter, it logs events that take place, including errors.
Because the POA consists of multiple threads, you might find it useful to retrieve the log file into an editor and sort it on the thread ID that follows the date and time information. Sorting groups all messages together for the same POA thread.