Bug 212116 - net/dhcpd: Unparseable time format in dhcpd.leases
Summary: net/dhcpd: Unparseable time format in dhcpd.leases
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs mailing list
URL:
Keywords:
: 212108 212191 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-08-24 16:04 UTC by Christoph H. Larsen
Modified: 2019-01-06 17:42 UTC (History)
3 users (show)

See Also:
koue: maintainer-feedback+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph H. Larsen 2016-08-24 16:04:54 UTC
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
Comment 1 Christoph H. Larsen 2016-08-27 06:49:45 UTC
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
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2016-08-27 11:30:18 UTC
*** Bug 212191 has been marked as a duplicate of this bug. ***
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2016-08-28 05:18:26 UTC
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.
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2016-08-28 05:19:05 UTC
*** Bug 212108 has been marked as a duplicate of this bug. ***
Comment 5 Nikola Kolev 2016-09-25 12:01:10 UTC
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
Comment 6 Christoph H. Larsen 2016-09-25 12:23:21 UTC
I see. Thank you so much for pointing this out. 
Chris
Comment 7 Nikola Kolev 2016-10-23 18:31:00 UTC
This bug can be closed.
Comment 8 swa 2017-03-31 20:19:54 UTC
Ran into this one on 11.0-RELEASE-p8 so it's still unfixed in releases
Comment 9 Nikola Kolev 2017-04-12 08:04:09 UTC
Yes, I was able to reproduce the problem. Thanks for notifying!
Comment 10 Kurt Jaeger freebsd_committer 2019-01-06 17:42:09 UTC
Did the upgrade to 6.4.20181105 fix this issue ?