Summary: | mail-filter/amavisd-new-2.11.1-r3: rc-status reports amavisd-new stopped even if it's started | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tomáš Mózes <hydrapolic> |
Component: | Current packages | Assignee: | Net-Mail Packages <net-mail+disabled> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | antivirus, mjo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=675196 https://bugs.gentoo.org/show_bug.cgi?id=669206 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tomáš Mózes
2019-01-11 18:31:59 UTC
Ironically, I rewrote the init script for v2.11.1 (in part) to fix the exact opposite issue: bug #646336. The new init script runs amavis in the foreground, so it should be easy to figure out what's going wrong. Amavis no longer creates its own PID file, so there's only one PID file at /run/amavisd.pid containing the PID of the "amavis (master)" process. When you try to stop the service, OpenRC should kill the PID contained in that file, and not succeed until the process is dead. But from your "ps" output, it obviously isn't... Can you tell me what's in that PID file after a fresh start, and what happens during/after you tell OpenRC to stop it? What's in the PID file (and what is the PID of the amavis master process) after the problem appears? Ping =) Sorry it took me so long and it's a false alarm. The problem was that I had app-admin/monit with old pidfile location. After adjusting the pidfile to /run/amavisd.pid it works properly. |