Bug 706397

Summary: TBM* files in condor\bin directory
Product: Red Hat Enterprise MRG Reporter: Martin Kudlej <mkudlej>
Component: condorAssignee: Timothy St. Clair <tstclair>
Status: CLOSED WONTFIX QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 2.0CC: iboverma, jneedle, matt
Target Milestone: 2.1Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-12 15:42:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Martin Kudlej 2011-05-20 12:28:11 UTC
Description of problem:
I've done installation and repair of condor on Windows and it creates strange TBM* files in condor\bin directory.

Version-Release number of selected component (if applicable):
Windows 2003 32/64 bit
condor-win-7.6.1-0.5

How reproducible:
100%

Steps to Reproduce:
1. install condor
2. restart OS
3. repair condor
4. restart OS
5. check condor\bin directory
  
Actual results:
There are TBM* files in condor\bin directory.

Expected results:
There are no TBM* files in condor\bin directory.

Comment 2 Timothy St. Clair 2011-05-23 16:55:35 UTC
In the install log I see the following: 
------------------- Begin snip:

Info 1603. The file C:\condor\bin\k5sprt32.dll is being held in use. Close that application and retry.
Info 1902. Scheduling reboot operation: Renaming file C:\condor\bin\TBMD.tmp to C:\condor\bin\k5sprt32.dll. Must reboot to complete operation.
Info 1603. The file C:\condor\bin\ssleay32.dll is being held in use. Close that application and retry.
Info 1902. Scheduling reboot operation: Renaming file C:\condor\bin\TBME.tmp to C:\condor\bin\ssleay32.dll. Must reboot to complete operation.
Info 1603. The file C:\condor\bin\libpcre.dll is being held in use. Close that application and retry.
Info 1902. Scheduling reboot operation: Renaming file C:\condor\bin\TBMF.tmp to C:\condor\bin\libpcre.dll. Must reboot to complete operation.
Info 1603. The file C:\condor\bin\libeay32.dll is being held in use. Close that application and retry.
Info 1902. Scheduling reboot operation: Renaming file C:\condor\bin\TBM10.tmp to C:\condor\bin\libeay32.dll. Must reboot to complete operation.
Info 1603. The file C:\condor\bin\condor_kbdd.exe is being held in use. Close that application and retry.
MSI (s) (4C:84) [08:03:10:531]: Product: condor-7.6.1. The file C:\condor\bin\condor_kbdd.exe is being held in use by the following process Name: condor_kbdd , Id 1832.

Info 1902. Scheduling reboot operation: Renaming file C:\condor\bin\TBM11.tmp to C:\condor\bin\condor_kbdd.exe. Must reboot to complete operation.
Info 1603. The file C:\condor\bin\comerr32.dll is being held in use. Close that application and retry.
Info 1902. Scheduling reboot operation: Renaming file C:\condor\bin\TBM12.tmp to C:\condor\bin\comerr32.dll. Must reboot to complete operation.
Info 1603. The file C:\condor\bin\krb5_32.dll is being held in use. Close that application and retry.
Info 1902. Scheduling reboot operation: Renaming file C:\condor\bin\TBM13.tmp to C:\condor\bin\krb5_32.dll. Must reboot to complete operation.

------------------- End snip:


What happens on a restart?

Comment 3 Timothy St. Clair 2011-05-24 13:47:47 UTC
Also, what happens when you "net stop condor + kill kbdd" prior to repair?

Comment 4 Martin Kudlej 2011-05-25 06:58:10 UTC
I've done these:
1) repair; kill kbdd; restart -> TBM* files are there
2) kill kbdd; repair; restart -> TBM* files are not there

I should highlight that I see it only on 2003 64/32 bit.

Comment 6 Timothy St. Clair 2011-07-08 17:17:49 UTC
Tried a couple of options with Custom Actions but none have the desired results.  When looking at different versions of windows I've detected that they do the correct thing, and as mentioned before there is a workaround for this specific version of windows.  Needless to mention Server 2003 is past mainstream support end date.

CLOSE->WONTFIX

Comment 9 Timothy St. Clair 2011-07-11 18:33:22 UTC
Issue: 
   TBM* files in condor\bin directory during <repair> of condor on Server 2003. 

Resolution:
   taskkill /F /IM condor_kbdd.exe prior to running repair.