Bug 5977 - postgrey does not create specified pidfile that confuses systemd
Summary: postgrey does not create specified pidfile that confuses systemd
Status: RESOLVED DUPLICATE of bug 6392
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Michael Scherer
QA Contact:
URL:
Whiteboard: MGA2TOO
Keywords: Junior_job
Depends on:
Blocks:
 
Reported: 2012-05-19 17:22 CEST by Zoltan Balaton
Modified: 2012-06-25 22:50 CEST (History)
1 user (show)

See Also:
Source RPM: postgrey-1.34-1.mga2.src.rpm
CVE:
Status comment:


Attachments
Add --pidfile option to /etc/sysconfig/postgray (366 bytes, patch)
2012-05-29 21:16 CEST, Zoltan Balaton
Details | Diff

Description Zoltan Balaton 2012-05-19 17:22:15 CEST
The init script of postgrey claims:

# processname: postgrey
# pidfile: /var/run/greylist.pid

but postgrey does not create this pid file by default and no --pidfile option is given (neither in the init script nor in /etc/sysconfig/postgrey). Thus systemd thinks the service is failed when in fact it is running:

postgrey[12588]: Starting postgrey:[  OK  ]
systemd[1]: PID file /var/run/greylist.pid not readable (yet?) after start.
systemd[1]: postgrey.service operation timed out. Terminating.
systemd[1]: Unit postgrey.service entered failed state.

$ systemctl status postgrey.service 
postgrey.service - LSB: Starts the postfix Greylisting Policy Server
	  Loaded: loaded (/etc/rc.d/init.d/postgrey)
	  Active: failed (Result: timeout) since Sat, 19 May 2012 16:50:55 +0200; 27min ago
	 Process: 12588 ExecStart=/etc/rc.d/init.d/postgrey start (code=exited, status=0/SUCCESS)
	  CGroup: name=systemd:/system/postgrey.service
		  รข 12645 /usr/sbin/postgrey -d --unix=/var/spool/postfix/ex...
Manuel Hiebel 2012-05-21 12:50:07 CEST

Keywords: (none) => Junior_job
Assignee: bugsquad => misc

Comment 1 Marja Van Waes 2012-05-26 13:06:24 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 2 Zoltan Balaton 2012-05-29 21:15:08 CEST
I reported the bug shortly before the release of Mageia 2 and haven't seen an update yet so I assume it's still valid. There's more than one possible way to fix this, I attach a workaround I'm using now.
Comment 3 Zoltan Balaton 2012-05-29 21:16:19 CEST
Created attachment 2401 [details]
Add --pidfile option to /etc/sysconfig/postgray
Zoltan Balaton 2012-05-29 21:18:07 CEST

Attachment 2401 is patch: 0 => 1
Attachment 2401 mime type: application/octet-stream => text/plain

Sander Lepik 2012-05-29 22:10:09 CEST

Keywords: NEEDINFO => (none)
CC: (none) => sander.lepik
Whiteboard: (none) => MGA2TOO

Comment 4 Zoltan Balaton 2012-06-25 22:50:43 CEST

*** This bug has been marked as a duplicate of bug 6392 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.