After machine upgrade there is a problem with postgrey start up script. The main problem is that postgrey does not set pid file. After start rc-status gives crashed and if i restart it prints start-stop-daemon: on start fopen `/var/run/postgrey.pid': No such file or directory Even if i ran postgrey --inet=127.0.0.1:10030 --pidfile=/var/run/postgrey.pid --delay=300 in terminal there is no pid file, but the process is running Reproducible: Always
Created attachment 354820 [details] emerge --info
(In reply to Bagr from comment #0) > After machine upgrade there is a problem with postgrey start up script. > The main problem is that postgrey does not set pid file. > After start rc-status gives crashed and if i restart it prints > start-stop-daemon: on start fopen `/var/run/postgrey.pid': No such file or > directory > > Even if i ran postgrey --inet=127.0.0.1:10030 > --pidfile=/var/run/postgrey.pid --delay=300 in terminal there is no pid > file, but the process is running > > Reproducible: Always do you have /var/run -> /run symlink? If no can you try to create it manually and test, if it's a root of an issue then init script should be fixed. Thanks.
(In reply to Alexander Vershilov from comment #2) > (In reply to Bagr from comment #0) > > After machine upgrade there is a problem with postgrey start up script. > > The main problem is that postgrey does not set pid file. > > After start rc-status gives crashed and if i restart it prints > > start-stop-daemon: on start fopen `/var/run/postgrey.pid': No such file or > > directory > > > > Even if i ran postgrey --inet=127.0.0.1:10030 > > --pidfile=/var/run/postgrey.pid --delay=300 in terminal there is no pid > > file, but the process is running > > > > Reproducible: Always > > do you have /var/run -> /run symlink? If no can you try to create it > manually and test, if it's a root of an issue then init script should be > fixed. Thanks. UPD. or just change conf.d POSTGREY_PID to /run/postgrey.pid
(In reply to Alexander Vershilov from comment #3) > (In reply to Alexander Vershilov from comment #2) > > (In reply to Bagr from comment #0) > > > After machine upgrade there is a problem with postgrey start up script. > > > The main problem is that postgrey does not set pid file. > > > After start rc-status gives crashed and if i restart it prints > > > start-stop-daemon: on start fopen `/var/run/postgrey.pid': No such file or > > > directory > > > > > > Even if i ran postgrey --inet=127.0.0.1:10030 > > > --pidfile=/var/run/postgrey.pid --delay=300 in terminal there is no pid > > > file, but the process is running > > > > > > Reproducible: Always > > > > do you have /var/run -> /run symlink? If no can you try to create it > > manually and test, if it's a root of an issue then init script should be > > fixed. Thanks. > > UPD. or just change conf.d POSTGREY_PID to /run/postgrey.pid I have /var/run -> /run symlink and I tried edit POSTGREY_PID to /run/postgrey.pid but still same problem start-stop-daemon: on start fopen `/run/postgrey.pid': No such file or directory
from http://forums.gentoo.org/viewtopic-t-954454-start-0.html this problem can be fixed by removing -T from #!/usr/bin/perl -T -w in the postgrey script
I removed -T from postgrey script as suggested and now is working. Thanks
(In reply to Bagr from comment #6) > I removed -T from postgrey script as suggested and now is working. > > Thanks Fixed in tree. Thanks.
please don't close bugs that affect stable and have not been fixed in stable yet
either update to postgrey-1.35-r1 or postgrey-1.34-r3
Looks like a working version of postgrey has been marked stable. Am I missing anything or is this bug able to be closed as resolved?
postgrey-1.34-r3 is working and bug can to be closed as resolved
Marking as resolved since dependent bug is solved and this one is confirmed as solved.