I have an issue with the logs which get exceed the size limit such as CVDeviceselector.log,CSDiscovery.log,jrm.log,I have read the user guide CS3.1 Maintaining the log files but am not sure that the logrot file which am editing is correct as per the instruction.Am using LMS 3.0.1 and CS3.1.
What i understand from configuring logrot is what i have configured in attachment document. Please refer to attachments
Maintaining Log Files On Windows
To maintain log files on Windows:
Step 1 Make sure the new location has sufficient disk space.
Step 2 Go to the command line and make sure you have the correct permissions.
Step 3 Stop all processes by entering:
net stop crmdmgtd
Step 4 Perform log maintenance by running logrot.
See Configuring Logrot and Running Logrot for more information.
Step 5 Verify the procedure was successful by examining the contents of the log files in the following location:
Only log files that reach 90% of their size limits are backed up, and the original log file is emptied.
Step 6 Restart the system by entering:
net start crmdmgtd
Step 7 Select Server > Reports > Log File Status to view your log changes.
The Logrot utility helps you manage the log files in a better fashion.
Logrot is a log rotation program that can:
â¢ Rotate log when CiscoWorks is running.
â¢ Optionally archive and compress rotated logs.
â¢ Rotate log only when it has reached a particular size.
Logrot helps you add new files easily. Logrot should be installed on the same machine where you have
installed Common Services.
User Guide for CiscoWorks Common Services
Chapter 4 Configuring the Server
Administering Common Services
To configure Logrot:
Step 1 Enter NMSROOT\bin\perl.exe NMSROOT\bin\logrot.pl -c (on Windows)
Step 2 Run /opt/CSCOpx/bin/logrot.pl -c (on Solaris)
The Logrot configuration menu appears. You have the following options:
â¢ Edit variables.
â¢ Edit log files.
â¢ Quit and save changes.
â¢ Quit without saving change.
Step 3 Select Edit variables to set your Backup Directory.
If you do not set a backup directory, each log will be rotated in its current directory.
Step 4 Select Edit log files to add log files you wish Logrot to rotate.
You can specify log files using fully-qualified or relative paths. If a relative path is specified, and the log
file does not exist in that path, the default log file path for your operating system will be added during
rotation (for example, /var/adm/CSCOpx/log on Solaris).
Step 5 Specify the number of archive revisions. If you do not want to keep any archives, enter 0 (the default)
for this option.
Step 6 Specify the maximum file size. The log will not be rotated until this size is reached. The unit is in
kilobytes (KB). The default is 1024 KB or 1 MB.
Step 7 Specify the file compression type to be used. It can be:
â¢ gz-GNU gzip (available by default on Windows only)
â¢ bz2-bzip2 (available by default on Solaris8 and above only).
When deleting logfiles, you can choose to delete an individual file, a list of files, or all files matching a
For example, 1-3 means delete files numbered 1 through 3. a list of comma-separated file numbers, for
example, 1,21, means delete files numbered 1 and 21. A pattern string *.log means delete all files that
match the pattern *.log.
You can also specify the special pattern, *, which means delete all logfiles in the configuration.
To run Logrot enter:
â¢ On Windows:
Enter NMSROOT\bin\perl NMSROOT\bin\logrot.pl
â¢ On Solaris:
First, the log file name is jrm.log, not jrm. Second, restarting Daemon Manager does not run logrot. After you configure logrot, run:
D:\progra~1\cscopx\bin\perl D:\progra~1\cscopx\bin\logrot.pl -s
That will shutdown Daemon Manager, rotate the logs, then restart Daemon Manager.