Bug 479400 – mail-filter/postgrey-1.34-r1 - start-stop-daemon: on start fopen `/var/run/postgrey.pid': No such file or directory

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description bagrx 2013-08-01 13:06:29 UTC]

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

[Comment 1 bagrx 2013-08-01 13:07:37 UTC]

Created attachment 354820 [details]
emerge --info

[Comment 2 Alexander Vershilov (RETIRED) 2013-08-02 20:33:08 UTC]

(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.

[Comment 3 Alexander Vershilov (RETIRED) 2013-08-02 20:50:58 UTC]

(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

[Comment 4 bagrx 2013-08-02 21:34:59 UTC]

(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

[Comment 5 Aleksandr Zagzin 2013-09-07 17:50:28 UTC]

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

[Comment 6 bagrx 2013-09-09 10:05:10 UTC]

I removed -T from postgrey script as suggested and now is working.

Thanks

[Comment 7 Alexander Vershilov (RETIRED) 2013-09-09 14:26:31 UTC]

(In reply to Bagr from comment #6)
> I removed -T from postgrey script as suggested and now is working.
> 
> Thanks

Fixed in tree. Thanks.

[Comment 8 Julian Ospald 2014-08-13 13:30:06 UTC]

please don't close bugs that affect stable and have not been fixed in stable yet

[Comment 9 Julian Ospald 2014-08-13 14:14:05 UTC]

either update to postgrey-1.35-r1 or postgrey-1.34-r3

[Comment 10 Alex Brandt (RETIRED) 2014-10-25 20:45:20 UTC]

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?

[Comment 11 bagrx 2014-10-27 07:23:25 UTC]

postgrey-1.34-r3 is working and bug can to be closed as resolved

[Comment 12 Alex Brandt (RETIRED) 2014-11-01 15:54:02 UTC]

Marking as resolved since dependent bug is solved and this one is confirmed as solved.