BIND 10 #2696: dhcp4 component shutdown issues
BIND 10 Development
do-not-reply at isc.org
Wed Feb 6 20:20:25 UTC 2013
#2696: dhcp4 component shutdown issues
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: | Status: new
defect | Milestone: New Tasks
Priority: | Keywords:
medium | Sensitive: 0
Component: | Sub-Project: Core
Unclassified | Estimated Difficulty: 0
CVSS Scoring: | Total Hours: 0
Defect Severity: N/A |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
In bindctl:
{{{
> config remove Boss/components b10-dhcp4
> config commit
Error: [Errno 32] Broken pipe
Configuration not committed
}}}
It appears the configuration was removed as viewable by bindctl. The
process was not stopped. I manually killed it (and it was not restarted).
Soon later I upgraded and restart bind10 (now using b10-init). But the
component configuration for b10-dhcp4 still existed so I tried to stop by
removing the component.
{{{
2013-02-06 13:54:07.487 DEBUG [b10-init.init/18558]
BIND10_CONFIGURATOR_TASK performing task stop on b10-dhcp4
2013-02-06 13:54:07.488 INFO [b10-init.init/18558] BIND10_COMPONENT_STOP
component b10-dhcp4 is being stopped
2013-02-06 13:54:07.488 INFO [b10-init.init/18558] BIND10_STOP_PROCESS
asking b10-dhcp4 to shut down
}}}
But no log message from b10-dhcp4 (no DHCP4_SHUTDOWN_REQUEST and no
DHCP4_SHUTDOWN) and the b10-dhcp4 process was still running.
I did a "Dhcp4 shutdown" and that worked.
To retest, I re-added the component and it started. Then I tried to stop:
{{{
> config remove Init/components b10-dhcp4
> config commit
Error: [Errno 32] Broken pipe
Configuration not committed
}}}
b10-dhcp4 was still running.
I did a Dhcp4 shutdown and that worked.
--
Ticket URL: <http://bind10.isc.org/ticket/2696>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list