On 24.06.2022 22:46, Felix Miata wrote:
Andrei Borzenkov composed on 2022-06-24 15:34 (UTC+0300):
On Tumbleweed logrotate is controlled by logrotate.timer which by default runs every day and has Persistent option which means, if it missed run (because system was not up) it should immediately activate service during boot. Check logrotate.timer (is it enabled, when was the last time it run etc).
Apparently the problem is at least in part the immediate activation on a new boot, a boot on which a large quantity of transactions subsequently transpire from zypper dup after a lengthy period of no booting. It compacts the old file with the current date, then on a subsequent boot following a new kernel installation and massive zypper.log growth,
You seriously say that one zypper dup results in 10M log file?
it refuses to compact the gigantic new log file because a rotated file with the current date already exists.
In default configuration logrotate.timer will trigger service once a day.