Bug 1034640 - CLI tools fail to locate proper condor daemon
Summary: CLI tools fail to locate proper condor daemon
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor
Version: 2.3
Hardware: i686
OS: Linux
high
medium
Target Milestone: ---
: ---
Assignee: grid-maint-list
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-26 09:20 UTC by Tomas Rusnak
Modified: 2016-05-26 19:13 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-26 19:13:21 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Tomas Rusnak 2013-11-26 09:20:50 UTC 
Description of problem:
Calling condor_userprio in the loop sometimes fails to locate negotiator daemon. 

Version-Release number of selected component (if applicable):
RH-7.8.9-0.5

How reproducible:
<30%

Steps to Reproduce:
1. start personal condor
2. for i in `seq 1000`; do condor_userprio -setfactor "user${i}@localdomain 2.0"
3. some should fail with /usr/bin/condor_userprio: Can't locate negotiator in local pool

Actual results:
condor_userprio fails to locate negotiator

Expected results:
no fails
Comment 8 Lubos Trilety 2014-04-07 14:05:38 UTC 
Similar problem can be found for other CLI tools too (condor_q, condor_status ...).
e.g.
$ time for j in {0..5000}; do condor_status; done > /dev/null
Error: communication error
Error: communication error

real	0m56.156s
user	0m32.096s
sys	0m8.431s

Note though that it happens only on 32bit machines.
Comment 13 Anne-Louise Tangring 2016-05-26 19:13:21 UTC 
MRG-G is in maintenance only and only customer escalations will be addressed from this point forward. This issue can be re-opened if a customer escalation associated with this issue occurs.
Note You need to log in before you can comment on or make changes to this bug.