Bug 217615 - net/chrony daemon fails to start if IPV6 enabled
Summary: net/chrony daemon fails to start if IPV6 enabled
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-07 16:04 UTC by Robert Kruus
Modified: 2018-05-19 02:56 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (yonas)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Kruus 2017-03-07 16:04:20 UTC
FreeBSD wfm.gos.ca 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24 06:55:27 UTC 2016     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

If chrony is built with the IPV6 flag, it will cowardly refuse to start and show:
Assertion failed: (MD5_hash >= 0), function UTI_IPToRefid, file util.c, line 373.
in a /var/log/chrony/tracking.log.

It traces back to HSH_GetHashId in hash_nss.c where it can't find the hash algorithm or can't init nss or can't init the hash, so returns an invalid value.
Comment 1 Yonas Yanfa 2017-03-18 11:30:59 UTC
I think you might need to install the 'nss' package.

The patch in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217691 might help fix this.
Comment 2 Robert Kruus 2017-06-27 14:28:51 UTC
That is installed.  I had just done a system upgrade and rebuilt all the packages when chrony would no longer start.
Comment 3 OlivierW 2017-11-24 20:57:24 UTC
Hello,

I have the same problem, and it seems there's a conflict between IPv6 and NSS. My bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223840

Best Regards,
Olivier
Comment 4 Tobias Kortkamp freebsd_committer freebsd_triage 2018-05-09 11:45:13 UTC
Is this still relevant after switching chrony from nss to nettle
in ports r469426?
Comment 5 Robert Kruus 2018-05-09 19:26:18 UTC
Seems to build and run with nettle and ipv6 enabled (and NSS disabled).  I don't use IPV6 so can't really test it.
Comment 6 Tobias Kortkamp freebsd_committer freebsd_triage 2018-05-19 02:56:32 UTC
(In reply to rob.kruus from comment #5)
Thank you for testing.

Since nobody here has said anything to the contrary I assume that this is
fixed by ports r469426.