Devuan bug report logs - #848
Pd: Problems starting kea-dhcp4-server

Package: kea-dhcp4-server; Maintainer for kea-dhcp4-server is (unknown); Source for kea-dhcp4-server is src:isc-kea.

Reported by: Jerzy Sobczyk <Jerzy.Sobczyk@pw.edu.pl>

Date: Wed, 24 Apr 2024 18:32:02 UTC

Severity: normal

Tags: debian

Found in version 2.2.0-6

Fixed in version 2.4.1-3

Done: Mark Hindley <mark@hindley.org.uk>

Forwarded to https://bugs.debian.org/1055438

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.devuan.org
Subject: bug#848: Pd: Problems starting kea-dhcp4-server
Reply-To: Jerzy Sobczyk <Jerzy.Sobczyk@pw.edu.pl>, 848@bugs.devuan.org
Resent-From: Jerzy Sobczyk <Jerzy.Sobczyk@pw.edu.pl>
Resent-To: devuan-bugs@lists.dyne.org
Resent-CC: devuan-dev@lists.dyne.org
X-Loop: owner@bugs.devuan.org
Resent-Date: Wed, 24 Apr 2024 18:32:02 +0000
Resent-Message-ID: <handler.848.B.171398349717957@bugs.devuan.org>
Resent-Sender: owner@bugs.devuan.org
X-Devuan-PR-Message: report 848
X-Devuan-PR-Package: kea-dhcp4-server
X-Devuan-PR-Keywords: 
Received: via spool by submit@bugs.devuan.org id=B.171398349717957
          (code B); Wed, 24 Apr 2024 18:32:02 +0000
Received: (at submit) by bugs.devuan.org; 24 Apr 2024 18:31:37 +0000
Delivered-To: bugs@devuan.org
Received: from email.devuan.org [2a01:4f9:fff1:13::5fd9:f9e4]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 24 Apr 2024 18:31:36 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id dXrfCwdQKWbEBAAAmSBk0A
	(envelope-from <jerzy.sobczyk@pw.edu.pl>)
	for <bugs@devuan.org>; Wed, 24 Apr 2024 18:31:35 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 1B8B9408; Wed, 24 Apr 2024 18:31:35 +0000 (UTC)
Authentication-Results: email.devuan.org;
	dkim=pass (2048-bit key; unprotected) header.d=pw.edu.pl header.i=@pw.edu.pl header.a=rsa-sha256 header.s=pw_2021 header.b=XIDKpSq6;
	dkim-atps=neutral
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,HTML_MESSAGE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham
	autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=194.29.130.59; helo=prox-mg-02.pw.edu.pl; envelope-from=jerzy.sobczyk@pw.edu.pl; receiver=<UNKNOWN> 
Received: from prox-mg-02.pw.edu.pl (prox-mg-02.pw.edu.pl [194.29.130.59])
	by email.devuan.org (Postfix) with ESMTPS id 9575421D
	for <submit@bugs.devuan.org>; Wed, 24 Apr 2024 18:31:30 +0000 (UTC)
Received: from prox-mg-02.pw.edu.pl (localhost.localdomain [127.0.0.1])
	by prox-mg-02.pw.edu.pl (Proxmox) with ESMTP id 75019227DD
	for <submit@bugs.devuan.org>; Wed, 24 Apr 2024 20:31:29 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; d=pw.edu.pl; s=pw_2021; c=relaxed/relaxed;
	t=1713983487; h=from:subject:to:date:message-id;
	bh=rdzXuKZm9CmXv8pX54eRhbAxRCyNCnQWSxJnKp1ME5M=;
	b=XIDKpSq6ohNCeLu9PoYn9LuYNfYVZtSvyloi52XnJhGxwRckb7vl8WuW1zkkcLqSk/W8xIGK4wi
	6CGDv+87cWf/dqVqPg4EG986D9SGfk7Cal5y+HeXdB3JciymgB9b3eyR5c9N8Csj7z253ozA6l7yk
	pKDlFcbUv40QtQyYQ1gOCGWK9EYmB369Misy08UBj5rmuhJY1JvdQccDhhbk68wjvsUjLMfKY2Dnl
	rqEHtcoNfajfA/QGU70qMyP3y3jvboontePMM+cY+nMmyqPY3sNHQ2gVdi3EHnLrwSCMZlc8vG6rl
	aY001GgphiWnTDmtNftkAaLmfezISJB80aOQ==
Date: Wed, 24 Apr 2024 20:31:16 +0200
From: Jerzy Sobczyk <Jerzy.Sobczyk@pw.edu.pl>
To: <submit@bugs.devuan.org>
Message-ID: <bb5fac12-a1fe-412c-bb18-3d78b12fe5de@pw.edu.pl>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_5_50427516.1713983477002"
X-Correlation-ID: <bb5fac12-a1fe-412c-bb18-3d78b12fe5de@pw.edu.pl>
X-Originating-IP: [192.168.129.243]
X-ClientProxiedBy: ex1.wut.pl (192.168.129.171) To ex4.wut.pl
 (192.168.129.174)

[Message part 1 (text/plain, inline)]

Package: kea-dhcp4-server
Version: 2.2.0-6
1.After clean installation using:
    apt update
    apt install kea-dhcp4-server
necessary directories: /var/log/kea, /var/lib/kea, /var/run/kea were missing (they were left to be created by systemd ???).
So I had to create them manually.

2. There was also a problem with apparmor - I had to change the file /etc/apparmor.d/usr.sbin.kea-dhcp4 adding:
  /var/log/kea/** rwk,
  /run/kea/logger_lockfile wrk,
  /run/kea/kea4-ctrl-socket wrk,
  /run/kea/kea4-ctrl-socket.lock wrk,
and commenting out:
   owner /run/lock/kea/logger_lockfile rwk,
   owner /var/run/kea/logger_lockfile rwk,
Maybe You will be able to achieve the goal in a better way, but it works for me!

3. There was also a problem with start/stop script: /etc/init.d/kea-dhcp4-server
originally it could start the daemon but was unable to stop it.
After replacing: 
           --name $NAME
with:
          --exec $DAEMON
in two locations, it stops it (although sometimes with long delay).

After all this changes the daemon seems to be working - dhclient from other machine is able to get IP assignment.
I hope this information will help managing the package.

With Best Regards,
    Jerzy Sobczyk

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.

Devuan bug report logs - #848 Pd: Problems starting kea-dhcp4-server

Devuan bug report logs - #848
Pd: Problems starting kea-dhcp4-server