Re: Logfile Recommended size over error - LMS 3.1

bhavyangs · ‎11-27-2009

Log file	Directory	File Size (KBytes)	Recommended Size Limit (KBytes)	File System Utilization%
jrm.log	C:\PROGRA~1\CSCOpx\log	107084	1024	Less than 1%
stdout.log.*	C:\PROGRA~1\CSCOpx\mdc\tomcat\logs	57591	102400	Less than 1%
dbbackup.log	C:\PROGRA~1\CSCOpx\log	11772	1024	Less than 1%
psu.log.*	C:\PROGRA~1\CSCOpx\log	4832	1024	Less than 1%
restorebackup.log.*	C:\PROGRA~1\CSCOpx\log	3075	51200	Less than 1%

I have already configured recommended file size - file rotations in my LMS. still i keep getting this errors. Can you help me getting out of these RED alarms !!

Joe Clarke · ‎11-27-2009

The recommended sizes listed here have nothing to do with log file rotation. The "recommended" sizes are generally much too small anyway. If you have configured log rotation to your liking, you can set the recommended sizes to be the same as what you have configured for log rotation by modifying NMSROOT/conf/logstat.conf.

bhavyangs · ‎11-28-2009

i have configured log rotations to recommended size exectly. Still i get these errors.

Any way out ?

Or

What is the adverse effects if these log sizes are increased than recommended ?

Joe Clarke · ‎11-28-2009

Make sure logrot.pl is actually running then. Logrot must be scheduled, and will not automatically run just because a file exceeds its configured size. If logrot is running, and the files are not being rotated, post the output of:

NMSROOT/bin/perl NMSROOT/bin/logrot.pl -v

Note: log files like jrm.log cannot be properly rotated while Daemon Manager is running. Therefore, you will need to perform offline rotation to truncate them (i.e. logrot.pl -s).

Increasing the recommended size has no negative impact provided you have the necessary disk space. In fact, when troubleshooting problems, TAC usually likes log files to contain more data than what would be contained by the recommended sizes.

bhavyangs · ‎12-01-2009

C:\Program Files\CSCOpx\bin>perl "c:\Program Files\CSCOpx\bin\logrot.pl" -v
Tue Dec 1 19:53:50 2009: INFO: Read variable backup_dir --> D:\Log\
Tue Dec 1 19:53:50 2009: INFO: Read variable delay --> 60
Tue Dec 1 19:53:50 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\dbbackup.log, B
ackup File = D:\Log\\dbbackup.log
Tue Dec 1 19:53:50 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
stat.exe to obtain logfile size.
Tue Dec 1 19:53:50 2009: INFO: Rolling logfile archive.
Tue Dec 1 19:53:50 2009: INFO: Archiving C:\PROGRA~1\CSCOpx\log\dbbackup.log to
D:\Log\\dbbackup.log.0.
1 file(s) copied.
Tue Dec 1 19:53:51 2009: INFO: Rotating C:\PROGRA~1\CSCOpx\log\dbbackup.log.
Tue Dec 1 19:53:51 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\jrm.log, Backup
File = D:\Log\\jrm.log
Tue Dec 1 19:53:51 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
stat.exe to obtain logfile size.
Tue Dec 1 19:53:51 2009: INFO: Rolling logfile archive.
Tue Dec 1 19:53:51 2009: INFO: Archiving C:\PROGRA~1\CSCOpx\log\jrm.log to D:\L
og\\jrm.log.0.
1 file(s) copied.
Tue Dec 1 19:54:01 2009: INFO: Compressing D:\Log\\jrm.log.0 using gzip -f
Tue Dec 1 19:54:08 2009: INFO: Rotating C:\PROGRA~1\CSCOpx\log\jrm.log.
Tue Dec 1 19:54:08 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\EDS.log, Backup
File = D:\Log\\EDS.log
Tue Dec 1 19:54:08 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
stat.exe to obtain logfile size.
Tue Dec 1 19:54:08 2009: INFO: Not archiving C:\PROGRA~1\CSCOpx\log\EDS.log bec
ause it is not big enough.
file size = 2745636, conf size = 19118080
Tue Dec 1 19:54:08 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\CSPortal.log, B
ackup File = D:\Log\\CSPortal.log
Tue Dec 1 19:54:08 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
stat.exe to obtain logfile size.
Tue Dec 1 19:54:08 2009: INFO: Not archiving C:\PROGRA~1\CSCOpx\log\CSPortal.lo
g because it is not big enough.
file size = 132588, conf size = 1048576
Tue Dec 1 19:54:08 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\EDS-GCF.log, Ba
ckup File = D:\Log\\EDS-GCF.log
Tue Dec 1 19:54:08 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
stat.exe to obtain logfile size.
Tue Dec 1 19:54:08 2009: INFO: Not archiving C:\PROGRA~1\CSCOpx\log\EDS-GCF.log
because it is not big enough.
file size = 26184, conf size = 1048576
Tue Dec 1 19:54:08 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\psu.log, Backup
File = D:\Log\\psu.log
Tue Dec 1 19:54:08 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
stat.exe to obtain logfile size.
Tue Dec 1 19:54:08 2009: INFO: Not archiving C:\PROGRA~1\CSCOpx\log\psu.log bec
ause it is not big enough.
file size = 894079, conf size = 7122944
Tue Dec 1 19:54:08 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\mdc\tomcat\logs\std
out.log, Backup File = D:\Log\\stdout.log
Tue Dec 1 19:54:08 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
stat.exe to obtain logfile size.
Tue Dec 1 19:54:08 2009: INFO: Not archiving C:\PROGRA~1\CSCOpx\mdc\tomcat\logs
\stdout.log because it is not big enough.
file size = 56244907, conf size = 111889408
Tue Dec 1 19:54:08 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\CSDiscovery.log
, Backup File = D:\Log\\CSDiscovery.log
Tue Dec 1 19:54:08 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
stat.exe to obtain logfile size.
Tue Dec 1 19:54:08 2009: INFO: Not archiving C:\PROGRA~1\CSCOpx\log\CSDiscovery
.log because it is not big enough.
file size = 1084297, conf size = 1084416
Tue Dec 1 19:54:08 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\CSDeviceSelecto
r.log, Backup File = D:\Log\\CSDeviceSelector.log
Tue Dec 1 19:54:08 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
stat.exe to obtain logfile size.
Tue Dec 1 19:54:08 2009: INFO: Not archiving C:\PROGRA~1\CSCOpx\log\CSDeviceSel
ector.log because it is not big enough.
file size = 99013, conf size = 1326080

C:\Program Files\CSCOpx\bin>

Joe Clarke · ‎12-01-2009

What I see here is that most files are not large enough to rotate. Two files were rotated successfully: dbbackup.log and jrm.log. The problem with rotating jrm.log is that it will immediately return to its previous size. This log can only be rotated when Daemon Manager is down. Therefore, to rotate it properly, you will need to run logrot.pl -o (offline mode). Other than that, everything appears to be working properly.

bhavyangs · ‎12-07-2009

i feel i am misunderstanding something. or my logrot backup schedule is wrong. I have kept Log rota

tions like :

I have scheduled backup @ 00:00 Hours on every sundays.

is it a right practice ?

Or shall i change schedule to daily ?

because; even if i configure rotation, very next time logfile size exceeds. Something is happening wrong.

bhavyangs · ‎12-07-2009

i feel i am misunderstanding something. or my logrot backup schedule is wrong. I have kept Log rota

tions like :

I have scheduled backup @ 00:00 Hours on every sundays.

is it a right practice ?

Or shall i change schedule to daily ?

because; even if i configure rotations, logfiles exceeds very next moment.

Joe Clarke · ‎12-08-2009

I would certainly schedule logrot to run daily. You will also need to check the "Restart Daemon Manager" box to allow for log files like jrm.log to be properly rotated.