Bug 672239

Summary: Starting condor on a loaded Windows system can cause configd cycling.
Product: Red Hat Enterprise MRG Reporter: Timothy St. Clair <tstclair>
Component: condorAssignee: Robert Rati <rrati>
Status: CLOSED INSUFFICIENT_DATA QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: low Docs Contact:
Priority: low    
Version: DevelopmentCC: iboverma, matt, mkudlej, rrati, tstclair
Target Milestone: 2.0   
Target Release: ---   
Hardware: i686   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-25 16:45:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
MasterLog none

Description Timothy St. Clair 2011-01-24 15:02:45 UTC 
Description of problem:
When attempting to start condor on loaded windows system (running other services&apps) it appears that the configd goes into a cycling loop, where the configd will exit w/status 1.

Version-Release number of selected component (if applicable):
3-9.2

How reproducible:
100%

Steps to Reproduce:
1. Load a system either either a service or task @ normal priority.  My specific case was an Intel SSD re-balancing service
2. net start condor
3. Monitor process explorer and MasterLog 
  
Actual results:
From the master log it appears that the configd fails without any logs.

Expected results:
normal startup
Comment 1 Timothy St. Clair 2011-01-24 16:03:30 UTC 
Created attachment 474978 [details]
MasterLog
Comment 2 Robert Rati 2011-03-25 16:45:42 UTC 
Haven't been able to repro except on a Win XP machine and Intel's SSD re-balancing software running.  Given the resources consumed by the SSD re-balancer, this could be a lack of memory/disk space needed to start the python interpreter and run the configd.  On win7, the same sw doesn't cause near as high a load and the issue is not reproducible.