cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Debug log Automatic rollover starting FNP-11.17.2 explained (101)

Debug log Automatic rollover starting FNP-11.17.2 explained (101)

Starting FNP-11.17.2 release, the debug log statement in the options file now comes with the possibility of automatic rollover of debug log files if a pre-defined condition is met (size of debug log file).

The "AUTO_ROLLOVER" option with DEBUGLOG keyword enables the auto rollover of debug log file, which automatically performs the rollover functionality of debug log file when the debug log file size reaches the specified value.

Syntax: DEBUGLOG [+]debug_log_path [OBF_ADDMARK] [AUTO_ROLLOVER size]
  • Here the last entry about [AUTO_ROLLOVER] is the enhancement related to the rollover of debug log.
  • The AUTO_ROLLOVER option enables the auto rollover of debug log file, which automatically performs the rollover functionality of debug log file when the debug log file size crosses the specified value. The default value would be 512MB.
  • The automatic rollover will always be performed at midnight.

Here is the bare minimum step to perform the setup in motion:

1.) Create an option file as below to enable AUTO_ROLLOVER

DEBUGLOG +debug.log AUTO_ROLLOVER 5KB

Note : Here we can specify KB/MB/GB for file size to rollover

2.) Start the License server closer to midnight, for testing purpose (or change the system date in Test Environment ONLY).

3.) In the debug log, a set of logs will confirm that AUTO_ROLLOVER settings have been picked up by the license server, on startup.

23:58:54 (panda) Debug log started (+debug.log).
23:58:54 (panda) OBF_ADDMARK is disabled
23:58:54 (panda) DEBUGLOG AUTO_ROLLOVER is enabled with rollover size of 5120 bytes
23:58:54 (lmgrd) panda using TCP-port 59848

4.) When approaching midnight, ensure that the existing debug log has crossed the 5KB size threshold, if not then perform a series of checkout-checkin cycles / Manual reread.

5.) Post the midnight reread, auto rollover should happen and debug.log contents should have moved out to the newly generated file [<vendor daemon name><hostname><date> T<time>.log].

6.)  debog.log should have successful Rollover details.

0:14:49 (panda) Successful roll-over of debug log file debog.log. The debug log back-up is available in panda_BLR-LT-101128_02-17-2021_T00056.log

7.)  panda_BLR-LT-101128_02-17-2021_T00056.log should have all the data of debog.log before rollover.

The similar code flow to automatic rollover of debug log will be performed based on its current size on every midnight server reread.

 

Was this article helpful? Yes No
No ratings
Version history
Revision #:
1 of 1
Last update:
‎Feb 15, 2021 04:14 PM
Updated by:
 
Contributors