Send kea-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."
Today's Topics:
1. [0.9.1-beta] Kea startup and logging (Chaigneau, Nicolas)
2. [0.9.1-beta1] Issue with config reload and IPv4 sockets
(Chaigneau, Nicolas)
----------------------------------------------------------------------
Message: 1
Date: Mon, 23 Feb 2015 15:28:12 +0000
From: "Chaigneau, Nicolas" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [kea-dev] [0.9.1-beta] Kea startup and logging
Message-ID:
<ab94b0b675bdf14189cd5a861db36c84194ee...@de-cm-mbx06.corp.capgemini.com>
Content-Type: text/plain; charset="us-ascii"
Hello,
I have a few questions and comments about Kea startup and logging:
1)
I'm starting a kea-dhcp4 server configured with logging to a file.
Upon starting, the server outputs the following to console:
2015-02-23 15:50:48.346 INFO [kea-dhcp4.dhcp4/17854] DHCP4_STARTING
Kea DHCPv4 server version 0.9.1-beta starting
2015-02-23 15:50:48.348 INFO [kea-dhcp4.dhcpsrv/17854]
DHCPSRV_CFGMGR_USE_ADDRESS listening on address 10.163.216.230, on interface
eth0.102
2015-02-23 15:50:48.348 INFO [kea-dhcp4.dhcpsrv/17854]
DHCPSRV_CFGMGR_SOCKET_TYPE_SELECT using socket type udp
2015-02-23 15:50:48.348 INFO [kea-dhcp4.dhcpsrv/17854]
DHCPSRV_MEMFILE_DB opening memory file lease database: lfc-interval=60
name=/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv persist=true
type=memfile universe=4
(...)
2015-02-23 15:50:48.351 INFO [kea-dhcp4.dhcp4/17854]
DHCP4_CONFIG_COMPLETE DHCPv4 server has completed configuration: added IPv4
subnets: 1; DDNS: disabled
Nothing at all is written in the log file.
I suppose this is because the log facility must be initialized before anything
can be written to the log file ?
In any case, it would be nice to have at least one line in the file such as:
2015-02-23 15:50:48.346 INFO [kea-dhcp4.dhcp4/17854] DHCP4_STARTED Kea
DHCPv4 server version 0.9.1-beta started
So we can know from the log that the server has been really started and when
exactly.
2)
When being started in non-debug mode, the process kea-dhcp4 does not daemonize
itself (I have to terminate the command line with a '&').
Is that normal ?
3)
Each time kea-lfc is executed, we have:
- the following messages in Kea's log file:
2015-02-23 16:18:53.891 INFO [kea-dhcp4.dhcpsrv/17947]
DHCPSRV_MEMFILE_LFC_START starting Lease File Cleanup
2015-02-23 16:18:53.892 INFO [kea-dhcp4.dhcpsrv/17947]
DHCPSRV_MEMFILE_LFC_EXECUTE executing Lease File Cleanup using:
/opt/application/mwpdhcp/products/kea/0.9.1-beta-c2/sbin/kea-lfc -4 -x
/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.2 -i
/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.1 -o
/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.output -f
/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.completed -p
/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.pid -c ignored-path
- but also the following on the console from which the kea-dhcp4 process was
started:
/opt/application/mwpdhcp/products/kea/0.9.1-beta-c2/sbin/kea-lfc -4 -x
/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.2 -i
/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.1 -o
/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.output -f
/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.completed -p
/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.pid -c ignored-path
I think the redundant console output should be removed.
Regards,
Nicolas.
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
------------------------------
Message: 2
Date: Mon, 23 Feb 2015 15:34:21 +0000
From: "Chaigneau, Nicolas" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [kea-dev] [0.9.1-beta1] Issue with config reload and IPv4
sockets
Message-ID:
<ab94b0b675bdf14189cd5a861db36c84194ef...@de-cm-mbx06.corp.capgemini.com>
Content-Type: text/plain; charset="us-ascii"
Hello,
When attempting to reload Kea configuration through a HUP signal, for example
with:
kill -HUP $(pidof kea-dhcp4)
The log file shows the following errors:
2015-02-23 16:29:08.944 INFO [kea-dhcp4.dhcp4/17947]
DHCP4_DYNAMIC_RECONFIGURATION initiate server reconfiguration using file:
/mnt/wifi/users/NCH/src-owa/src-kea-qualif/etc/kea1.conf, after receiving
SIGHUP signal
2015-02-23 16:29:08.945 INFO [kea-dhcp4.dhcpsrv/17947]
DHCPSRV_CFGMGR_USE_ADDRESS listening on address 10.163.216.230, on interface
eth0.102
2015-02-23 16:29:08.945 INFO [kea-dhcp4.dhcpsrv/17947]
DHCPSRV_CFGMGR_SOCKET_TYPE_SELECT using socket type udp
2015-02-23 16:29:08.945 INFO [kea-dhcp4.dhcpsrv/17947]
DHCPSRV_MEMFILE_DB opening memory file lease database: lfc-interval=60
name=/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv persist=true
type=memfile universe=4
2015-02-23 16:29:08.946 INFO [kea-dhcp4.dhcpsrv/17947]
DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file
/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv.2
2015-02-23 16:29:08.946 INFO [kea-dhcp4.dhcpsrv/17947]
DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file
/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv
2015-02-23 16:29:08.946 INFO [kea-dhcp4.dhcpsrv/17947]
DHCPSRV_MEMFILE_LFC_SETUP setting up the Lease File Cleanup interval to 60 sec
2015-02-23 16:29:08.946 INFO [kea-dhcp4.dhcp4/17947]
DHCP4_CONFIG_NEW_SUBNET a new subnet has been added to configuration:
10.164.0.0/15 with params: t1=900, t2=1575, valid-lifetime=1800
2015-02-23 16:29:08.946 INFO [kea-dhcp4.dhcp4/17947]
DHCP4_CONFIG_COMPLETE DHCPv4 server has completed configuration: added IPv4
subnets: 1; DDNS: disabled
2015-02-23 16:29:08.946 ERROR [kea-dhcp4.dhcp4/17947]
DHCP4_CONFIG_LOAD_FAIL configuration error using file:
/mnt/wifi/users/NCH/src-owa/src-kea-qualif/etc/kea1.conf, reason: Error while
processing command 'config-reload':it is not allowed to set new packet filter
when there are open IPv4 sockets - need to close them first, params: '{
"hooks-libraries": [
"/mnt/wifi/users/NCH/src-owa/src-kea-qualif/hooks/libdhcp_nch_hook.so" ],
"interfaces-config": { "dhcp-socket-type": "udp", "interfaces": [
"eth0.102/10.163.216.230" ] }, "lease-database": { "lfc-interval": 60, "name":
"/var/opt/data/flat/mwpdhcp/ramdisk1/kea1-leases4.csv", "persist": true,
"type": "memfile" }, "rebind-timer": 1575, "renew-timer": 900, "subnet4": [ {
"id": 1001, "pools": [ { "pool": "10.164.0.2 - 10.165.255.254" } ], "relay": {
"ip-address": "10.163.216.250" }, "subnet": "10.164.0.0/15" } ],
"valid-lifetime": 1800 }'
2015-02-23 16:29:08.946 ERROR [kea-dhcp4.dhcp4/17947]
DHCP4_DYNAMIC_RECONFIGURATION_FAIL dynamic server reconfiguration failed with
file: /mnt/wifi/users/NCH/src-owa/src-kea-qualif/etc/kea1.conf
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
------------------------------
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
End of kea-dev Digest, Vol 11, Issue 6
**************************************
