Hi Clarke,

Please find the attached logrot.conf file.

LMS version is LMS3.1

What is the output of NMSROOT/bin/perl NMSROOT/bin/logrot.pl -v?

Hi Clarke,

Please find the logrot.pl output.

C:\PROGRA~1\CSCOpx>cd bin

C:\PROGRA~1\CSCOpx\bin>perl C:\PROGRA~1\CSCOpx\bin\logrot.pl -v

Thu Jun 18 08:16:21 2009: INFO: Read variable backup_dir --> D:\BackupSYSlog\

Thu Jun 18 08:16:21 2009: INFO: Read variable delay --> 60

Thu Jun 18 08:16:21 2009: INFO: Logfile = D:\BackupSYSlog\syslog.log.0\syslog.lo

g, Backup File = D:\BackupSYSlog\\syslog.log

C:\PROGRA~1\CSCOpx\bin>C:\PROGRA~1\CSCOpx\bin

Hi clarke ,

Sorry , the previous post u can ignore the output.

Please find the below updated output:-

C:\PROGRA~1\CSCOpx>cd bin

C:\PROGRA~1\CSCOpx\bin>perl C:\PROGRA~1\CSCOpx\bin\logrot.pl -v

Thu Jun 18 12:49:34 2009: INFO: Read variable backup_dir --> D:\BackupSYSlog\

Thu Jun 18 12:49:34 2009: INFO: Read variable delay --> 60

Thu Jun 18 12:49:34 2009: INFO: Logfile = D:\BackupSYSlog\syslog.log.0\syslog.lo

g, Backup File = D:\BackupSYSlog\\syslog.log

Thu Jun 18 12:49:34 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\syslog.log, Bac

kup File = D:\BackupSYSlog\\syslog.log

Thu Jun 18 12:49:34 2009: INFO: Archiving C:\PROGRA~1\CSCOpx\log\syslog.log (fil

e size = 862074975, conf size = 102400000)

Thu Jun 18 12:49:34 2009: INFO: Rolling logfile archive.

Thu Jun 18 12:49:34 2009: INFO: Archiving C:\PROGRA~1\CSCOpx\log\syslog.log to D

:\BackupSYSlog\\syslog.log.0.

1 file(s) copied.

Thu Jun 18 12:52:26 2009: INFO: Rotating C:\PROGRA~1\CSCOpx\log\syslog.log.

This looks good. The C:\PROGRA~1\CSCOpx\log\syslog.log should have been truncated to 0 bytes. You should now only see messages in this filed dated after Jun 18 12:49:34 2009.

Hi,

I have exactly the same problem, however when I try run the logrot.pl it just comes back to command line without printing any output and the log file size stays the same.

Any ideas why?

I am running LMS 2.6.

Thanks!

David

Start a new thread for your problem.

Hi clarke,

We are observing the issue log rotation is increasing or not. I will update u the status of this thread.

Hi clarke,

We are observing the issue log rotation is increasing or not. I will update u the status of this thread.

Regards

Subash

Today the file has again increased to 129MB, our configured size is 100MB.

The rmeeng file syslog db is related to this syslog rotation. Kindly advice.

C:\Program Files\CSCOpx\databases\rmeng

SyslogFirst.db Size 8,929,292 KB Date 6/16/2009

SyslogSecond.db Size 23,684,808 KB Date 6/20/2009

SyslogThird.db Size 3,139,272 KB Date 6/14/2009

Sun Jun 21 10:57:44 2009] Backing up database rmengdb:SQL Anywhere Command File Hiding Utility Version 10.0.1.3694

SQL Anywhere Backup Utility Version 10.0.1.3694

Database backup failed

Backup is unable to open database file 'SyslogFirst.db'

[Sun Jun 21 10:57:45 2009] Backup rmeng to D:/\0\rmeng\database\rmeng.db failed. Retry backup database rmeng

SQL Anywhere Command File Hiding Utility Version 10.0.1.3694

SQL Anywhere Backup Utility Version 10.0.1.3694

Database backup failed

Backup is unable to open database file 'SyslogFirst.db'

[Sun Jun 21 10:58:45 2009] Backup rmeng to D:/\0\rmeng\database\rmeng.db failed second time.

[Sun Jun 21 10:58:45 2009] ERROR(1101): Database rmengdb backup failed and . Check the log file for information.

[Sun Jun 21 10:58:45 2009] Backup failed: 2009/06/21 10:58:45

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Logrot is scheduled. For example, if you schedule logrot to run every day at midnight, it is possible for syslog.log to grow to a size greater than the configured rotation size within the 24 hour period where logrot is not running. However, when logrot runs again, it will rotate the log (reducing the size back to 0 bytes momentarily).

No, logrot has nothing to do with the syslog data spaces. It does appear that at least one of your syslog data spaces is corrupt, though. You should restore LMS from a known good backup to recover from this.

Thanks Clarke,

Any workaround is to reducing the size of the syslog.db file.

I can use the syslog.db file from the orig folder and the existing file rename to .backup .Kindly advice me .

You can contact TAC to get the DBSpaceReclaimer.class utility. However, if your syslog data spaces are corrupt, that utility will not work. You will need to restore LMS from a known good backup first to get a consistent RME database.