On 12/4/2017 5:02 AM, Francis Dupont wrote:
> I have to verify in the code but it seems to be the result of a lost
> signal... BTW there is a known race in signal handling with at least
> a ticket (#4068), if we are lucky it could be enough to address it.
>
> Regards
>
> Francis Dupont
>
> PS:
I have to verify in the code but it seems to be the result of a lost
signal... BTW there is a known race in signal handling with at least
a ticket (#4068), if we are lucky it could be enough to address it.
Regards
Francis Dupont
PS: strace (Linux), ktrace (BSD), dtrace (Solaris), etc, allow to
I can't see anything wrong in the logs...
Below, all log messages I got up to the last reclaim-expired-leases execution
(executed every second):
(and 7 minutes after that a packet is received)
(...)
2017-12-01 09:13:39.255 DEBUG [kea-dhcp4.packets/32013] DHCP4_BUFFER_WAIT
waiting for next DH
Are there any additional messages prior to this, indicating what might
have caused it?
Marcin
On 04.12.2017 09:32, Chaigneau, Nicolas wrote:
> Hello,
>
>
> Got another occurence of the issue, on 2017 December 1st at 09:12.
>
> This time I had the server running with debug logs.
> I noticed tha
Hello,
Got another occurence of the issue, on 2017 December 1st at 09:12.
This time I had the server running with debug logs.
I noticed that, not only did the LFC stopped being executed, but also the lease
reclaiming mechanism (both at the same time).
So I think that the issue is bigger, that
