Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#1037297: /usr/sbin/kea-dhcp6: socket error when starting or restarting the server

91 views
Skip to first unread message

Bruno

unread,
Jun 10, 2023, 10:42:07 AM6/10/23
to
Package: kea-dhcp6-server
Version: 2.2.0-6
Severity: normal
File: /usr/sbin/kea-dhcp6
X-Debbugs-Cc: bmeir...@gmail.com

Dear Maintainer,

when starting or restarting the server, kea-dhcp6-server does not work with the following error:

kea-dhcp6-server.service - Kea IPv6 DHCP daemon
Loaded: loaded (/lib/systemd/system/kea-dhcp6-server.service; enabled; preset: enabled)
Active: active (running) since Sat 2023-06-10 10:39:38 -03; 10min ago
Docs: man:kea-dhcp6(8)
Main PID: 770 (kea-dhcp6)
Tasks: 5 (limit: 4915)
Memory: 6.1M
CPU: 306ms
CGroup: /system.slice/kea-dhcp6-server.service
└─770 /usr/sbin/kea-dhcp6 -c /etc/kea/kea-dhcp6.conf

jun 10 10:39:38 router kea-dhcp6[770]: INFO DHCPSRV_MEMFILE_DB opening memory file lease database: lfc-interval=3600 type=memfile universe=6
jun 10 10:39:38 router kea-dhcp6[770]: INFO DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file /var/lib/kea/kea-leases6.csv.2
jun 10 10:39:38 router kea-dhcp6[770]: INFO DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file /var/lib/kea/kea-leases6.csv
jun 10 10:39:38 router kea-dhcp6[770]: INFO DHCPSRV_MEMFILE_LFC_SETUP setting up the Lease File Cleanup interval to 3600 sec
jun 10 10:39:38 router kea-dhcp6[770]: INFO DHCP6_USING_SERVERID server is using server-id 00:01:00:01:2c:10:a8:b5:70:71:bc:94:33:af and stores in the file /var/lib/kea/kea-dhcp6-serverid
jun 10 10:39:38 router kea-dhcp6[770]: WARN DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: Failed to open multicast socket on interface enp1s0, reason: Failed to open link-local socket on interf>
jun 10 10:39:38 router kea-dhcp6[770]: INFO DHCP6_OPEN_SOCKETS_FAILED maximum number of open service sockets attempts: 0, has been exhausted without success
jun 10 10:39:38 router kea-dhcp6[770]: WARN DHCPSRV_NO_SOCKETS_OPEN no interface configured to listen to DHCP traffic
jun 10 10:39:38 router kea-dhcp6[770]: WARN DHCP6_MULTI_THREADING_INFO enabled: no, number of threads: 0, queue size: 0
jun 10 10:39:38 router kea-dhcp6[770]: INFO DHCP6_STARTED Kea DHCPv6 server version 2.2.0 started

If restart the service with "systemctl restart kea-dhcp6-server with "systemctl restart kea-dhcp6-server.service" it goes back to normal.
This only happens on system boot or restarting the server. Seems to start before ready interface

root@router:~# systemctl restart kea-dhcp6-server.service
root@router:~# systemctl status kea-dhcp6-server.service
● kea-dhcp6-server.service - Kea IPv6 DHCP daemon
Loaded: loaded (/lib/systemd/system/kea-dhcp6-server.service; enabled; preset: enabled)
Active: active (running) since Sat 2023-06-10 11:28:36 -03; 1s ago
Docs: man:kea-dhcp6(8)
Main PID: 1614 (kea-dhcp6)
Tasks: 5 (limit: 4915)
Memory: 1.8M
CPU: 147ms
CGroup: /system.slice/kea-dhcp6-server.service
└─1614 /usr/sbin/kea-dhcp6 -c /etc/kea/kea-dhcp6.conf

jun 10 11:28:37 router kea-dhcp6[1614]: INFO RUN_SCRIPT_LOAD Run Script hooks library has been loaded
jun 10 11:28:37 router kea-dhcp6[1614]: INFO HOOKS_LIBRARY_LOADED hooks library /usr/lib/i386-linux-gnu/kea/hooks/libdhcp_run_script.so successfully loaded
jun 10 11:28:37 router kea-dhcp6[1614]: INFO DHCP6_CONFIG_COMPLETE DHCPv6 server has completed configuration: added IPv6 subnets: 1; DDNS: disabled
jun 10 11:28:37 router kea-dhcp6[1614]: INFO DHCPSRV_MEMFILE_DB opening memory file lease database: lfc-interval=3600 type=memfile universe=6
jun 10 11:28:37 router kea-dhcp6[1614]: INFO DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file /var/lib/kea/kea-leases6.csv.2
jun 10 11:28:37 router kea-dhcp6[1614]: INFO DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file /var/lib/kea/kea-leases6.csv
jun 10 11:28:37 router kea-dhcp6[1614]: INFO DHCPSRV_MEMFILE_LFC_SETUP setting up the Lease File Cleanup interval to 3600 sec
jun 10 11:28:37 router kea-dhcp6[1614]: INFO DHCP6_USING_SERVERID server is using server-id 00:01:00:01:2c:10:a8:b5:70:71:bc:94:33:af and stores in the file /var/lib/kea/kea-dhcp6-serverid
jun 10 11:28:37 router kea-dhcp6[1614]: WARN DHCP6_MULTI_THREADING_INFO enabled: no, number of threads: 0, queue size: 0
jun 10 11:28:37 router kea-dhcp6[1614]: INFO DHCP6_STARTED Kea DHCPv6 server version 2.2.0 started

-- System Information:
Debian Release: 12.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 6.1.0-9-686-pae (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kea-dhcp6-server depends on:
ii init-system-helpers 1.65.2
ii kea-common 2.2.0-6
ii libc6 2.36-9
ii libgcc-s1 12.2.0-14
ii libstdc++6 12.2.0-14

kea-dhcp6-server recommends no packages.

Versions of packages kea-dhcp6-server suggests:
pn kea-doc <none>

-- Configuration Files:
/etc/apparmor.d/usr.sbin.kea-dhcp6 changed [not included]
/etc/kea/kea-dhcp6.conf changed [not included]

-- debconf-show failed

Paride Legovini

unread,
Jun 19, 2023, 9:00:03 AM6/19/23
to
Bruno wrote on 10/06/2023:
> Dear Maintainer,
>
> when starting or restarting the server, kea-dhcp6-server does not work with the following error:
[...]

Hello Bruno and thanks for this bug report. I think this issue falls
under the "network-online ordering" category, which is due to the fact
that the "networking is ready" or "system is online" status is not well
defined. It may me tempting to use an After=network-online.target rule
in the systemd service file, but the point defining what that target
means. For example: if a secondary network interface of a server is
down, should this prevent systemd from starting kea?

Unfortunately I don't have a solution at hand at the moment which is
guaranteed to do more good than harm.

Paride

Bruno Meirelles

unread,
Jun 19, 2023, 6:40:04 PM6/19/23
to
Hi Paride, thanks for the reply.

I checked the systemd file and it says After=network-online.target, it
still doesn't work, I need to restart the service.

Is the problem in systemd?

Who should I report to?

Thanks.

Paride Legovini

unread,
Jun 20, 2023, 7:10:04 AM6/20/23
to
Bruno Meirelles wrote on 20/06/2023:
> Hi Paride, thanks for the reply.
>
> I checked the systemd file and it says After=network-online.target, it
> still doesn't work, I need to restart the service.
>
> Is the problem in systemd?
>
> Who should I report to?

Hi,

https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ says:

---
network-online.target is a target that actively waits until the nework
is "up", where the definition of "up" is defined by the network
management software. Usually it indicates a configured, routable IP
address of some kind. Its primary purpose is to actively delay
activation of services until the network is set up.
---

so I'd say it's either systemd or ifupdown (assuming that's what you are
using).

Paride

Bruno Meirelles

unread,
Jun 22, 2023, 7:30:04 AM6/22/23
to
Hi Paride,

I asked on systemd github, see if that might help:

https://github.com/systemd/systemd/issues/28122#

Paride Legovini

unread,
Jun 22, 2023, 7:30:04 AM6/22/23
to
Bruno Meirelles wrote on 22/06/2023:
> Hi Paride,
>
> I asked on systemd github, see if that might help:
>
> https://github.com/systemd/systemd/issues/28122#

Lennart is right, this is not a systemd upstream issue. It's about the
Debian systemd package or the network management system you are using.

Paride
0 new messages