BIND 10 #2940: DHCPv4 server crashes when using Memfile backend and running perfdhcp
BIND 10 Development
do-not-reply at isc.org
Thu May 2 08:04:33 UTC 2013
#2940: DHCPv4 server crashes when using Memfile backend and running perfdhcp
-------------------------------------+-------------------------------------
Reporter: | Owner:
marcin | Status: new
Type: | Milestone: DHCP
defect | Outstanding Tasks
Priority: | Keywords:
medium | Sensitive: 0
Component: dhcp4 | Sub-Project: DHCP
CVSS Scoring: | Estimated Difficulty: 0
Defect Severity: | Total Hours: 0
Medium |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
I am running the following setup:
- Kea (DHCPv4) installed on Debian 7 with a single pool configured
- perfdhcp installed on the Debian 6 system directly connected to the
server system
- Memfile backend is used to handle lease assignments
Server starts successfully. I start perfdhcp on the client machine:
{{{
./perfdhcp -4 -R 65535 -r 10 -n 100 172.16.1.1
}}}
When perfdhcp is started, the server crashes immediately with the
following error log:
{{{
b10-dhcp4: /usr/include/boost/smart_ptr/shared_ptr.hpp:418:
boost::shared_ptr<T>::reference boost::shared_ptr<T>::operator*() const
[with T = isc::dhcp::ClientId; boost::shared_ptr<T>::reference =
isc::dhcp::ClientId&]: Assertion `px != 0' failed.
2013-04-30 15:14:36.026 INFO [b10-init.init/4796] BIND10_PROCESS_ENDED
process 4803 of b10-dhcp4 ended with status 6
2013-04-30 15:14:36.026 ERROR [b10-init.init/4796] BIND10_COMPONENT_FAILED
component b10-dhcp4 (pid 4803) failed: process terminated with exit status
6 (killed by signal 6: SIGABRT)
2013-04-30 15:14:41.011 INFO [b10-init.init/4796] BIND10_RECEIVED_SIGNAL
received signal SIGINT
2013-04-30 15:14:41.011 INFO [b10-init.init/4796] BIND10_SHUTDOWN
stopping the server
2013-04-30 15:14:41.024 INFO [b10-init.init/4796]
BIND10_CONFIGURATOR_STOP bind10 component configurator is shutting down
2013-04-30 15:14:41.024 INFO [b10-init.init/4796] BIND10_COMPONENT_STOP
component Socket creator is being stopped
2013-04-30 15:14:41.024 INFO [b10-init.init/4796]
BIND10_SOCKCREATOR_TERMINATE terminating socket creator
2013-04-30 15:14:41.026 INFO [b10-init.init/4796] BIND10_COMPONENT_STOP
component msgq is being stopped
2013-04-30 15:14:41.028 INFO [b10-init.init/4796] BIND10_COMPONENT_STOP
component b10-cmdctl is being stopped
2013-04-30 15:14:41.028 INFO [b10-init.init/4796] BIND10_STOP_PROCESS
asking b10-cmdctl to shut down
2013-04-30 15:14:41.030 INFO [b10-init.init/4796] BIND10_COMPONENT_STOP
component cfgmgr is being stopped
2013-04-30 15:14:41.030 INFO [b10-init.init/4796] BIND10_STOP_PROCESS
asking cfgmgr to shut down
2013-04-30 15:14:41.030 INFO [b10-init.init/4796] BIND10_COMPONENT_STOP
component b10-stats is being stopped
2013-04-30 15:14:41.030 INFO [b10-init.init/4796] BIND10_STOP_PROCESS
asking b10-stats to shut down
2013-04-30 15:14:41.031 INFO [b10-cmdctl.cmdctl/4802] CMDCTL_EXITING
exiting
2013-04-30 15:14:41.038 INFO [b10-cfgmgr.cfgmgr/4800]
CFGMGR_STOPPED_BY_COMMAND received shutdown command, shutting down
2013-04-30 15:14:41.047 INFO [b10-stats.stats/4804]
STATS_RECEIVED_SHUTDOWN_COMMAND shutdown command received
2013-04-30 15:14:41.048 INFO [b10-stats.stats/4804] STATS_EXITING exiting
2013-04-30 15:14:42.035 INFO [b10-init.init/4796] BIND10_PROCESS_ENDED
process 4797 of Socket creator ended with status 0
2013-04-30 15:14:42.035 INFO [b10-init.init/4796] BIND10_PROCESS_ENDED
process 4800 of cfgmgr ended with status 0
2013-04-30 15:14:42.036 INFO [b10-init.init/4796] BIND10_PROCESS_ENDED
process 4802 of b10-cmdctl ended with status 0
2013-04-30 15:14:42.036 INFO [b10-init.init/4796] BIND10_PROCESS_ENDED
process 4804 of b10-stats ended with status 0
2013-04-30 15:14:42.040 INFO [b10-init.init/4796] BIND10_SEND_SIGTERM
sending SIGTERM to msgq (PID 4798)
2013-04-30 15:14:42.145 INFO [b10-init.init/4796] BIND10_PROCESS_ENDED
process 4798 of msgq ended with status 0
2013-04-30 15:14:42.145 INFO [b10-init.init/4796]
BIND10_SHUTDOWN_COMPLETE all processes ended, shutdown complete
}}}
Similar issue has been discovered a few months back when using MySQL
backend. It has been reported and resolved as #2723.
--
Ticket URL: <http://bind10.isc.org/ticket/2940>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list