Bug 2213840 - "Can't open PID file" in logs
Summary: "Can't open PID file" in logs
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: amavisd-milter
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-09 14:35 UTC by Stefano Biagiotti
Modified: 2023-06-12 10:35 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.