This bug seems to start at size setting over 2000M.
When size is set to 2000M logrotate works as intended, rotates the log.
However if size is set to 2100M, 2G or higher logrotate will fail rotating logs. Eg. Logs get rotated at wrong size.
File size during tests are approx 2.3GB and should therefore not need rotation.
Debug log from size is set to 4G
rotating pattern: /monitoring/logs/dir/filename.log 0 bytes (7 rotations) empty log files are not rotated, old logs are removed considering log /monitoring/logs/dir/filename.log log needs rotating
When size is set to 4000M.
rotating pattern: /monitoring/logs/dir/filename.log -100663296 bytes (7 rotations) empty log files are not rotated, old logs are removed considering log /monitoring/logs/dir/filename.log log needs rotating
This bug seems to start at size setting over 2000M.
When size is set to 2000M logrotate works as intended, rotates the log.
However if size is set to 2100M, 2G or higher logrotate will fail rotating logs.
Eg. Logs get rotated at wrong size.
File size during tests are approx 2.3GB and should therefore not need rotation.
Debug log from size is set to 4G
rotating pattern: /monitoring/ logs/dir/ filename. log logs/dir/ filename. log
0 bytes (7 rotations)
empty log files are not rotated, old logs are removed
considering log /monitoring/
log needs rotating
When size is set to 4000M.
rotating pattern: /monitoring/ logs/dir/ filename. log logs/dir/ filename. log
-100663296 bytes (7 rotations)
empty log files are not rotated, old logs are removed
considering log /monitoring/
log needs rotating