You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using log4net for .NET Framework version 2.0.8
RollingFileAppender is used with CountDirection=1
On startup log4net enumerates existing rollback files and sets curSizeRollBackups
Sometimes log4net does not discover ALL existing rollback files and then new rollback is created, deletes an existing file and creates new rollback. This behavior causes gaps in logs.
In attached log4net internal debug file there are issues with B7EBL.log.455, B7EBL.log.459, B7EBL.log.460 files
Files B7EBL.log.455 and B7EBL.log.459 were not discovered and curSizeRollBackups was not set correctly
log4net: File name [b7ebl.log.450] moves current count to [450]
log4net: curSizeRollBackups starts at [450]
...
log4net: Deleted file [E:\zurnalai\B7Logs\B7EBL.log.455]
log4net: Moving [E:\zurnalai\B7Logs\B7EBL.log] -> [E:\zurnalai\B7Logs\B7EBL.log.455]
...
log4net: File name [b7ebl.log.458] moves current count to [458]
log4net: curSizeRollBackups starts at [458]
...
log4net: Deleted file [E:\zurnalai\B7Logs\B7EBL.log.459]
log4net: Moving [E:\zurnalai\B7Logs\B7EBL.log] -> [E:\zurnalai\B7Logs\B7EBL.log.459]
...
log4net: Deleted file [E:\zurnalai\B7Logs\B7EBL.log.460]
log4net: Moving [E:\zurnalai\B7Logs\B7EBL.log] -> [E:\zurnalai\B7Logs\B7EBL.log.460]
No.
Setting didn't help.
Still while enumerating existing files on startup log4net doesn't "see" existing files and then deletes them during rollback.
How log4net decide about file existence?
Potentially files may be analyzed by agent, which collect logs from files to centralized location for analysis or by antivirus software
I'm using log4net for .NET Framework version 2.0.8
RollingFileAppender is used with CountDirection=1
On startup log4net enumerates existing rollback files and sets curSizeRollBackups
Sometimes log4net does not discover ALL existing rollback files and then new rollback is created, deletes an existing file and creates new rollback. This behavior causes gaps in logs.
In attached log4net internal debug file there are issues with B7EBL.log.455, B7EBL.log.459, B7EBL.log.460 files
Files B7EBL.log.455 and B7EBL.log.459 were not discovered and curSizeRollBackups was not set correctly
log4net.log
The text was updated successfully, but these errors were encountered: