05-10-2006 07:31 AM
After I use logrot.pl to rotate and backup log file, the size of the log file is reduced, and the backup zip file is in the backup folder. All these look good.
But, after a while, when I check the size of that log file, it goes back to the size before I use logrot. I open the log file and find it is all blank (I think the content has been erased and backup by logrot). How does this happen and any suggestion?
Thanks
05-10-2006 07:35 AM
What version of RME are you running? Windows or Solaris?
05-10-2006 07:47 AM
Windows, RME 4.0.4. Any suggestion?
05-10-2006 07:58 AM
This may be a brand new issue. What log file(s) is this happening with?
05-10-2006 08:06 AM
It happens to all log files I try to rotate. BTW, I did not use -s option to shut down CRMdmgtd, does it cause the problem?
Thanks
05-10-2006 10:50 AM
I would like to try duplicating this. Please let me know the names of the files.
05-10-2006 01:12 PM
For example, psu.log and stdout.log.
05-10-2006 07:03 PM
The symptoms you have described are very similar to CSCsb44847: Logrot cannot rotate ani.log
Granted in your case it is happening for a number of files, however I believe the reason is the same.
Notice the Symptom from the Release-note:
"After running logrot on ani.log, the file will go to zero bytes in size. However, the next time the file is written to, its size will jump back to the original size, and there will be spaces or NUL bytes in the beginning of the file."
The work-around as you probably figured:
"Perform an offline logrot rotation with ``logrot -o''. This will shutdown dmgtd prior to logfile rotation."
05-11-2006 05:31 AM
Thanks a lot.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide