On Wed, Feb 5, 2020 at 9:40 AM Falconieri Falconieri <[email protected]> wrote: > > Hi all. > > I'm getting a critical error using tracd. I'm serving Trac for multiple envs, > using Ubuntu and MySQL 8. The performance is very good, everything is running > ok and performing very well. However during the day, something happens and > tracd stops to attend new requests. It is not deterministic. Suddenly, one > time per day tracd stops. And it is very strange because it keeps running but > nobody can access Trac because it does not respond any request. It is > incredible because the pidfile is still there and the process alive. The > resolution is to call "sudo systemctl restart tracd". Immediately, after > restarting, tracd starts to serve Trac again. > > Below is my systemd configuration: > > [Unit] > Description = Agilo Tracd Service > After=network.target > > [Service] > Type = forking > PIDFile=/tmp/tracd.pid > ExecStart = /usr/local/bin/tracd -p 443 --protocol https --certfile > /xxx/conf/server.crt --keyfile /xxx/conf/server.key > --basic-auth='*,/xxx/conf/trac.htpasswd, Trac' --hostname xxx.yyy.com -d > --pidfile /tmp/tracd.pid -e /xxx/trac-envs > KillMode=process > Restart=on-failure > > [Install] > WantedBy=multi-user.target > > Many people use this Trac. Could anyone give a hint on how to solve this > problem? > > Thanks.
Try to check systemd logs for tracd.service after reproducing the issue. $ systemctl status tracd.service $ journalctl -u tracd Also, I recommend using WSGI server (e.g. mod_wsgi) for production and tracd is not. -- Jun Omae <[email protected]> (大前 潤) -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/CAEVLMajxo34ioRLe7MuTUjyXZYuM7f7Q5VYGcoC4X3SUcTvdhQ%40mail.gmail.com.
