Bug 624943

Summary: quickly killing condor_configd running in debugging mode
Product: Red Hat Enterprise MRG Reporter: Lubos Trilety <ltrilety>
Component: condor-wallaby-clientAssignee: Robert Rati <rrati>
Status: CLOSED CURRENTRELEASE QA Contact: Lubos Trilety <ltrilety>
Severity: low Docs Contact:
Priority: low    
Version: 1.3CC: matt
Target Milestone: 1.3.2   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: condor-wallaby-client-3.6-6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-15 13:02:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Lubos Trilety 2010-08-18 08:10:58 UTC
Description of problem:
When configd running in debugging mode is killed quickly after it's started, the exception appears.

Version-Release number of selected component (if applicable):
condor-wallaby-client-3.4-1

How reproducible:
100%

Steps to Reproduce:
1. Terminal one, start configd with '-d' option
$ _CONDOR_QMF_BROKER_HOST=localhost _CONDOR_QMF_CONFIGD_LOG=configd.log /usr/sbin/condor_configd -d

2. Terminal two run
$ killall -v condor_configd

  
Actual results:
Notice exception in terminal one
Traceback (most recent call last):
  File "/usr/lib64/python2.4/logging/handlers.py", line 71, in emit
    if self.shouldRollover(record):
  File "/usr/lib64/python2.4/logging/handlers.py", line 150, in shouldRollover
    self.stream.seek(0, 2)  #due to non-posix-compliant Windows feature
ValueError: I/O operation on closed file
Traceback (most recent call last):
  File "/usr/lib64/python2.4/logging/handlers.py", line 71, in emit
    if self.shouldRollover(record):
  File "/usr/lib64/python2.4/logging/handlers.py", line 150, in shouldRollover
    self.stream.seek(0, 2)  #due to non-posix-compliant Windows feature
ValueError: I/O operation on closed file


Expected results:
No exception

Comment 1 Robert Rati 2010-11-03 13:16:23 UTC
Unable to reproduce in the 3.6 build shipping with 1.3.  I believe this has been resolved already.

Comment 2 Lubos Trilety 2010-11-03 15:05:33 UTC
Tested with condor-wallaby-client-3.6-6, run 100 times without the exception.

Tested on:
RHEL5 x86_64,i386  - passed
RHEL4 x86_64,i386  - passed

>>> VERIFIED