[Kea-users] On the issue of DHCP4_BUFFER_WAIT kea-dhcp help / 关于 DHCP4_BUFFER_WAIT 在 kea-dhcp 中的问题求助

[mtiner at mtiner.com]

        hello , everyone of the kea developers and defenders ；

               I am a kea-dhcp server user , Kea-dhcp service has always been very stable, and can connect to the database, in the use of very good .
               But in the recent use of a failure I can not solve their own :
                        When I use the docker to run kea, the user can not get the IP address in most cases .
                        The log shows the error from DHCP4_BUFFER_WAIT_INTERRUPTED  and  DHCP4_BUFFER_WAIT
                        And I checked the official manual and did not find a solution .
                        Debug log excerpts :
2017-05-09 15:02:38.032 DEBUG [kea-dhcp4.dhcpsrv/1] DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer: reclaim-expired-leases
2017-05-09 15:02:38.032 DEBUG [kea-dhcp4.alloc-engine/1] ALLOC_ENGINE_V4_LEASES_RECLAMATION_START starting reclamation of expired leases (limit = 100 leases or 250 milliseconds)
2017-05-09 15:02:38.032 DEBUG [kea-dhcp4.dhcpsrv/1] DHCPSRV_MYSQL_GET_EXPIRED4 obtaining maximum 101 of expired IPv4 leases
2017-05-09 15:02:38.032 DEBUG [kea-dhcp4.alloc-engine/1] ALLOC_ENGINE_V4_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.440 ms
2017-05-09 15:02:38.032 DEBUG [kea-dhcp4.alloc-engine/1] ALLOC_ENGINE_V4_NO_MORE_EXPIRED_LEASES all expired leases have been reclaimed
2017-05-09 15:02:38.032 DEBUG [kea-dhcp4.dhcpsrv/1] DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases
2017-05-09 15:02:38.033 DEBUG [kea-dhcp4.packets/1] DHCP4_BUFFER_WAIT_INTERRUPTED interrupted wait for the next packet due to timeout, signal or external socket callback (timeout value is 1000)
2017-05-09 15:02:38.033 DEBUG [kea-dhcp4.packets/1] DHCP4_BUFFER_WAIT waiting for next DHCPv4 packet with timeout 1000 ms

                        Hope to get your reply and answers . 

            Sincere thanks
            May 9, 2017  23:24  Beijing China

p.s. My English is very poor, and the English version of the mail is provided by Google Translate.




        各位 kea-dhcp 的开发者及维护者 ；

               我是一个 kea-dhcp 的使用者 , Kea-dhcp 服务运行十分稳定, 并且可以连接数据库, 在使用体验上十分优秀 .
               但是在最近的使用中，我碰到了一个自己无法解决的问题 :
                        当我使用 Docker 运行 kea-dhcp 的时候, 用户在绝大多数情况下无法获取到 IP地址 .
                        日志中显示错误来自 DHCP4_BUFFER_WAIT_INTERRUPTED  和 DHCP4_BUFFER_WAIT
                       但是我查询官方手册后，没有发现如何解决这个问题 .
                        Debug 日志节选 :
2017-05-09 15:02:38.032 DEBUG [kea-dhcp4.dhcpsrv/1] DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer: reclaim-expired-leases
2017-05-09 15:02:38.032 DEBUG [kea-dhcp4.alloc-engine/1] ALLOC_ENGINE_V4_LEASES_RECLAMATION_START starting reclamation of expired leases (limit = 100 leases or 250 milliseconds)2017-05-09 15:02:38.032 DEBUG [kea-dhcp4.dhcpsrv/1] DHCPSRV_MYSQL_GET_EXPIRED4 obtaining maximum 101 of expired IPv4 leases2017-05-09 15:02:38.032 DEBUG [kea-dhcp4.alloc-engine/1] ALLOC_ENGINE_V4_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.440 ms2017-05-09 15:02:38.032 DEBUG [kea-dhcp4.alloc-engine/1] ALLOC_ENGINE_V4_NO_MORE_EXPIRED_LEASES all expired leases have been reclaimed2017-05-09 15:02:38.032 DEBUG [kea-dhcp4.dhcpsrv/1] DHCPSRV_TIMERMGR_START_TIMER starting timer: reclaim-expired-leases2017-05-09 15:02:38.033 DEBUG [kea-dhcp4.packets/1] DHCP4_BUFFER_WAIT_INTERRUPTED interrupted wait for the next packet due to timeout, signal or external socket callback (timeout value is 1000)
2017-05-09 15:02:38.033 DEBUG [kea-dhcp4.packets/1] DHCP4_BUFFER_WAIT waiting for next DHCPv4 packet with timeout 1000 ms

                        期待您的回复 . 

            由衷的感谢。
            2017年5月9日 23:24  中国北京



    丁亮 DING LIANG | Mtiner.com
    无所畏惧的小逗比   运维工程师  北京蓝军

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20170509/5605c2ec/attachment.htm>