Bug 286171

Summary: fetchmail complains about another fetchmail running
Product: [Fedora] Fedora Reporter: n0dalus <n0dalus+redhat>
Component: fetchmailAssignee: Vitezslav Crhonek <vcrhonek>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: medium    
Version: 7   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-09-20 08:06:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description n0dalus 2007-09-11 15:20:10 UTC 
Description of problem:
I have a cronjob that recently has been outputting an error every time it runs
(using fetchmail):
fetchmail: can't poll specified hosts with another fetchmail running at <number>.

The problem is, there is definitely no other fetchmail running, and there is no
stale .fetchmail.pid file lying around. To make matters more complicated, I am
unable to reproduce this outside of a cronjob. Running fetchmail directly on the
shell produces no error message.

Here is the cron entry:

*/5 * * * * fetchmail myserver > /dev/null

I have had no problems until the update to fetchmail-6.3.7-2.fc7, at which point
the problem has occurred every time the cronjob runs.

I put an strace into the cronjob (strace -o /tmp/straceout fetchmail myserver),
and it shows a successful open() for reading only of .fetchmail.pid - which
makes no sense as the file does not exist. I suspect that there is a threading
issue or something.

Version-Release number of selected component (if applicable):
fetchmail-6.3.7-2.fc7

How reproducible:
Only from the cronjob for some reason
Comment 1 n0dalus 2007-09-20 08:06:22 UTC 
Found the problem - for some reason, there were two crond's running. So two
fetchmail instances were being started simultaneously every time. If it happens
again I'll file a bug against vixie-cron instead.

Apologies for the non-bug report. Closing.