Logrotate

[Becker884]

Hi, what do you think about a logrotate for FlashMQ?
I built the following:

/var/log/flashmq/flashmq.log {
    daily
    rotate 7
    compress
    delaycompress
    dateext
    missingok
    notifempty
    create 0640 root root
    postrotate
        systemctl reload flashmq >/dev/null 2>&1 || true
    endscript
}

/etc/logrotate.d/flashmq

[halfgaar]

You're right, probably one should be packaged. I use this on my deployments:

/var/log/flashmq/*.log {
        daily
        dateformat .%Y-%m-%d
        dateyesterday 
        rotate 30
        noshred
        dateext
        missingok
        compress
        delaycompress
        ifempty
        create 0640 root root
        sharedscripts
        postrotate
          killall -SIGUSR1 flashmq
        endscript
}

I prefer dated file names that don't change, to make it easier for daily backups of all files on the server.

Also, you can see it uses SIGUSR1. That's specifically meant for log rotation and doesn't reload anything.

[Becker884]

Thank you, so I should just change "postrotate
killall -SIGUSR1 flashmq" for my script.
I've never heard of "SIGUSR1" !

[halfgaar]

Yeah, there are many signals. Essentially they are just numbers so only have a default action by standard, but the USR1 and USR2 are up to the application to define what they do. I chose this :)

[Becker884]

after changing to "postrotate killall -SIGUSR1 flashmq" I take a look at the log file and today I saw: log stays empty.
on my RPi logrotate doesn´t do anything.
I restarted flashmq.service:
Apr 25 07:32:22 flashmq[262733]: [2025-04-25 07:32:22.005] [INFO] [main] Switching logging from stdout t o logfile '/var/log/flashmq/flashmq.log'

so i switched to

/var/log/flashmq/flashmq.log {
    daily
    rotate 7
    compress
    delaycompress
    dateext
    missingok
    notifempty
    create 0644 root root
    postrotate
        systemctl reload flashmq >/dev/null 2>&1 || true
    endscript
}

0644 -> so I can take a look at the log file with non-root as before

[halfgaar]

There is probably another reason for that. Try just sending the signal on the command line and see if it logs that it's reopening the log file.