BIND 10 #3051: DHCP4 logfiles output from Kea display parameter mismatch errors

BIND 10 Development do-not-reply at isc.org
Thu Jul 11 15:53:32 UTC 2013


#3051: DHCP4 logfiles output from Kea display parameter mismatch errors
-------------------------------------+-------------------------------------
            Reporter:  jwright       |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  New
           Component:  Unclassified  |  Tasks
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Description changed by stephen:

Old description:

> BIND10 version: (BIND 10 20130529).
>
> When running ANVL tests for Section 2: "Introduction, Design Goals and
> Protocol Summary," I get the following messages in the dhcp4 component
> logfile:
>
> @@Excess logger placeholders still exist@@
>
> Logging for this components is configured as follows:
>
> # Set up logging for DHCP4 component
> > config add Logging/loggers
> > config set Logging/loggers[2]/name dhcp4
> > config set Logging/loggers[2]/severity DEBUG
> > config set Logging/loggers[2]/debuglevel 99
> > config add Logging/loggers[2]/output_options
> > config set Logging/loggers[2]/output_options[0]/destination file
> > config set Logging/loggers[2]/output_options[0]/output /home/test/var
> /test-anvl/dhcp4.log
> > config set Logging/loggers[2]/output_options[0]/maxsize 20040800
> > config set Logging/loggers[2]/output_options[0]/maxver 8
> > config commit
>
> Stephen had a quick look at the code and said the mismatch has to do with
> the file dhcp4_srv.cc:
>
> % DHCP4_QUERY_DATA received packet type %1, data is <%2>
> A debug message listing the data received from the client.
> LOG_DEBUG(dhcp4_logger, DBG_DHCP4_DETAIL_DATA, DHCP4_QUERY_DATA)
>                       .arg(query->toText());

New description:

 BIND10 version: (BIND 10 20130529).

 When running ANVL tests for Section 2: "Introduction, Design Goals and
 Protocol Summary," I get the following messages in the dhcp4 component
 logfile:

 2013-07-10 16:56:46.280 DEBUG [b10-dhcp4.dhcp4/10666] DHCP4_QUERY_DATA
 received packet type localAddr=255.255.255.255:67 remoteAddr=0.0.0.0:68,
 msgtype=1, transid=0x563db4e6
   type=53, len=1:
 , data is <%2> @@Excess logger placeholders still exist@@

 (several times) and ...

 2013-07-10 16:56:46.285 DEBUG [b10-dhcp4.dhcp4/10666]
 DHCP4_RELEASE_FAIL_NO_LEASE client (client-id hwtype=1 02:02:00:00:00:06)
 tried to release address 0.0.0.0, but there is no lease for such address.
 @@Missing placeholder %3 for '(no client-id)'@@


 Stephen had a quick look at the code and said the problem is that the
 number of placeholders in the message definitions do not match the number
 of arguments provided in the relevant LOG_XXX statement. Both messages are
 logged in src/bin/dhcp4/dhcp4_srv.cc

--

-- 
Ticket URL: <http://bind10.isc.org/ticket/3051#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list