Bug 1622635

Looks like qdrouterd does not re-create the log file upon receiving SIGHUP or any other signal:

As per:
https://github.com/apache/qpid-dispatch/blob/master/router/src/main.c

/**
 * This is the OS signal handler, invoked on an undetermined thread at a completely
 * arbitrary point of time.
 */
static void signal_handler(int signum)
{
    /* Ignore future signals, dispatch may already be freed */
    signal(SIGHUP,  SIG_IGN);
    signal(SIGQUIT, SIG_IGN);
    signal(SIGTERM, SIG_IGN);
    signal(SIGINT,  SIG_IGN);
    switch (signum) {
    case SIGINT:
        exit_with_sigint = 1;
        // fallthrough
    case SIGQUIT:
    case SIGTERM:
        qd_server_stop(dispatch); /* qpid_server_stop is signal-safe */
        break;
    default:
        break;
    }
}



So the only possible way to implement log rotation is through logrotate's copytruncate (see logrotate.conf(8)).

I'm attaching a sample /etc/logrotate.d/qdrouterd.conf that should work fine.

Created attachment 1479041 [details]
sample /etc/logrotate.d/qdrouterd.conf

Place this file under /etc/logrotate.d/ and wait a few days to see /var/log/qdrouterd.log get rotated.

Won't we return back to qpidd and qdrouterd logging via syslog, what would make this BZ redundant?

(In reply to Pavel Moravec from comment #4)
> Won't we return back to qpidd and qdrouterd logging via syslog, what would
> make this BZ redundant?

Yes we are, in 6.4 and also in Sat6.5 HTB:

log {
    module: DEFAULT
    enable: info+
    timestamp: true
    output: syslog
}


So I will close this BZ as resolved - qdrouterd logs are logrotated (again) since 6.4.