<div style="font-family: Arial, sans-serif; font-size: 14px;">Hello,</div><div style="font-family: Arial, sans-serif; font-size: 14px;"><br></div><div style="font-family: Arial, sans-serif; font-size: 14px;">After upgrading from 3.0.3 to 3.2.0 I started seeing the following warning in my logs:</div><div style="font-family: Arial, sans-serif; font-size: 14px;"><br></div><div style="font-family: Arial, sans-serif; font-size: 14px;"><span></span><span>Jun 24 22:40:21 dns01.redacted.net kea-dhcp4[769057]: WARN  DHCP_RECEIVE4_UNKNOWN Received data over unknown socket</span><div><span>Jun 24 22:40:21 dns01.redacted.net kea-dhcp4[769057]: WARN  DHCP_RECEIVE4_UNKNOWN Received data over unknown socket</span></div><div><span>Jun 24 22:40:31 dns01.redacted.net kea-dhcp4[769057]: WARN  DHCP_RECEIVE4_UNKNOWN Received data over unknown socket</span></div><div><span>Jun 24 22:40:38 dns01.redacted.net kea-dhcp4[769057]: WARN  DHCP_RECEIVE4_UNKNOWN Received data over unknown socket</span></div><div><span>Jun 24 22:40:41 dns01.redacted.net kea-dhcp4[769057]: WARN  DHCP_RECEIVE4_UNKNOWN Received data over unknown socket</span></div><div><span>Jun 24 22:40:50 dns01.redacted.net kea-dhcp4[769057]: WARN  DHCP_RECEIVE4_UNKNOWN Received data over unknown socket</span></div><div><span>Jun 24 22:40:50 dns01.redacted.net kea-dhcp4[769057]: WARN  DHCP_RECEIVE4_UNKNOWN Received data over unknown socket</span></div><div><span>Jun 24 22:40:50 dns01.redacted.net kea-dhcp4[769057]: WARN  DHCP_RECEIVE4_UNKNOWN Received data over unknown socket</span></div><div><span>Jun 24 22:40:51 dns01.redacted.net kea-dhcp4[769057]: WARN  DHCP_RECEIVE4_UNKNOWN Received data over unknown socket</span></div><span>Jun 24 22:41:01 dns01.redacted.net kea-dhcp4[769057]: WARN  DHCP_RECEIVE4_UNKNOWN Received data over unknown socket</span><div><span>...</span></div><div><span><br></span></div><div>It appears that the warning is triggered by the Stork Agent connection.  The "control-sockets",  "loggers" and the Stork Agent configurations did not change between versions:</div><div><br></div><div><span>...</span><div><span>    "control-sockets": [</span></div><div><span>      {</span></div><div><span>        "socket-type": "http",</span></div><div><span>        "socket-address": "127.0.0.1",</span></div><div><span>        "socket-port": 8000,</span></div><div><span>        "authentication": {</span></div><div><span>          "type": "basic",</span></div><div><span>          "realm": "kea-dhcpv4-server",</span></div><div><span>          "directory": "/etc/kea/auth",</span></div><div><span>          "clients": [</span></div><div><span>            {</span></div><div><span>              "user-file": "stork-agent.user",</span></div><div><span>              "password-file": "stork-agent.passwd"</span></div><div><span>            }</span></div><div><span>          ]</span></div><div><span>        }</span></div><div><span>      },</span></div><span>...</span></div><div><br></div><div><span></span><div><span>    "loggers": [</span></div><div><span>      { "name": "kea-dhcp4",</span></div><div><span>        "severity": "WARN",</span></div><div><span>        "debuglevel": 0,</span></div><div><span>        "output-options": [ { "output": "stdout", "pattern": "%-5p %m\n" } ]</span></div><div><span>      },</span></div><div><span>      {</span></div><div><span>        "name": "kea-dhcp4.bad-packets",</span></div><div><span>        "severity": "INFO",</span></div><div><span>        "output-options": [</span></div><div><span>          {</span></div><div><span>            "output": "/var/log/kea/kea-dhcp4.bad-packets.log",</span></div><div><span>            "pattern": "%D{%Y-%m-%d %H:%M:%S.%q} %-5p %m\n",</span></div><div><span>            "maxsize": 10240000,</span></div><div><span>            "maxver": 5</span></div><div><span>          }</span></div><div><span>...</span></div><div><br></div><div>The only way I was able to silence the warning while keeping the "kea-dhcp4" in WARN was to add the following to loggers:</div><div><br></div><div><span>      {</span></div><div><span>        "name": "dhcp",</span></div><div><span>        "severity": "ERROR"</span></div><div><span>      },</span></div><span></span><br></div><div>Is this "new" behaviour expected or is there something else amiss in my configuration for v3.2.0?</div><div><br></div><div>Thanks,<br>Mathieu.</div><div><br></div><div><br></div><span></span><br></div>
<div style="font-family: Arial, sans-serif; font-size: 14px;" class="protonmail_signature_block protonmail_signature_block-empty">
    <div class="protonmail_signature_block-user protonmail_signature_block-empty"></div>
    
            <div class="protonmail_signature_block-proton protonmail_signature_block-empty">
        
            </div>
</div>