Bug 672239 - Starting condor on a loaded Windows system can cause configd cycling.
Summary: Starting condor on a loaded Windows system can cause configd cycling.
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor
Version: Development
Hardware: i686
OS: Windows
low
low
Target Milestone: 2.0
: ---
Assignee: Robert Rati
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-24 15:02 UTC by Timothy St. Clair
Modified: 2011-03-25 16:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-25 16:45:42 UTC
Target Upstream Version:

Attachments (Terms of Use)
MasterLog (13.11 KB, text/plain)
2011-01-24 16:03 UTC, Timothy St. Clair 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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