Cisco Cisco Unified MeetingPlace for IBM Lotus Notes Guide D’Installation Rapide
Monitoring and Maintaining Cisco Unified MeetingPlace Web Conferencing
How to Configure the Lumberjack Logging Utility
13
Lumberjack Logging Utility
Upon startup of the master service, a new thread for Lumberjack begins. Lumberjack reads the
configuration values from the registry and INI file to determine behavior. If a performance monitor
definition INI file does not exist, Lumberjack automatically creates a file with a predefined counter list
and logging interval by using the Lumberjack default values.
configuration values from the registry and INI file to determine behavior. If a performance monitor
definition INI file does not exist, Lumberjack automatically creates a file with a predefined counter list
and logging interval by using the Lumberjack default values.
Every 24 hours, Lumberjack creates a new Gateway SIM event log for a 24-hour window. If the eventlog
terminates before midnight, Lumberjack restarts it. If the event log runs past midnight of the day that the
first call was made, Lumberjack terminates that process. During routing log gathering, Lumberjack also
acquires the following information:
terminates before midnight, Lumberjack restarts it. If the event log runs past midnight of the day that the
first call was made, Lumberjack terminates that process. During routing log gathering, Lumberjack also
acquires the following information:
•
Performance monitor (24-hour window)
•
NT Application and System eventlog
•
Registry snapshots
•
IIS Log
When the master service is running and Lumberjack is enabled, it detects stopped (crashed) services. and
collects the following information in a temp folder in the windows temp directory:
collects the following information in a temp folder in the windows temp directory:
•
GWSIM eventlog (24 hour window)
•
NT Application and System eventlog
•
Registry snapshots
•
IIS log
•
DrWtsn.log and User.dmp
•
.exe, .map, and .pdb of downed services
•
binaries for authfilt.dll (if downed IIS)
After the information is collected, Lumberjack bundles the files by using pkzipc.exe. This executable
file is distributed with MPWEB and located in the DataSvc folder.
file is distributed with MPWEB and located in the DataSvc folder.
The naming convention for the file is lumberjack_timestamp.zip for routine logs and
lumberjackCrash_timestamp.zip for crash logs, where timestamp is the time the log gathering started for
routine logs and the time of the detected crash for crash logs.
lumberjackCrash_timestamp.zip for crash logs, where timestamp is the time the log gathering started for
routine logs and the time of the detected crash for crash logs.
If the master service is simply stopped, the temp directory that is created for routine logs is not deleted
so that the logs for one day are bundled together if there is a restart of the master service. This
functionality enables the logs that are captured to be reviewed without having to open a zip file and
allows for a quicker shutdown and restart of master service because the service does not have to wait to
zip files and remove the directory.
so that the logs for one day are bundled together if there is a restart of the master service. This
functionality enables the logs that are captured to be reviewed without having to open a zip file and
allows for a quicker shutdown and restart of master service because the service does not have to wait to
zip files and remove the directory.
Configuring Lumberjack on a Cisco MCS Server
Before You Begin
Read the
.
Procedure
Step 1
Select Start > Run.
The Run window displays.