On Thu, Sep 6, 2018, at 8:34 AM, Dmitry Makovey wrote:

I've been looking for a while and cannot find any information regarding log rotation for Mailman3.

We're running containerized deployment which complicates the matter slightly, but having "some" approach for log rotation would be helpful. So before I dig into the code looking for SIGUSR1 or SIGHUP handlers can someone point me to a proper documentation for log management with MM3 ?

You can send SIGHUP to master runner process to reopen all the log files.

-- Sr System and DevOps Engineer SoM IRT

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Email had 1 attachment:

• signature.asc 1k (application/pgp-signature)

-- thanks, Abhilash Raj (maxking)

On 09/06/2018 08:34 AM, Dmitry Makovey wrote:

We're running containerized deployment which complicates the matter slightly, but having "some" approach for log rotation would be helpful. So before I dig into the code looking for SIGUSR1 or SIGHUP handlers can someone point me to a proper documentation for log management with MM3 ?

Log rotation per se is not done by Mailman. It is up to some external process like logrotate.

As far as reopening logs post rotation is concerned, the mailman command 'mailman reopen' is used for the core logs. What is done for web logs depends on the web configuration.

With gunicorn I use

    if [ -r /opt/mailman/mm/var/gunicorn.pid ]; then
        PID=`cat /opt/mailman/mm/var/gunicorn.pid`
        kill -s USR1 $PID
    fi

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan