Bug 502171

Summary:	Errors at startup
Product:	[Fedora] Fedora	Reporter:	Adam Huffman <bloch>
Component:	condor	Assignee:	Matthew Farrellee <matt>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	10	CC:	matt
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:	2009-05-22 15:21:00 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 Adam Huffman 2009-05-22 10:22:56 UTC

Description of problem:

When starting condor I see these errors in MasterLog:

5/22 10:35:20 DaemonCore: ERROR: Can't open pid file /var/run/condor/condor_master.pid
5/22 10:35:20 FileLock::obtain(1) failed - errno 11 (Resource temporarily unavailable)
5/22 10:35:20 ERROR "Can't get lock on "/var/lib/condor/log/InstanceLock"" at line 933 in file master.cpp

They don't seem to be fatal.

Version-Release number of selected component (if applicable):
condor-7.2.3-1.fc10.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Matthew Farrellee 2009-05-22 13:19:11 UTC

Those should be fatal. I'm guessing you ran the condor_master as a non-root user.

You should check to see if the files exist and who owns them.

Comment 2 Adam Huffman 2009-05-22 14:35:14 UTC

-rw------- 1 condor condor      0 2009-05-22 10:35 InstanceLock

so, it does exist.

As for /var/run/condor/condor_master.pid, there isn't even a /var/run/condor directory.

Comment 3 Matthew Farrellee 2009-05-22 15:21:00 UTC


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