#283 Log file ont rolling over

v3.3.5
open
nobody
7
2010-05-28
2010-05-28
Sumax
No

I have a few instances where the log file is not rolling over after reaching 5MB in size.
This happens sporadically. Not sure what the cause might be.
I have had instances when the log file has not rolled over even after reaching 80MB, but in most instances the log file rolls over after hitting 5MB.

I have attached a snapshot that shows the file 'sbldvgrdp03b016-node101.log', currently at 80MB in size, but previously having being rolled over after 5MB.
I have also attached the wrapper config file used to start this JVM.

All help greatly appreciated.
Thanks
Sumax

Discussion

  • Sumax
    Sumax
    2010-05-28

    Screenshot showing this log file having rolled over preoperly in a few instances, and not lately

     
    Attachments
  • Sumax
    Sumax
    2010-05-28

    Wrapper conf file used on this JVM

     
    Attachments
  • Sumax
    Sumax
    2010-05-28

    • priority: 5 --> 7
     
  • Sumax
    Sumax
    2010-05-28

    Update the version number we are using: 3.3.5

     
  • Sumax
    Sumax
    2010-05-28

    • milestone: --> v3.3.5
     
  • Sumax,

    I think I know what's preventing the wrapper from rolling the log file.
    I think the log file on your server got locked by another process (Word, etc).
    If this happens the wrapper can not rename the log file and keeps writing to the original file without rolling the log file.

    Hope this information helps you out.

     
  • Sumax
    Sumax
    2010-06-01

    Hi nayt,
    The server on which this log file is being written is a dedicated server for our process. It does not have any end-user apps installed (like word, excel, etc).
    Our app-jvm is the only process having access to this log file.

    Thanks
    Sumax

     
  • Sumax,

    for test purpose only, but could you please try to rename the filename of the current log (wrapper.log) while the wrapper is running and not rolling over the log file correctly?
    The wrapper closes and reopens the file for each write process, so renaming the file should be possible due to the wrapper. if you get an error this means a process (not necessarly from the server) has set a lock.

    in the last releases there were also quite some improvements for the logging implemented, could you also give it a try to a more recent version of the wrapper?

    Cheers,
    Christian

     
  • Sumax
    Sumax
    2010-06-01

    Thank Christian,
    I will give it a try, just need to wait for the file to exceed 5MB again.
    I'll let you know.

    Sumax