[Kea-users] KEA stops responding to requests after a time

Jan Sielemann jan.sielemann at jsiit.info
Mon May 6 19:46:07 UTC 2019


Hello folks,

my current problem is, that KEA stops responding to requests after a time.

The logs are set to debug (level 5), but don't show up anything
interesting (maybe I wasn't successful in setting debugging correctly).

This behaviour causes some my clients to lose network-connectivity after
a time.

After I do a keactrl reload, the server suddenly starts to throw with
leases and everything works.

I didn't figure out yet, what's going on...maybe someone has an idea.
Also hints to make the config better are appreciated!

Regards,

Jan


some configs and logs:

-----------------------------------

dc /etc/kea # cat kea-dhcp4.conf
{
"Dhcp4": {
    "interfaces-config": { "interfaces": [ "net0p0", "net0p1" ] },
    "control-socket": {
        "socket-type": "unix",
        "socket-name": "/tmp/kea-dhcp4-ctrl.sock"
    },

    "lease-database": {
        // "type": "memfile",
        // "lfc-interval": 3600
        "type": "mysql",
        "name": "kea",
        "user": "kea",
        "password": "yJXvL0G3qH9W9Xydu26n",
        "host": "localhost",
        "port": 3306
    },

    "hosts-database":
{                                                                                                                                                                                             

        "type":
"mysql",                                                                                                                                                                                            

        "name": "kea",
        "user": "kea",
        "password": "yJXvL0G3qH9W9Xydu26n",
        "host": "localhost",
        "port": 3306
    },
    "expired-leases-processing": {
        "reclaim-timer-wait-time": 10,
        "flush-reclaimed-timer-wait-time": 25,
        "hold-reclaimed-time": 3600,
        "max-reclaim-leases": 100,
        "max-reclaim-time": 250,
        "unwarned-reclaim-cycles": 5
    },

    "renew-timer": 900,
    "rebind-timer": 1800,
    "valid-lifetime": 3600,

    "option-data": [
        { "name": "domain-name-servers", "data": "192.168.2.1" },
        { "name": "domain-search", "data": "lwlvl.lan" },
        { "name": "default-ip-ttl", "data": "0xf0" }
    ],

    "subnet4": [
        {
                        "id": 1001,
            "subnet": "192.168.2.0/24",
            "pools": [ { "pool": "192.168.2.100 - 192.168.2.200" } ],
            "option-data": [ { "name": "routers", "data": "192.168.2.1" } ]
        }
    ]
},

"Logging":
{
  "loggers": [
    {
        "name": "kea-dhcp4",
        "output_options": [
            {
                "output": "/var/log/kea-dhcp4.log",
                "flush": true,
                "maxsize": 1048576,
                "maxver": 8
            }
        ],
        "severity": "DEBUG",
        "debuglevel": 5
    }
  ]
}
}

------------------------

2019-05-06 21:20:12.475 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 b8:27:eb:28:58:06],
cid=[ff:eb:28:58:06:00:01:00:01:c7:92:bc:9d:b8:27:eb:28:58:06],
tid=0x1a8686bb: lease 192.168.2.31 has been allocated
2019-05-06 21:22:30.980 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 b8:27:eb:b2:5a:01],
cid=[ff:eb:b2:5a:01:00:01:00:01:c7:92:bc:9d:b8:27:eb:28:58:06],
tid=0x6f82187d: lease 192.168.2.30 has been allocated
2019-05-06 21:35:12.561 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 b8:27:eb:28:58:06],
cid=[ff:eb:28:58:06:00:01:00:01:c7:92:bc:9d:b8:27:eb:28:58:06],
tid=0x520232be: lease 192.168.2.31 has been allocated
2019-05-06 21:35:12.682 INFO  [kea-dhcp4.dhcp4/11297]
DHCP4_DYNAMIC_RECONFIGURATION initiate server reconfiguration using
file: /etc/kea/kea-dhcp4.conf, after receiving SIGHUP
signal                             
2019-05-06 21:35:12.682 INFO  [kea-dhcp4.hosts/11297]
HOSTS_BACKENDS_REGISTERED the following host backend types are
available:
mysql                                                                              

2019-05-06 21:35:12.694 INFO  [kea-dhcp4.dhcpsrv/11297]
DHCPSRV_CFGMGR_ADD_IFACE listening on interface
net0p0                                                                                                     

2019-05-06 21:35:12.694 INFO  [kea-dhcp4.dhcpsrv/11297]
DHCPSRV_CFGMGR_ADD_IFACE listening on interface
net0p1                                                                                                     

2019-05-06 21:35:12.694 INFO  [kea-dhcp4.dhcpsrv/11297]
DHCPSRV_CFGMGR_SOCKET_TYPE_DEFAULT "dhcp-socket-type" not specified ,
using default socket type
raw                                                        
2019-05-06 21:35:12.694 INFO  [kea-dhcp4.dhcpsrv/11297]
DHCPSRV_CFGMGR_NEW_SUBNET4 a new subnet has been added to configuration:
192.168.2.0/24 with params: t1=900, t2=1800,
valid-lifetime=3600                  
2019-05-06 21:35:12.695 INFO  [kea-dhcp4.dhcp4/11297]
DHCP4_CONFIG_COMPLETE DHCPv4 server has completed configuration: added
IPv4 subnets: 1; DDNS:
disabled                                                       
2019-05-06 21:35:12.695 INFO  [kea-dhcp4.dhcpsrv/11297] DHCPSRV_MYSQL_DB
opening MySQL lease database: host=localhost name=kea password=*****
port=3306 type=mysql universe=4 user=kea                             
2019-05-06 21:35:12.705 INFO  [kea-dhcp4.hosts/11297]
DHCPSRV_MYSQL_HOST_DB opening MySQL hosts database: host=localhost
name=kea password=***** port=3306 type=mysql universe=4
user=kea                          
2019-05-06 21:35:12.848 INFO  [kea-dhcp4.leases/11297]
DHCP4_LEASE_ADVERT [hwtype=1 48:ee:0c:f1:5a:aa],
cid=[01:48:ee:0c:f1:5a:aa], tid=0x2e84b383: lease 192.168.2.9 will be
advertised                           
2019-05-06 21:35:12.851 INFO  [kea-dhcp4.leases/11297]
DHCP4_LEASE_ADVERT [hwtype=1 6c:19:8f:ed:37:fd],
cid=[01:6c:19:8f:ed:37:fd], tid=0x69773b2d: lease 192.168.2.8 will be
advertised                           
2019-05-06 21:35:12.855 INFO  [kea-dhcp4.leases/11297]
DHCP4_LEASE_ADVERT [hwtype=1 00:1b:fe:04:1d:c6],
cid=[01:00:1b:fe:04:1d:c6], tid=0xabe67545: lease 192.168.2.50 will be
advertised                          
2019-05-06 21:35:12.907 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 48:ee:0c:f1:5a:aa], cid=[01:48:ee:0c:f1:5a:aa],
tid=0x2e84b383: lease 192.168.2.9 has been
allocated                            
2019-05-06 21:35:13.041 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 6c:19:8f:ed:37:fd], cid=[01:6c:19:8f:ed:37:fd],
tid=0x69773b2d: lease 192.168.2.8 has been
allocated                            
2019-05-06 21:35:13.085 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 00:1b:fe:04:1d:c6], cid=[01:00:1b:fe:04:1d:c6],
tid=0xabe67545: lease 192.168.2.50 has been
allocated                           
2019-05-06 21:35:13.737 INFO  [kea-dhcp4.leases/11297]
DHCP4_LEASE_ADVERT [hwtype=1 4c:9e:ff:7f:28:bc],
cid=[01:4c:9e:ff:7f:28:bc], tid=0x873b: lease 192.168.2.2 will be
advertised                               
2019-05-06 21:35:13.833 INFO  [kea-dhcp4.leases/11297]
DHCP4_LEASE_ADVERT [hwtype=1 b0:c5:54:08:16:0a],
cid=[01:b0:c5:54:08:16:0a], tid=0xdd575a7d: lease 192.168.2.51 will be
advertised                          
2019-05-06 21:35:13.924 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 b0:c5:54:08:16:0a], cid=[01:b0:c5:54:08:16:0a],
tid=0xdd575a7d: lease 192.168.2.51 has been
allocated                           
2019-05-06 21:35:14.537 INFO  [kea-dhcp4.leases/11297]
DHCP4_LEASE_ADVERT [hwtype=1 7c:2f:80:9d:bd:ca], cid=[no info],
tid=0x241a1a94: lease 192.168.2.22 will be advertised
2019-05-06 21:35:14.597 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 7c:2f:80:9d:bd:ca], cid=[no info], tid=0x241a1a94: lease
192.168.2.22 has been allocated
2019-05-06 21:35:17.832 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 4c:9e:ff:7f:28:bc], cid=[01:4c:9e:ff:7f:28:bc], tid=0x96db:
lease 192.168.2.2 has been allocated
2019-05-06 21:35:22.325 INFO  [kea-dhcp4.leases/11297]
DHCP4_LEASE_ADVERT [hwtype=1 00:0b:82:d0:b7:e1],
cid=[01:00:0b:82:d0:b7:e1], tid=0x44a0203a: lease 192.168.2.23 will be
advertised
2019-05-06 21:35:22.328 INFO  [kea-dhcp4.leases/11297]
DHCP4_LEASE_ADVERT [hwtype=1 c0:a0:bb:e5:0b:62],
cid=[01:c0:a0:bb:e5:0b:62], tid=0x17c3c512: lease 192.168.2.7 will be
advertised
2019-05-06 21:35:22.443 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 c0:a0:bb:e5:0b:62], cid=[01:c0:a0:bb:e5:0b:62],
tid=0x17c3c512: lease 192.168.2.7 has been allocated
2019-05-06 21:35:22.499 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 00:0b:82:d0:b7:e1], cid=[01:00:0b:82:d0:b7:e1],
tid=0x44a0203a: lease 192.168.2.23 has been allocated
2019-05-06 21:35:25.994 INFO  [kea-dhcp4.leases/11297]
DHCP4_LEASE_ADVERT [hwtype=1 b8:ec:a3:b6:73:d7],
cid=[01:b8:ec:a3:b6:73:d7], tid=0x8f2f: lease 192.168.2.3 will be advertised
2019-05-06 21:35:30.042 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 b8:ec:a3:b6:73:d7], cid=[01:b8:ec:a3:b6:73:d7], tid=0x9ecf:
lease 192.168.2.3 has been allocated
2019-05-06 21:35:55.994 INFO  [kea-dhcp4.leases/11297]
DHCP4_LEASE_ADVERT [hwtype=1 00:1b:a9:7e:07:70],
cid=[01:00:1b:a9:7e:07:70], tid=0x31af0000: lease 192.168.2.21 will be
advertised
2019-05-06 21:35:56.088 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 00:1b:a9:7e:07:70], cid=[01:00:1b:a9:7e:07:70],
tid=0x31af0000: lease 192.168.2.21 has been allocated
2019-05-06 21:36:08.038 INFO  [kea-dhcp4.leases/11297]
DHCP4_LEASE_ADVERT [hwtype=1 bc:5f:f4:c2:a3:d1],
cid=[ff:f4:c2:a3:d1:00:01:00:01:20:a9:25:54:bc:5f:f4:c2:a3:d1],
tid=0x8e5320ef: lease 192.168.2.13 will be advertised
2019-05-06 21:36:08.227 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 bc:5f:f4:c2:a3:d1],
cid=[ff:f4:c2:a3:d1:00:01:00:01:20:a9:25:54:bc:5f:f4:c2:a3:d1],
tid=0x8e5320ef: lease 192.168.2.13 has been allocated
2019-05-06 21:37:31.068 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 b8:27:eb:b2:5a:01],
cid=[ff:eb:b2:5a:01:00:01:00:01:c7:92:bc:9d:b8:27:eb:28:58:06],
tid=0xaf76c42: lease 192.168.2.30 has been allocated
2019-05-06 21:39:19.010 INFO  [kea-dhcp4.leases/11297] DHCP4_INIT_REBOOT
[hwtype=1 00:be:3b:48:f6:f3], cid=[01:00:be:3b:48:f6:f3],
tid=0xfc7b00ae: client is in INIT-REBOOT state and requests address
192.168.2.100
2019-05-06 21:39:23.777 INFO  [kea-dhcp4.leases/11297] DHCP4_INIT_REBOOT
[hwtype=1 00:be:3b:48:f6:f3], cid=[01:00:be:3b:48:f6:f3],
tid=0xfc7b00ae: client is in INIT-REBOOT state and requests address
192.168.2.100
2019-05-06 21:39:25.863 INFO  [kea-dhcp4.leases/11297]
DHCP4_LEASE_ADVERT [hwtype=1 00:be:3b:48:f6:f3],
cid=[01:00:be:3b:48:f6:f3], tid=0xad233864: lease 192.168.2.100 will be
advertised
2019-05-06 21:39:26.005 INFO  [kea-dhcp4.leases/11297] DHCP4_LEASE_ALLOC
[hwtype=1 00:be:3b:48:f6:f3], cid=[01:00:be:3b:48:f6:f3],
tid=0xad233864: lease 192.168.2.100 has been allocated

-- 
------------------------------------------------------------------------
Logo JSIIT Consulting 	JSIIT Consulting 	Phone: 	+49 40 22865465 	
Jan Sielemann 	Telefax: 	+49 40 22865468 	
Riekbornweg 22 	Mobile: 	+49 1578 6769143 	
22547 Hamburg 	GPG-Public-Key: 	1D6CA679CEBDF96C
<https://jsiit.info/public/1D6CA679CEBDF96C.pub.gpg> 	

------------------------------------------------------------------------


More information about the Kea-users mailing list