<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 7/25/19 12:11, Paul Theodoropoulos wrote:<br>
<blockquote type="cite"
cite="mid:e8d500b7-fd6b-45f3-6f29-8094b1110c1b@anastrophe.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
I just ran a first pass at setting up NTS on a device (RPI 3b+,
raspbian 10/buster). <br>
<br>
The server failed to come up on restart of service, as follows:<br>
<br>
2019-07-25T12:03:53 ntpd[21436]: NTSs: Private Key OK<br>
2019-07-25T12:03:53 ntpd[21436]: NTSs: OpenSSL security level is 2<br>
2019-07-25T12:03:53 ntpd[21436]: NTSs: listen4 worked<br>
2019-07-25T12:03:53 ntpd[21436]: NTSs: Can't create socket6:<br>
2019-07-25T12:03:53 ntpd[21436]: NTSc: Using system default root
certificates.<br>
2019-07-25T12:03:53 ntpd[21436]: NTS: troubles during init.
Bailing.<br>
<br>
I don't use ipv6. Without regard to the countless arguments
associated with ipv6, shouldn't NTS simply acknowledge that ipv6
isn't enabled, and continue initialization if it isn't available?
<br>
<br>
It was easily enough solved by re-enabling ipv6 in the boot
config, and I have it running fine now in my test environment.
</blockquote>
Forgot to add - <br>
root@ C-NTPsec: ~ # ntpd -V<br>
ntpd ntpsec-1.1.6+ 2019-07-19T23:59:16Z (git rev 8e3daaf0b)<br>
<br>
<pre class="moz-signature" cols="72">--
Paul Theodoropoulos
<a class="moz-txt-link-abbreviated" href="http://www.anastrophe.com">www.anastrophe.com</a></pre>
</body>
</html>