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. Loggers and immediate flush (Chaigneau, Nicolas)
2. Re: [0.9.1-beta] Kea startup and logging (Stephen Morris)
3. Re: [0.9.1-beta] Kea startup and logging (Chaigneau, Nicolas)
----------------------------------------------------------------------
Message: 1
Date: Wed, 11 Mar 2015 14:35:50 +0000
From: "Chaigneau, Nicolas" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [kea-dev] Loggers and immediate flush
Message-ID:
<ab94b0b675bdf14189cd5a861db36c8419505...@de-cm-mbx26.corp.capgemini.com>
Content-Type: text/plain; charset="us-ascii"
Hello,
I have a suggestion concerning Kea logging implementation.
>From what I understand, options for log4cplus are handled in OutputOption.
These options contain a member "flush", which is used to set the following
property of log4cplus FileAppender:
ImmediateFlush
When it is set true, output stream will be flushed after each appended
event.
But it is always set to true.
I would like to be able to set this parameter for a given logger through Kea
configuration file.
Why we need this:
We're using a dedicated logger to log each DHCP packet received, and I've
noticed:
- first, this has a significant impact on Kea performances (which is expected)
- but this can be alleviated by disabling "ImmediateFlush" (I tested this by
forcing "flush" to false in OutputOption constructor).
Preliminary benchmark tests show that doing so results in a performance gain of
about 15-20%, which is significant.
I'll open a ticket to track this.
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: Wed, 11 Mar 2015 16:19:47 +0000
From: Stephen Morris <[email protected]>
To: [email protected]
Subject: Re: [kea-dev] [0.9.1-beta] Kea startup and logging
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
Nicolas
All good points. I've created tickets #3755, #3756 and #3757 for these.
Stephen
On 23/02/15 15:28, Chaigneau, Nicolas wrote:
>
> 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.
>
> _______________________________________________
> kea-dev mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/kea-dev
>
------------------------------
Message: 3
Date: Wed, 11 Mar 2015 16:35:57 +0000
From: "Chaigneau, Nicolas" <[email protected]>
To: Stephen Morris <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [kea-dev] [0.9.1-beta] Kea startup and logging
Message-ID:
<ab94b0b675bdf14189cd5a861db36c8419505...@de-cm-mbx26.corp.capgemini.com>
Content-Type: text/plain; charset="iso-8859-1"
Thanks Stephen.
We've been opening the same tickets at the same time though :)
3756 is 3754.
3757 is 3753.
(3755 is new)
-----Message d'origine-----
De?: [email protected] [mailto:[email protected]] De la
part de Stephen Morris
Envoy??: mercredi 11 mars 2015 17:20
??: [email protected]
Objet?: Re: [kea-dev] [0.9.1-beta] Kea startup and logging
Nicolas
All good points. I've created tickets #3755, #3756 and #3757 for these.
Stephen
On 23/02/15 15:28, Chaigneau, Nicolas wrote:
>
> 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.
>
> _______________________________________________
> kea-dev mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/kea-dev
>
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
------------------------------
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
End of kea-dev Digest, Vol 12, Issue 3
**************************************
