[Kea-users] Kea-dhcp-ddns not logging debug info (OPEN)

[Weisteen Per]

Hi, thanks for the suggestion. 

I'm a newbie regarding JSON syntax - does kea-dhcp-ddns.dhcp-to-d2 need its own output_options  section or could it use the same as the kea-dhcp-ddns logger ? 

./PerW


-----Original Message-----
From: Oscar Carlsson <oscar at spindel.tax> 
Sent: tirsdag 10. mai 2022 15:43
To: Weisteen Per <per.weisteen at telenor.no>
Cc: kea-users at lists.isc.org
Subject: Re: [Kea-users] Kea-dhcp-ddns not logging debug info (INTERNAL)

Hi,

There's a wealth of different loggers you can tune, when I had some issues with ddns I used kea-dhcp-ddns.dhcp-to-d2 and kea-dhcp-ddns.d2-to-dns (set to DEBUG) which was enough in that case.


https://kea.readthedocs.io/en/kea-1.6.2/arm/logging.html


Oscar

Weisteen Per <per.weisteen at telenor.no> writes:

> I'm testing DDNS an I've succeeded in doing updates. But the logs 
> created from kea-dhcp-ddns doesn't seem to be consistent.
> During testing last week I got sensible information in logs from 
> kea-dhcp-ddns but not during testing today.
>
> My logs from kea-dhcp4 regarding DNS updates tells me that updates is 
> done :
>
> 2022-05-10 14:31:16.216 DEBUG DHCP4_CLIENT_FQDN_PROCESS
> [hwtype=1
> 00:07:5f:ae:77:cb], cid=[01:00:07:5f:ae:77:cb], tid=0x3d06108f:
> processing Client FQDN option
> 2022-05-10 14:31:16.216 DEBUG DHCP4_CLIENT_FQDN_DATA [hwtype=1 
> 00:07:5f:ae:77:cb], cid=[01:00:07:5f:ae:77:cb], tid=0x3d06108f:
> Client
> sent FQDN option: type=81 (CLIENT_FQDN), flags: (N=0, E=0, O=0, S=1), 
> domain-name='tst-ra005.cctv.telenor.net.' (full)
> 2022-05-10 14:31:16.217 DEBUG DHCP4_RESPONSE_FQDN_DATA [hwtype=1 
> 00:07:5f:ae:77:cb], cid=[01:00:07:5f:ae:77:cb], tid=0x3d06108f:
> including FQDN option in the server's response: type=81 (CLIENT_FQDN),
> flags: (N=0, E=0, O=0, S=1),
> domain-name='tst-ra005.cctv.telenor.net.'
> (full)
> 2022-05-10 14:31:16.217 DEBUG DHCP4_NCR_CREATE [hwtype=1 
> 00:07:5f:ae:77:cb], cid=[01:00:07:5f:ae:77:cb], tid=0x3d06108f:
> DDNS
> updates enabled, therefore sending name change requests
>
> However kea-dhcp-ddns still doesn't seem to do anyting.
> I've enabled DEBUG logging at level 45 and restarted the daemon but 
> there is no corresponding update info in the log. The last info logged 
> is:
>
> 2022-05-10 14:03:38.179 DEBUG COMMAND_REGISTERED Command config-write 
> registered
> 2022-05-10 14:03:38.179 DEBUG COMMAND_REGISTERED Command shutdown 
> registered
> 2022-05-10 14:03:38.179 DEBUG COMMAND_REGISTERED Command status-get 
> registered
> 2022-05-10 14:03:38.179 DEBUG COMMAND_REGISTERED Command version-get 
> registered
> 2022-05-10 14:03:38.179 DEBUG COMMAND_REGISTERED Command statistic-get 
> registered
> 2022-05-10 14:03:38.179 DEBUG COMMAND_REGISTERED Command 
> statistic-get-all registered
> 2022-05-10 14:03:38.179 DEBUG COMMAND_REGISTERED Command 
> statistic-reset registered
> 2022-05-10 14:03:38.179 DEBUG COMMAND_REGISTERED Command 
> statistic-reset-all registered
> 2022-05-10 14:03:38.179 DEBUG DHCP_DDNS_QUEUE_MGR_RECONFIGURING 
> application is reconfiguring the queue manager
> 2022-05-10 14:03:38.179 DEBUG DHCP_DDNS_QUEUE_MGR_STARTED 
> application's queue manager has begun listening for requests.
>
>
> Version info:
> # kea-dhcp-ddns -V
> 2.0.1
> tarball
> linked with:
> log4cplus 1.2.0
> OpenSSL 1.1.1k  FIPS 25 Mar 2021
>
> # kea-dhcp4 -V
> 2.0.1
> tarball
> linked with:
> log4cplus 1.2.0
> OpenSSL 1.1.1k  FIPS 25 Mar 2021
> database:
> MySQL backend 12.0, library 10.5.5
> PostgreSQL backend 6.2, library 130003 Memfile backend 2.1
>
>
>
> ./PerW