Public bug reported: Ubuntu 12.04.4 LTS, 64-bit version postgrey 1.34-1
I cannot force reload of whitelist with reload commend to service script of postgrey # service postgrey reload * Reloading postfix greylisting daemon configuration...... [fail] This command is called from the script /etc/init.d/postgrey, it looks OK: start-stop-daemon --stop --signal 1 --quiet --pidfile /var/run/postgrey.pid --name postgrey When I manually send signal 1 to postgrey, whitelists are reloaded, so it proves that postgrey handles signal 1 correctly. Problem is with PID file, /var/run/postgrey.pid. PID stored in the file is not the PID of running postgrey. # cat /var/run/postgrey.pid 3932 # ps -p 3932 PID TTY TIME CMD # ps ax | grep postgrey | grep -v grep 1084 ? Ss 0:11 /usr/sbin/postgrey --pidfile=/var/run/postgrey.pid --daemonize --inet=10023 postgrey runs with PID 1084 but 3932 is reported in /var/run/postgrey.pid Status query has the same problem, it report that postgrey is not running but it is not true because it runs with different PID... # service postgrey status * postgrey is not running ** Affects: postgrey (Ubuntu) Importance: Undecided Status: New ** Description changed: Ubuntu 12.04.4 LTS, 64-bit version postgrey 1.34-1 I cannot force reload of whitelist with reload commend to service script of postgrey # service postgrey reload - * Reloading postfix greylisting daemon configuration...... [fail] + * Reloading postfix greylisting daemon configuration...... [fail] - This command is called from the script, it looks OK: + This command is called from the script /etc/init.d/postgrey, it looks + OK: start-stop-daemon --stop --signal 1 --quiet --pidfile /var/run/postgrey.pid --name postgrey When I manually send signal 1 to postgrey, whitelists are reloaded, so it proves that postgrey handles signal 1 correctly. Problem is with PID file, /var/run/postgrey.pid. PID stored in the file is not the PID of running postgrey. # cat /var/run/postgrey.pid 3932 # ps -p 3932 - PID TTY TIME CMD + PID TTY TIME CMD # ps ax | grep postgrey | grep -v grep - 1084 ? Ss 0:11 /usr/sbin/postgrey --pidfile=/var/run/postgrey.pid --daemonize --inet=10023 + 1084 ? Ss 0:11 /usr/sbin/postgrey --pidfile=/var/run/postgrey.pid --daemonize --inet=10023 postgrey runs with PID 1084 but 3932 is reported in /var/run/postgrey.pid ** Description changed: Ubuntu 12.04.4 LTS, 64-bit version postgrey 1.34-1 I cannot force reload of whitelist with reload commend to service script of postgrey # service postgrey reload * Reloading postfix greylisting daemon configuration...... [fail] This command is called from the script /etc/init.d/postgrey, it looks OK: - start-stop-daemon --stop --signal 1 --quiet --pidfile + start-stop-daemon --stop --signal 1 --quiet --pidfile /var/run/postgrey.pid --name postgrey When I manually send signal 1 to postgrey, whitelists are reloaded, so it proves that postgrey handles signal 1 correctly. Problem is with PID file, /var/run/postgrey.pid. PID stored in the file is not the PID of running postgrey. # cat /var/run/postgrey.pid 3932 # ps -p 3932 PID TTY TIME CMD # ps ax | grep postgrey | grep -v grep 1084 ? Ss 0:11 /usr/sbin/postgrey --pidfile=/var/run/postgrey.pid --daemonize --inet=10023 postgrey runs with PID 1084 but 3932 is reported in /var/run/postgrey.pid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289424 Title: postgrey cannot do reload (init.d script) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgrey/+bug/1289424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs