BIND 10 #456: [kean] noisy exception when msgq session times out
BIND 10 Development
do-not-reply at isc.org
Mon Oct 28 07:41:04 UTC 2013
#456: [kean] noisy exception when msgq session times out
-------------------------------------+-------------------------------------
Reporter: jreed | Owner: jreed
Type: defect | Status:
Priority: medium | assigned
Component: msgq | Milestone:
Keywords: | Sprint-20131015
Sensitive: 0 | Resolution:
Sub-Project: Core | CVSS Scoring:
Estimated Difficulty: 0.0 | Defect Severity: N/A
Total Hours: 0 | Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by kean):
* owner: kean => jreed
* status: accepted => assigned
Comment:
This bug was filed a very long time ago. This is the output I now get when
trying to start bind10 with it still running:
{{{
../sbin/bind10
INFO [b10-init.init]: BIND10_STARTING starting BIND10: bind10 20110223
(BIND 10 20130529)
DEBUG [b10-init.init]: BIND10_CHECK_MSGQ_ALREADY_RUNNING checking if msgq
is already running
DEBUG [b10-init.pycc]: PYCC_LNAME_RECEIVED received local name:
526e12d9_a at hyperion
FATAL [b10-init.init]: BIND10_MSGQ_ALREADY_RUNNING msgq daemon already
running, cannot start
FATAL [b10-init.init]: BIND10_STARTUP_ERROR error during startup: b10-msgq
already running, or socket file not cleaned , cannot start
}}}
So I cannot seem to reproduce the error as reported. Not sure what state
to move the ticket to so I will reassign to jreed to verify he can still
repeat the original problem and if so, ask him to provide the commands
used to do so.
--
Ticket URL: <http://bind10.isc.org/ticket/456#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list