Opened 7 years ago

Closed 5 years ago

#2616 closed defect (wontfix)

existing msgq has confusing error if another bind10 tries to start

Reported by: jreed Owned by: jreed
Priority: low Milestone: Remaining BIND10 tickets
Component: ~msgq (obsolete) Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

I accidently tried to start bind10 again. The existing msgq logged:

2013-01-08 10:17:36.446 ERROR [b10-msgq.msgq/3646] MSGQ_RECV_ERR Error reading from socket 9: EOF

It is a "low-level error" but this is confusing. Should existing msgq have an error?

Subtickets

Change History (4)

comment:1 Changed 7 years ago by shane

  • Milestone New Tasks deleted
  • Owner set to jreed
  • Status changed from new to assigned

This should not happen, as we have code to check for an already-running msgq when we start up:

        # Try to connect to the c-channel daemon, to see if it is already
        # running
        c_channel_env = {}
        if self.msgq_socket_file is not None:
             c_channel_env["BIND10_MSGQ_SOCKET_FILE"] = self.msgq_socket_file
        logger.debug(DBG_PROCESS, BIND10_CHECK_MSGQ_ALREADY_RUNNING)
        try:
            self.cc_session = isc.cc.Session(self.msgq_socket_file)
            logger.fatal(BIND10_MSGQ_ALREADY_RUNNING)
            return "b10-msgq already running, or socket file not cleaned , cannot start"
        except isc.cc.session.SessionError:
            # this is the case we want, where the msgq is not running
            pass

If this didn't work, that is the bug.

How exactly did you get this condition?

comment:2 Changed 7 years ago by jreed

I got it by running bind10 twice (maybe a second or two between). I reproduced:

INFO [b10-boss.boss]: BIND10_STARTING starting BIND10: bind10 20110223 (BIND 10 20121219)
DEBUG [b10-boss.boss]: BIND10_CHECK_MSGQ_ALREADY_RUNNING checking if msgq is already running
FATAL [b10-boss.boss]: BIND10_MSGQ_ALREADY_RUNNING msgq daemon already running, cannot start
FATAL [b10-boss.boss]: BIND10_STARTUP_ERROR error during startup: b10-msgq already running, or socket file not cleaned , cannot start
2013-01-30 09:22:18.807 ERROR [b10-msgq.msgq/17782] MSGQ_RECV_ERR Error reading from socket 15: EOF

Yes it gets the FATAL as expected. Also see the msgq ERROR.

Process ID 17782 is the already-running b10-msgq.

comment:3 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:4 Changed 5 years ago by tomek

  • Resolution set to wontfix
  • Status changed from assigned to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check http://bundy-dns.de.

Closing ticket.

Note: See TracTickets for help on using tickets.