Bug 604812 - condor tools can't act upon condor_kbdd
Summary: condor tools can't act upon condor_kbdd
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor
Version: Development
Hardware: All
OS: Linux
medium
medium
Target Milestone: 1.3
: ---
Assignee: Robert Rati
QA Contact: Luigi Toscano
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-16 18:58 UTC by Robert Rati
Modified: 2010-10-20 11:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Robert Rati 2010-06-16 18:58:29 UTC 
Description of problem:
The condor tools are unable to act upon the kbdd daemon:

condor_restart -subsystem kbdd
ERROR "Unknown daemon type (7) in Daemon::init" at line 1007 in file daemon.cpp


Version-Release number of selected component (if applicable):
7.4.3-0.18

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Robert Rati 2010-06-16 19:24:30 UTC 
The issue is that, internally, the kbdd has its own daemon type, but it is not recognized by the Daemon::locate method.  Added the kbdd to the list of daemon types locate will handle, and use NO_AD as the ad type since it doesn't register with the collector.

Fixed in:
condor-7.4.3-0.20
Comment 2 Robert Rati 2010-06-16 19:28:24 UTC 
Make that:
condor-7.4.3-0.21
Comment 3 Luigi Toscano 2010-09-27 20:23:52 UTC 
condor_reconfig/condor_restart now accept -subsystem kbdd and properly operate on it.

Verified on RHEL 4.8/5.5, i386/x86_64.
condor-7.4.4-0.15
condor-kbdd-7.4.4-0.15
Note You need to log in before you can comment on or make changes to this bug.