Bug 2213840

Summary:	"Can't open PID file" in logs
Product:	[Fedora] Fedora EPEL	Reporter:	Stefano Biagiotti <stefano.biagiotti>
Component:	amavisd-milter	Assignee:	Robert Scheck <redhat-bugzilla>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	epel8	CC:	redhat-bugzilla
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stefano Biagiotti 2023-06-09 14:35:32 UTC

# rpm -q amavisd-milter
amavisd-milter-1.7.2-1.el8.x86_64

Every time amavisd-milter starts, systemd complains about the PID file.
Jun  9 11:49:24 x systemd[1]: amavisd-milter.service: Can't open PID file /run/amavisd/amavisd-milter.pid (yet?) after start: No such file or directory

An easy workaround is "ExecStartPost=/bin/sleep 1".

# cat /etc/systemd/system/amavisd-milter.service.d/amavisd.conf 
[Unit]
After=amavisd.service
[Service]
ExecStartPost=/bin/sleep 1

Comment 1 Robert Scheck 2023-06-11 22:35:46 UTC

I am sorry, but "/bin/sleep 1" is not an option. Does /run/amavisd/amavisd-milter.pid exist in the end - and this is just a cosmetic issue? Or is /run/amavisd/amavisd-milter.pid really missing (for longer than the race-condition during the daemon startup)?

Comment 2 Stefano Biagiotti 2023-06-12 10:35:09 UTC

/run/amavisd/amavisd-milter.pid exists and everything works.
I just saw the "Can't open PID file" error in logs and decided to report.