/etc/logrotate.d/redis-server should not use copytruncate

Bug #1236329 reported by Marius Gedminas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
redis (Ubuntu)
New
Undecided
Unassigned

Bug Description

/etc/logrotate.d/redis-server in redis 2.6.13-1 has the 'copytruncate' stanza, which means log rotation is slow and requires additional disk space. I'm now having fun performing overdue maintenance on an old server that has a 1.4 gig redis log file and less than 1 gig of free disk space.

Upstream says that redis automatically reopens the log file after every line, so it should be safe to just rotate the log file:
https://github.com/antirez/redis/issues/337#issuecomment-4002868

Now I'm not 100% sure what the appropriate redis-server logrotate config might be. I went with

    /var/log/redis/*.log {
            weekly
            missingok
            rotate 52
            compress
            delaycompress
            notifempty
            create 0660 redis redis
    }

Revision history for this message
Marius Gedminas (mgedmin) wrote :

This should be forwarded upstream to Debian, but my Debian bug reporting skills are too rusty. Can I use reportbug in Ubuntu and ask it to report Debian bugs? Must I craft the bug email by hand, and if so, how can I figure out what the syntax is?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.