Dear Mark, Thanks for coming back to me so quickly. Oops, I thought the port was linked to my report, but seemingly not - apologies. I installed OpenBSD DHCPd (http://www.freshports.org/net/dhcpd/), latest version. I do not seem to get this issue with the vastly more bulky ISC-DHCP4.3-Server, but certainly prefer the slim OpenBSD version. Any ideas? NTPd and date ad such are all fine on my server. CMOS clock is on UTC, and the lease times reported by OpenBSD DHCPd seem to stem from epoch. Thanks a lot! Chris
Just an update on this issue: dhcpd does not seem to like the "UTC" at the end of the time string. Please eee here from my log: Aug 27 08:15:56 server dhcpd: /var/db/dhcpd.leases line 9: unparseable time string Aug 27 08:15:56 server dhcpd: starts 6 2016/08/27 05:15:42 UTC; Anything I can do? Thanks a lot, Chris
*** Bug 212191 has been marked as a duplicate of this bug. ***
Copying over from 212008: I get this in the dhcpd log on syslog: Aug 24 15:26:07 server dhcpd: /var/db/dhcpd.leases line 21: unparseable time string Aug 24 15:26:07 server dhcpd: ends 4 1970/01/01 00:00:00 UTC; Aug 24 15:26:07 server dhcpd: ^ Aug 24 15:26:07 server dhcpd: /var/db/dhcpd.leases line 26: unparseable time string Aug 24 15:26:07 server dhcpd: starts 4 1970/01/01 00:00:00 UTC; Aug 24 15:26:07 server dhcpd: ^ Aug 24 15:26:07 server dhcpd: /var/db/dhcpd.leases line 27: unparseable time string Aug 24 15:26:07 server dhcpd: ends 4 1970/01/01 00:00:00 UTC; Aug 24 15:26:07 server dhcpd: ^ Aug 24 15:26:07 server dhcpd: /var/db/dhcpd.leases line 32: unparseable time string Aug 24 15:26:07 server dhcpd: starts 4 1970/01/01 00:00:00 UTC; Aug 24 15:26:07 server dhcpd: ^ Aug 24 15:26:07 server dhcpd: /var/db/dhcpd.leases line 33: unparseable time string Aug 24 15:26:07 server dhcpd: ends 4 1970/01/01 00:00:00 UTC; Aug 24 15:26:07 server dhcpd: ^ Aug 24 15:26:07 server dhcpd: /var/db/dhcpd.leases line 39: unparseable time string Aug 24 15:26:07 server dhcpd: starts 4 1970/01/01 00:00:00 UTC; Aug 24 15:26:07 server dhcpd: ^ Aug 24 15:26:07 server dhcpd: /var/db/dhcpd.leases line 40: unparseable time string Aug 24 15:26:07 server dhcpd: ends 4 1970/01/01 00:00:00 UTC; Seemingly time is issued in UTC, and DHCPd does not like it. It then starts to hang, and the entire LAN stalls.
*** Bug 212108 has been marked as a duplicate of this bug. ***
There is bug in the strptime function in the base system which cause this problem: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212983
I see. Thank you so much for pointing this out. Chris
This bug can be closed.
Ran into this one on 11.0-RELEASE-p8 so it's still unfixed in releases
Yes, I was able to reproduce the problem. Thanks for notifying!
Did the upgrade to 6.4.20181105 fix this issue ?
This should be fixed on all supported FreeBSD versions, even without a formal confirmation we are waiting since 2019. If it still affects someone, we can reopen