Opened 9 years ago

Closed 6 years ago

#662 closed defect (wontfix)

b10-auth wrongly falls back to default listen_on

Reported by: jreed Owned by: UnAssigned
Priority: medium Milestone: DNS Outstanding Tasks
Component: b10-auth Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: Medium
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 0.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

As I noted in #657, b10-auth now falls back to default listen_on (from spec?) if the b10-config.db version fails.

[bind10] BIND 10 started
Setting listen addresses:
 0.0.0.0:53
 127.0.0.1:5300
Initialize TCP server at 0.0.0.0:53
Unable to set new address: Failed to initialize network servers: Permission denied
[b10-auth] error: Server configuration failed: Failed to initialize network servers: Permission denied
[b10-auth] Configuration channel established.
[b10-auth] Xfrin session channel created.
[b10-auth] Xfrin session channel established.
[b10-auth] Statistics session channel created.
[b10-auth] Statistics session channel established.
Setting listen addresses:
 ::1:5300
 127.0.0.1:5300
Initialize TCP server at ::1:5300
Initialize UDP server at ::1:5300
Initialize TCP server at 127.0.0.1:5300
Initialize UDP server at 127.0.0.1:5300
[b10-auth] Set statistics timer to 60 seconds
[b10-auth] Data source database file: /usr/home/jreed/opt/bind10/var/bind10-devel/zone.sqlite3
[b10-auth] Server started.

I think the previous behaviour was for it to exit. bind10 (boss) would restart and the failure would continue looping. I don't think that is good behaviour either.

But using default values when a configuration is specifically defined is not correct. It may not be noticed and it may break some policies or other software (which wanted to use those).

Maybe this will be fixed in #657, but I open this ticket just in case.

Subtickets

Change History (8)

comment:1 Changed 8 years ago by shane

  • Defect Severity set to Medium
  • Owner set to jreed
  • Status changed from new to assigned
  • Sub-Project set to DNS

I tried it with a different DNS server running on the desired ports, and we get this:

2012-02-28 10:58:32.350 ERROR [b10-boss.boss] BIND10_SOCKET_ERROR error on bind call in the creator: 98/Address already in use
2012-02-28 10:58:32.351 ERROR [b10-auth.server_common] SRVCOMM_ADDRESS_FAIL failed to listen on addresses ("Error creating socket on bind")
2012-02-28 10:58:32.356 ERROR [b10-auth.auth] AUTH_CONFIG_LOAD_FAIL load of configuration failed: Server configuration failed: "Error creating socket on bind"

This seems reasonable. Shall we resolve this ticket?

comment:2 follow-up: Changed 8 years ago by jreed

I hit this problem again. This time with b10-resolver. I had four listen_on configurations (which includes two localhost addresses). Due to configuration error (outside of BIND 10), a wrong inet6 address was configured. The socket creation/binding error was logged a few times (but didn't identify the problem, see #1946). This made me think that the next listen_on as skipped and the third and fourth entries were used. Now I realize all were skipped on the first's failure. Just the default configuration was used.

The default configuration should not be used. If we do decide to use default configuration for some things, it needs to be clearly logged.

Maybe this ticket is related to #1707?

comment:3 in reply to: ↑ 2 Changed 8 years ago by jinmei

Replying to jreed:

The default configuration should not be used. If we do decide to use default configuration for some things, it needs to be clearly logged.

Maybe this ticket is related to #1707?

It looks like so.

comment:4 Changed 8 years ago by jreed

  • Owner changed from jreed to UnAssigned

comment:5 Changed 6 years ago by shane

  • Milestone set to Sprint-20131015
  • Summary changed from b10-auth wrongly falls back to default listen_on to [kean] b10-auth wrongly falls back to default listen_on

This behavior may be from before we had the socket creator. That would have changed this code path. We need to verify that this is still a problem.

comment:6 Changed 6 years ago by kean

  • Summary changed from [kean] b10-auth wrongly falls back to default listen_on to b10-auth wrongly falls back to default listen_on

comment:7 Changed 6 years ago by stephen

  • Milestone changed from bind10-1.2-release-freeze to DNS Outstanding Tasks

comment:8 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from assigned to closed

DNS and BIND10 framework is outside of scope for Kea project.
The corresponding code has been removed from Kea git repository.
If you want to follow up on DNS or former BIND10 issues, see
http://bundy-dns.de project.

Closing ticket.

Note: See TracTickets for help on using tickets.