BIND 10 #2244: remove boss component, but boss still keeps trying to start it
BIND 10 Development
do-not-reply at isc.org
Thu Sep 6 13:27:29 UTC 2012
#2244: remove boss component, but boss still keeps trying to start it
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: defect | Status: new
Priority: medium | Milestone: New
Component: Boss of BIND | Tasks
Sensitive: 0 | Keywords:
Sub-Project: Core | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Boss keeps trying to start ddns (see ticket #2243). I don't need ddns so
I decide to not use it:
{{{
> config remove Boss/components b10-ddns
> config commit
> config show Boss/components/b10-ddns
Error: Boss/components/b10-ddns/kind not found
}}}
And config show Boss/components does not show it.
The log showed:
{{{
2012-09-06 08:19:30.781 DEBUG [b10-boss.boss]
BIND10_RECEIVED_NEW_CONFIGURATION
received new configuration: {'components': {'b10-cmdctl': {'kind':
'needed', 'sp
ecial': 'cmdctl'}, 'b10-xfrout': {'kind': 'dispensable'}, 'b10-auth':
{'priority
': 10, 'kind': 'needed', 'special': 'auth'}, 'b10-stats': {'kind':
'dispensable'
, 'address': 'Stats'}, 'b10-resolver': {'priority': 10, 'kind': 'needed',
'speci
al': 'resolver'}, 'b10-stats-httpd': {'kind': 'dispensable', 'address':
'StatsHt
tpd'}}}
2012-09-06 08:19:30.781 INFO [b10-boss.boss]
BIND10_CONFIGURATOR_RECONFIGURE re
configuring running components
2012-09-06 08:19:30.781 DEBUG [b10-boss.boss] BIND10_CONFIGURATOR_BUILD
building
plan '{'sockcreator': ({'priority': 200, 'kind': 'core', 'special':
'sockcreato
r'}, <isc.bind10.special_component.SockCreator object at 0x7f7ff57ed610>),
'msgq
': ({'priority': 199, 'kind': 'core', 'special': 'msgq'},
<isc.bind10.special_co
mponent.Msgq object at 0x7f7ff57ed650>), 'b10-cmdctl': ({'kind': 'needed',
'spec
ial': 'cmdctl'}, <isc.bind10.special_component.CmdCtl object at
0x7f7ff5322050>)
, 'b10-xfrout': ({'kind': 'dispensable'}, <isc.bind10.component.Component
object
at 0x7f7ff5322090>), 'b10-auth': ({'priority': 10, 'kind': 'needed',
'special':
'auth'}, <isc.bind10.special_component.Auth object at 0x7f7ff5322110>),
'cfgmgr
': ({'priority': 198, 'kind': 'core', 'special': 'cfgmgr'},
<isc.bind10.special_
component.CfgMgr object at 0x7f7ff57ed690>), 'b10-ddns': ({'kind':
'dispensable'
}, <isc.bind10.component.Component object at 0x7f7ff5311fd0>),
'b10-stats': ({'k
ind': 'dispensable', 'address': 'Stats'}, <isc.bind10.component.Component
object
at 0x7f7ff5311e90>), 'b10-resolver': ({'priority': 10, 'kind': 'needed',
'speci
al': 'resolver'}, <isc.bind10.special_component.Resolver object at
0x7f7ff5311f5
0>), 'b10-stats-httpd': ({'kind': 'dispensable', 'address': 'StatsHttpd'},
<isc.
bind10.component.Component object at 0x7f7ff53220d0>)}' ->
'{'b10-resolver': {'p
riority': 10, 'kind': 'needed', 'special': 'resolver'}, 'sockcreator':
{'priorit
y': 200, 'kind': 'core', 'special': 'sockcreator'}, 'msgq': {'priority':
199, 'k
ind': 'core', 'special': 'msgq'}, 'b10-stats': {'kind': 'dispensable',
'address'
: 'Stats'}, 'b10-cmdctl': {'kind': 'needed', 'special': 'cmdctl'},
'b10-xfrout':
{'kind': 'dispensable'}, 'b10-stats-httpd': {'kind': 'dispensable',
'address':
'StatsHttpd'}, 'b10-auth': {'priority': 10, 'kind': 'needed', 'special':
'auth'}
, 'cfgmgr': {'priority': 198, 'kind': 'core', 'special': 'cfgmgr'}}'
2012-09-06 08:19:30.782 DEBUG [b10-boss.boss] BIND10_CONFIGURATOR_RUN
running pl
an of 0 tasks
2012-09-06 08:19:30.788 DEBUG [b10-cmdctl.cmdctl] CMDCTL_SEND_COMMAND
sending co
mmand get_config to module ConfigManager
2012-09-06 08:19:30.788 DEBUG [b10-cmdctl.cmdctl] CMDCTL_COMMAND_SENT
command 'g
et_config' to module 'ConfigManager' was sent
}}}
Then a few seconds later:
{{{
2012-09-06 08:19:35.826 INFO [b10-boss.boss] BIND10_COMPONENT_START
component b
10-ddns is starting
}}}
And this keeps happening.
{{{
2012-09-06 08:24:59.409 INFO [b10-boss.boss] BIND10_PROCESS_ENDED process
24982 of b10-ddns ended with status 0
2012-09-06 08:24:59.409 ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED
component b10-ddns (pid 24982) failed: process exited normally with exit
status 0
2012-09-06 08:25:06.053 INFO [b10-boss.boss] BIND10_COMPONENT_START
component b10-ddns is starting
2012-09-06 08:25:06.053 INFO [b10-boss.boss] BIND10_STARTING_PROCESS
starting process b10-ddns
2012-09-06 08:25:06.065 DEBUG [b10-boss.boss] BIND10_STARTED_PROCESS_PID
started b10-ddns (PID 6493)
}}}
and so on ...
So I did a "Boss shutdown" and restarted and it no longer tried to start
ddns.
--
Ticket URL: <http://bind10.isc.org/ticket/2244>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list