Re: obsd 6.7 - ntpd error msg
On Thu, Jun 18, 2020 at 11:41:17AM +0200, Otto Moerbeek wrote:
> On Thu, Jun 18, 2020 at 09:57:34AM +0200, Salvatore Cuzzilla wrote:
>
> > Perfect, tnx!
> >
> > On 18.06.2020 07:58, Otto Moerbeek wrote:
> > > On Wed, Jun 17, 2020 at 10:53:54PM +0200, Salvatore Cuzzilla wrote:
> > >
> > > > Hi Otto here the logs (multitail) - @22:49:15 I restarted ntpd:
> > > > -
> > > > Jun 17 22:49:23 obsd ntpd[88568]: constraint reply from 188.61.106.24:
> > > > offset -0.541051
> > > > Jun 17 22:49:46 obsd ntpd[88568]: peer 172.17.1.1 now valid
> > > > 01] /var/log/daemon <---
> > > >
> > > >
> > > >
> > > > 248KB - 2020/06/17 22:49:46
> > > > -
> > > > Jun 17 14:00:01 obsd syslogd[80400]: restart
> > > > Jun 17 16:19:41 obsd ntpd[92699]: pipe write error (from main): No such
> > > > file or directory
> > > > Jun 17 16:21:07 obsd ntpd[29588]: pipe write error (from main): No such
> > > > file or directory
> > > > Jun 17 17:00:01 obsd syslogd[80400]: restart
> > > > Jun 17 17:01:25 obsd ntpd[96273]: pipe write error (from main): No such
> > > > file or directory
> > > > Jun 17 17:02:38 obsd ntpd[94737]: pipe write error (from main): No such
> > > > file or directory
> > > > Jun 17 20:00:01 obsd syslogd[80400]: restart
> > > > Jun 17 22:00:01 obsd syslogd[80400]: restart
> > > > Jun 17 22:49:22 obsd ntpd[40936]: pipe write error (from main): No such
> > > > file or directory
> > > > 02] /var/log/messages <---
> > > >
> > > >
> > > >
> > > > 205KB - 2020/06/17 22:49:22
> > > > -
> > > > 22:49:15 -ksh ToTo@obsd ~ $ doas rcctl restart ntpd
> > > > ntpd(ok)
> > > > ntpd(ok)
> > > > 22:49:23 -ksh ToTo@obsd ~ $
> > >
> > >
> > > OK, now we're getting somewhere. It always helps to provide lots of
> > > information form the start.
> > >
> > > The message is generated by ntpd being stopped. It is harmless,
> > > though it is actually wrong, it's a pip read error.
> > >
> > > So nothing to worry about. I'll see if the log level should be
> > > changed to debug for this one or maybe another solution.
> > >
>
> And now with diff.
I committed a slighlty more conservative version of this diff. A dns
read error (which should not happen) still logs at warn level.
-Otto
>
> Index: ntp.c
> ===
> RCS file: /cvs/src/usr.sbin/ntpd/ntp.c,v
> retrieving revision 1.164
> diff -u -p -r1.164 ntp.c
> --- ntp.c 11 Apr 2020 07:49:48 - 1.164
> +++ ntp.c 18 Jun 2020 09:39:03 -
> @@ -365,7 +365,7 @@ ntp_main(struct ntpd_conf *nconf, struct
> if (nfds > 0 && pfd[PFD_PIPE_MAIN].revents & (POLLIN|POLLERR)) {
> nfds--;
> if (ntp_dispatch_imsg() == -1) {
> - log_warn("pipe write error (from main)");
> + log_debug("pipe read error (from main)");
> ntp_quit = 1;
> }
> }
> @@ -380,7 +380,7 @@ ntp_main(struct ntpd_conf *nconf, struct
> if (nfds > 0 && pfd[PFD_PIPE_DNS].revents & (POLLIN|POLLERR)) {
> nfds--;
> if (ntp_dispatch_imsg_dns() == -1) {
> - log_warn("pipe write error (from dns engine)");
> + log_debug("pipe read error (from dns engine)");
> ntp_quit = 1;
> }
> }
>
Re: obsd 6.7 - ntpd error msg
On Thu, Jun 18, 2020 at 09:57:34AM +0200, Salvatore Cuzzilla wrote:
> Perfect, tnx!
>
> On 18.06.2020 07:58, Otto Moerbeek wrote:
> > On Wed, Jun 17, 2020 at 10:53:54PM +0200, Salvatore Cuzzilla wrote:
> >
> > > Hi Otto here the logs (multitail) - @22:49:15 I restarted ntpd:
> > > -
> > > Jun 17 22:49:23 obsd ntpd[88568]: constraint reply from 188.61.106.24:
> > > offset -0.541051
> > > Jun 17 22:49:46 obsd ntpd[88568]: peer 172.17.1.1 now valid
> > > 01] /var/log/daemon <---
> > >
> > >
> > >
> > > 248KB - 2020/06/17 22:49:46
> > > -
> > > Jun 17 14:00:01 obsd syslogd[80400]: restart
> > > Jun 17 16:19:41 obsd ntpd[92699]: pipe write error (from main): No such
> > > file or directory
> > > Jun 17 16:21:07 obsd ntpd[29588]: pipe write error (from main): No such
> > > file or directory
> > > Jun 17 17:00:01 obsd syslogd[80400]: restart
> > > Jun 17 17:01:25 obsd ntpd[96273]: pipe write error (from main): No such
> > > file or directory
> > > Jun 17 17:02:38 obsd ntpd[94737]: pipe write error (from main): No such
> > > file or directory
> > > Jun 17 20:00:01 obsd syslogd[80400]: restart
> > > Jun 17 22:00:01 obsd syslogd[80400]: restart
> > > Jun 17 22:49:22 obsd ntpd[40936]: pipe write error (from main): No such
> > > file or directory
> > > 02] /var/log/messages <---
> > >
> > >
> > >
> > > 205KB - 2020/06/17 22:49:22
> > > -
> > > 22:49:15 -ksh ToTo@obsd ~ $ doas rcctl restart ntpd
> > > ntpd(ok)
> > > ntpd(ok)
> > > 22:49:23 -ksh ToTo@obsd ~ $
> >
> >
> > OK, now we're getting somewhere. It always helps to provide lots of
> > information form the start.
> >
> > The message is generated by ntpd being stopped. It is harmless,
> > though it is actually wrong, it's a pip read error.
> >
> > So nothing to worry about. I'll see if the log level should be
> > changed to debug for this one or maybe another solution.
> >
And now with diff.
-Otto
Index: ntp.c
===
RCS file: /cvs/src/usr.sbin/ntpd/ntp.c,v
retrieving revision 1.164
diff -u -p -r1.164 ntp.c
--- ntp.c 11 Apr 2020 07:49:48 - 1.164
+++ ntp.c 18 Jun 2020 09:39:03 -
@@ -365,7 +365,7 @@ ntp_main(struct ntpd_conf *nconf, struct
if (nfds > 0 && pfd[PFD_PIPE_MAIN].revents & (POLLIN|POLLERR)) {
nfds--;
if (ntp_dispatch_imsg() == -1) {
- log_warn("pipe write error (from main)");
+ log_debug("pipe read error (from main)");
ntp_quit = 1;
}
}
@@ -380,7 +380,7 @@ ntp_main(struct ntpd_conf *nconf, struct
if (nfds > 0 && pfd[PFD_PIPE_DNS].revents & (POLLIN|POLLERR)) {
nfds--;
if (ntp_dispatch_imsg_dns() == -1) {
- log_warn("pipe write error (from dns engine)");
+ log_debug("pipe read error (from dns engine)");
ntp_quit = 1;
}
}
Re: obsd 6.7 - ntpd error msg
Perfect, tnx! On 18.06.2020 07:58, Otto Moerbeek wrote: On Wed, Jun 17, 2020 at 10:53:54PM +0200, Salvatore Cuzzilla wrote: Hi Otto here the logs (multitail) - @22:49:15 I restarted ntpd: - Jun 17 22:49:23 obsd ntpd[88568]: constraint reply from 188.61.106.24: offset -0.541051 Jun 17 22:49:46 obsd ntpd[88568]: peer 172.17.1.1 now valid 01] /var/log/daemon <--- 248KB - 2020/06/17 22:49:46 - Jun 17 14:00:01 obsd syslogd[80400]: restart Jun 17 16:19:41 obsd ntpd[92699]: pipe write error (from main): No such file or directory Jun 17 16:21:07 obsd ntpd[29588]: pipe write error (from main): No such file or directory Jun 17 17:00:01 obsd syslogd[80400]: restart Jun 17 17:01:25 obsd ntpd[96273]: pipe write error (from main): No such file or directory Jun 17 17:02:38 obsd ntpd[94737]: pipe write error (from main): No such file or directory Jun 17 20:00:01 obsd syslogd[80400]: restart Jun 17 22:00:01 obsd syslogd[80400]: restart Jun 17 22:49:22 obsd ntpd[40936]: pipe write error (from main): No such file or directory 02] /var/log/messages <--- 205KB - 2020/06/17 22:49:22 - 22:49:15 -ksh ToTo@obsd ~ $ doas rcctl restart ntpd ntpd(ok) ntpd(ok) 22:49:23 -ksh ToTo@obsd ~ $ OK, now we're getting somewhere. It always helps to provide lots of information form the start. The message is generated by ntpd being stopped. It is harmless, though it is actually wrong, it's a pip read error. So nothing to worry about. I'll see if the log level should be changed to debug for this one or maybe another solution. -Otto On 17.06.2020 21:18, Otto Moerbeek wrote: > On Wed, Jun 17, 2020 at 09:15:22PM +0200, Salvatore Cuzzilla wrote: > > > Hi Otto, > > > > thanks for helping, really appreciated! > > The msg is showing after each restart. My simple conf here below: > > - > > 21:05:52 -ksh ToTo@obsd ~ $ doas cat /etc/ntpd.conf > > # $OpenBSD: ntpd.conf,v 1.14 2015/07/15 20:28:37 ajacoutot Exp $ > > # > > # See ntpd.conf(5) and /etc/examples/ntpd.conf > > > > server 172.17.1.1 > > sensor * > > constraints from "https://www.alfanetti.org; > > - > > And show the log lines, all of them > >-Otto > > > > > On 17.06.2020 20:51, Otto Moerbeek wrote: > > > On Wed, Jun 17, 2020 at 04:50:46PM +0200, Salvatore Cuzzilla wrote: > > > > > > > Hi Folks, > > > > > > > > when I restart ntpd I see this msg in /var/log/daemon: > > > > > > > > Jun 17 16:19:41 obsd ntpd[92699]: pipe write error (from main): No suchfile or directory > > > > > > > > however, time seems to be in sync: > > > > > > > > --- > > > > 16:37:17 -ksh ToTo@obsd ~ $ ntpctl -sa > > > > 1/1 peers valid, 1/1 sensors valid, constraint offset -1s, clock unsynced > > > > > > > > peer > > > >wt tl st next poll offset delay jitter > > > > 172.17.1.1 > > > > 1 10 3 2361s 3069s-0.008ms 0.716ms 0.137ms > > > > > > > > sensor > > > >wt gd st next poll offset correction > > > > vmt0 > > > > 1 1 07s 15s27.860ms 0.000ms > > > > > > > > 16:38:20 -ksh ToTo@obsd ~ $ doas sysctl -a | grep timecounter > > > > kern.timecounter.tick=1 > > > > kern.timecounter.timestepwarnings=0 > > > > kern.timecounter.hardware=tsc > > > > kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000) acpitimer0(1000) > > > > --- > > > > > > > > anyone else experiencing the same? > > > > > > > > --- > > > > :wq, > > > > Salvatore. > > > > > > > > > > Was the message in the log before or after restarting? > > > Please show your ntpd.conf > > > > > > -Otto > > > > > > > --- > > :wq, > > Salvatore. > --- :wq, Salvatore. --- :wq, Salvatore.
Re: obsd 6.7 - ntpd error msg
On Wed, Jun 17, 2020 at 10:53:54PM +0200, Salvatore Cuzzilla wrote: > Hi Otto here the logs (multitail) - @22:49:15 I restarted ntpd: > - > Jun 17 22:49:23 obsd ntpd[88568]: constraint reply from 188.61.106.24: offset > -0.541051 > Jun 17 22:49:46 obsd ntpd[88568]: peer 172.17.1.1 now valid > 01] /var/log/daemon <--- > > >248KB - 2020/06/17 > 22:49:46 > - > Jun 17 14:00:01 obsd syslogd[80400]: restart > Jun 17 16:19:41 obsd ntpd[92699]: pipe write error (from main): No such file > or directory > Jun 17 16:21:07 obsd ntpd[29588]: pipe write error (from main): No such file > or directory > Jun 17 17:00:01 obsd syslogd[80400]: restart > Jun 17 17:01:25 obsd ntpd[96273]: pipe write error (from main): No such file > or directory > Jun 17 17:02:38 obsd ntpd[94737]: pipe write error (from main): No such file > or directory > Jun 17 20:00:01 obsd syslogd[80400]: restart > Jun 17 22:00:01 obsd syslogd[80400]: restart > Jun 17 22:49:22 obsd ntpd[40936]: pipe write error (from main): No such file > or directory > 02] /var/log/messages <--- > > >205KB - 2020/06/17 > 22:49:22 > - > 22:49:15 -ksh ToTo@obsd ~ $ doas rcctl restart ntpd > ntpd(ok) > ntpd(ok) > 22:49:23 -ksh ToTo@obsd ~ $ OK, now we're getting somewhere. It always helps to provide lots of information form the start. The message is generated by ntpd being stopped. It is harmless, though it is actually wrong, it's a pip read error. So nothing to worry about. I'll see if the log level should be changed to debug for this one or maybe another solution. -Otto > > On 17.06.2020 21:18, Otto Moerbeek wrote: > > On Wed, Jun 17, 2020 at 09:15:22PM +0200, Salvatore Cuzzilla wrote: > > > > > Hi Otto, > > > > > > thanks for helping, really appreciated! > > > The msg is showing after each restart. My simple conf here below: > > > - > > > 21:05:52 -ksh ToTo@obsd ~ $ doas cat /etc/ntpd.conf > > > # $OpenBSD: ntpd.conf,v 1.14 2015/07/15 20:28:37 ajacoutot Exp $ > > > # > > > # See ntpd.conf(5) and /etc/examples/ntpd.conf > > > > > > server 172.17.1.1 > > > sensor * > > > constraints from "https://www.alfanetti.org; > > > - > > > > And show the log lines, all of them > > > > -Otto > > > > > > > > On 17.06.2020 20:51, Otto Moerbeek wrote: > > > > On Wed, Jun 17, 2020 at 04:50:46PM +0200, Salvatore Cuzzilla wrote: > > > > > > > > > Hi Folks, > > > > > > > > > > when I restart ntpd I see this msg in /var/log/daemon: > > > > > > > > > > Jun 17 16:19:41 obsd ntpd[92699]: pipe write error (from main): No > > > > > suchfile or directory > > > > > > > > > > however, time seems to be in sync: > > > > > > > > > > --- > > > > > 16:37:17 -ksh ToTo@obsd ~ $ ntpctl -sa > > > > > 1/1 peers valid, 1/1 sensors valid, constraint offset -1s, clock > > > > > unsynced > > > > > > > > > > peer > > > > >wt tl st next poll offset delay jitter > > > > > 172.17.1.1 > > > > > 1 10 3 2361s 3069s-0.008ms 0.716ms 0.137ms > > > > > > > > > > sensor > > > > >wt gd st next poll offset correction > > > > > vmt0 > > > > > 1 1 07s 15s27.860ms 0.000ms > > > > > > > > > > 16:38:20 -ksh ToTo@obsd ~ $ doas sysctl -a | grep timecounter > > > > > kern.timecounter.tick=1 > > > > > kern.timecounter.timestepwarnings=0 > > > > > kern.timecounter.hardware=tsc > > > > > kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000) > > > > > acpitimer0(1000) > > > > > --- > > > > > > > > > > anyone else experiencing the same? > > > > > > > > > > --- > > > > > :wq, > > > > > Salvatore. > > > > > > > > > > > > > Was the message in the log before or after restarting? > > > > Please show your ntpd.conf > > > > > > > > -Otto > > > > > > > > > > --- > > > :wq, > > > Salvatore. > > > > --- > :wq, > Salvatore.
Re: obsd 6.7 - ntpd error msg
Hi Otto here the logs (multitail) - @22:49:15 I restarted ntpd: - Jun 17 22:49:23 obsd ntpd[88568]: constraint reply from 188.61.106.24: offset -0.541051 Jun 17 22:49:46 obsd ntpd[88568]: peer 172.17.1.1 now valid 01] /var/log/daemon <--- 248KB - 2020/06/17 22:49:46 - Jun 17 14:00:01 obsd syslogd[80400]: restart Jun 17 16:19:41 obsd ntpd[92699]: pipe write error (from main): No such file or directory Jun 17 16:21:07 obsd ntpd[29588]: pipe write error (from main): No such file or directory Jun 17 17:00:01 obsd syslogd[80400]: restart Jun 17 17:01:25 obsd ntpd[96273]: pipe write error (from main): No such file or directory Jun 17 17:02:38 obsd ntpd[94737]: pipe write error (from main): No such file or directory Jun 17 20:00:01 obsd syslogd[80400]: restart Jun 17 22:00:01 obsd syslogd[80400]: restart Jun 17 22:49:22 obsd ntpd[40936]: pipe write error (from main): No such file or directory 02] /var/log/messages <--- 205KB - 2020/06/17 22:49:22 - 22:49:15 -ksh ToTo@obsd ~ $ doas rcctl restart ntpd ntpd(ok) ntpd(ok) 22:49:23 -ksh ToTo@obsd ~ $ On 17.06.2020 21:18, Otto Moerbeek wrote: On Wed, Jun 17, 2020 at 09:15:22PM +0200, Salvatore Cuzzilla wrote: Hi Otto, thanks for helping, really appreciated! The msg is showing after each restart. My simple conf here below: - 21:05:52 -ksh ToTo@obsd ~ $ doas cat /etc/ntpd.conf # $OpenBSD: ntpd.conf,v 1.14 2015/07/15 20:28:37 ajacoutot Exp $ # # See ntpd.conf(5) and /etc/examples/ntpd.conf server 172.17.1.1 sensor * constraints from "https://www.alfanetti.org; - And show the log lines, all of them -Otto On 17.06.2020 20:51, Otto Moerbeek wrote: > On Wed, Jun 17, 2020 at 04:50:46PM +0200, Salvatore Cuzzilla wrote: > > > Hi Folks, > > > > when I restart ntpd I see this msg in /var/log/daemon: > > > > Jun 17 16:19:41 obsd ntpd[92699]: pipe write error (from main): No suchfile or directory > > > > however, time seems to be in sync: > > > > --- > > 16:37:17 -ksh ToTo@obsd ~ $ ntpctl -sa > > 1/1 peers valid, 1/1 sensors valid, constraint offset -1s, clock unsynced > > > > peer > >wt tl st next poll offset delay jitter > > 172.17.1.1 > > 1 10 3 2361s 3069s-0.008ms 0.716ms 0.137ms > > > > sensor > >wt gd st next poll offset correction > > vmt0 > > 1 1 07s 15s27.860ms 0.000ms > > > > 16:38:20 -ksh ToTo@obsd ~ $ doas sysctl -a | grep timecounter > > kern.timecounter.tick=1 > > kern.timecounter.timestepwarnings=0 > > kern.timecounter.hardware=tsc > > kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000) acpitimer0(1000) > > --- > > > > anyone else experiencing the same? > > > > --- > > :wq, > > Salvatore. > > > > Was the message in the log before or after restarting? > Please show your ntpd.conf > >-Otto > --- :wq, Salvatore. --- :wq, Salvatore.
Re: obsd 6.7 - ntpd error msg
On Wed, Jun 17, 2020 at 09:15:22PM +0200, Salvatore Cuzzilla wrote: > Hi Otto, > > thanks for helping, really appreciated! > The msg is showing after each restart. My simple conf here below: > - > 21:05:52 -ksh ToTo@obsd ~ $ doas cat /etc/ntpd.conf > # $OpenBSD: ntpd.conf,v 1.14 2015/07/15 20:28:37 ajacoutot Exp $ > # > # See ntpd.conf(5) and /etc/examples/ntpd.conf > > server 172.17.1.1 > sensor * > constraints from "https://www.alfanetti.org; > - And show the log lines, all of them -Otto > > On 17.06.2020 20:51, Otto Moerbeek wrote: > > On Wed, Jun 17, 2020 at 04:50:46PM +0200, Salvatore Cuzzilla wrote: > > > > > Hi Folks, > > > > > > when I restart ntpd I see this msg in /var/log/daemon: > > > > > > Jun 17 16:19:41 obsd ntpd[92699]: pipe write error (from main): No > > > suchfile or directory > > > > > > however, time seems to be in sync: > > > > > > --- > > > 16:37:17 -ksh ToTo@obsd ~ $ ntpctl -sa > > > 1/1 peers valid, 1/1 sensors valid, constraint offset -1s, clock unsynced > > > > > > peer > > >wt tl st next poll offset delay jitter > > > 172.17.1.1 > > > 1 10 3 2361s 3069s-0.008ms 0.716ms 0.137ms > > > > > > sensor > > >wt gd st next poll offset correction > > > vmt0 > > > 1 1 07s 15s27.860ms 0.000ms > > > > > > 16:38:20 -ksh ToTo@obsd ~ $ doas sysctl -a | grep timecounter > > > kern.timecounter.tick=1 > > > kern.timecounter.timestepwarnings=0 > > > kern.timecounter.hardware=tsc > > > kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000) > > > acpitimer0(1000) > > > --- > > > > > > anyone else experiencing the same? > > > > > > --- > > > :wq, > > > Salvatore. > > > > > > > Was the message in the log before or after restarting? > > Please show your ntpd.conf > > > > -Otto > > > > --- > :wq, > Salvatore.
Re: obsd 6.7 - ntpd error msg
Hi Otto, thanks for helping, really appreciated! The msg is showing after each restart. My simple conf here below: - 21:05:52 -ksh ToTo@obsd ~ $ doas cat /etc/ntpd.conf # $OpenBSD: ntpd.conf,v 1.14 2015/07/15 20:28:37 ajacoutot Exp $ # # See ntpd.conf(5) and /etc/examples/ntpd.conf server 172.17.1.1 sensor * constraints from "https://www.alfanetti.org; - On 17.06.2020 20:51, Otto Moerbeek wrote: On Wed, Jun 17, 2020 at 04:50:46PM +0200, Salvatore Cuzzilla wrote: Hi Folks, when I restart ntpd I see this msg in /var/log/daemon: Jun 17 16:19:41 obsd ntpd[92699]: pipe write error (from main): No suchfile or directory however, time seems to be in sync: --- 16:37:17 -ksh ToTo@obsd ~ $ ntpctl -sa 1/1 peers valid, 1/1 sensors valid, constraint offset -1s, clock unsynced peer wt tl st next poll offset delay jitter 172.17.1.1 1 10 3 2361s 3069s-0.008ms 0.716ms 0.137ms sensor wt gd st next poll offset correction vmt0 1 1 07s 15s27.860ms 0.000ms 16:38:20 -ksh ToTo@obsd ~ $ doas sysctl -a | grep timecounter kern.timecounter.tick=1 kern.timecounter.timestepwarnings=0 kern.timecounter.hardware=tsc kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000) acpitimer0(1000) --- anyone else experiencing the same? --- :wq, Salvatore. Was the message in the log before or after restarting? Please show your ntpd.conf -Otto --- :wq, Salvatore.
Re: obsd 6.7 - ntpd error msg
On Wed, Jun 17, 2020 at 04:50:46PM +0200, Salvatore Cuzzilla wrote: > Hi Folks, > > when I restart ntpd I see this msg in /var/log/daemon: > > Jun 17 16:19:41 obsd ntpd[92699]: pipe write error (from main): No suchfile > or directory > > however, time seems to be in sync: > > --- > 16:37:17 -ksh ToTo@obsd ~ $ ntpctl -sa > 1/1 peers valid, 1/1 sensors valid, constraint offset -1s, clock unsynced > > peer >wt tl st next poll offset delay jitter > 172.17.1.1 > 1 10 3 2361s 3069s-0.008ms 0.716ms 0.137ms > > sensor >wt gd st next poll offset correction > vmt0 > 1 1 07s 15s27.860ms 0.000ms > > 16:38:20 -ksh ToTo@obsd ~ $ doas sysctl -a | grep timecounter > kern.timecounter.tick=1 > kern.timecounter.timestepwarnings=0 > kern.timecounter.hardware=tsc > kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000) acpitimer0(1000) > --- > > anyone else experiencing the same? > > --- > :wq, > Salvatore. > Was the message in the log before or after restarting? Please show your ntpd.conf -Otto
obsd 6.7 - ntpd error msg
Hi Folks, when I restart ntpd I see this msg in /var/log/daemon: Jun 17 16:19:41 obsd ntpd[92699]: pipe write error (from main): No suchfile or directory however, time seems to be in sync: --- 16:37:17 -ksh ToTo@obsd ~ $ ntpctl -sa 1/1 peers valid, 1/1 sensors valid, constraint offset -1s, clock unsynced peer wt tl st next poll offset delay jitter 172.17.1.1 1 10 3 2361s 3069s-0.008ms 0.716ms 0.137ms sensor wt gd st next poll offset correction vmt0 1 1 07s 15s27.860ms 0.000ms 16:38:20 -ksh ToTo@obsd ~ $ doas sysctl -a | grep timecounter kern.timecounter.tick=1 kern.timecounter.timestepwarnings=0 kern.timecounter.hardware=tsc kern.timecounter.choice=i8254(0) acpihpet0(1000) tsc(2000) acpitimer0(1000) --- anyone else experiencing the same? --- :wq, Salvatore.
