I had that on my systems several times too and reports at the forum show the same problem. We should replace it.
Holger > -----Original Message----- > From: Bill Marquette [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 03, 2006 11:10 PM > To: [email protected] > Subject: Re: [pfSense Support] msntp (update) > > > lol. Oh well, too late, it's been beheaded. > > --Bill > > On 10/3/06, Roberto Greiner <[EMAIL PROTECTED]> wrote: > > I don't know exactly how or why, but after about 14 hours reporting > > errors, suddenly msntp decided to work and updated the > timeinfo properly. > > > > > > Oct 3 14:52:53 msntp[82526]: msntp: 2006 Oct 03 > 14:52:53.381 + -0.000 > > +/- 0.217 secs > > Oct 3 14:52:53 msntp[82526]: msntp: after 4 hours 59 mins > acc. 2 rej. 1 > > flush 0 max.off. -1.362 corr. -1.362 > > Oct 3 14:52:54 msntp[82526]: msntp: 2006 Oct 03 > 14:52:53.380 + 1.362 > > +/- 0.217 secs > > Oct 3 14:52:54 msntp[82526]: msntp: after 4 hours 59 mins > acc. 1 rej. 1 > > flush 0 max.off. -8.169 corr. -8.169 > > Oct 3 14:52:54 msntp[82526]: msntp: packets out of order > on socket 0 > > Oct 3 09:53:00 msntp[82526]: msntp: using NTP server > xxxx.xxx.xx (A.B.C.D) > > Oct 3 09:53:00 msntp[82526]: msntp: bad daemon restart information > > Oct 3 09:53:00 msntp[82526]: d=18000 c=5 x=18000 op=1 > > l=/var/run/msntp.pid f=/var/db/msntp.state 143.107.151.2 > > Oct 3 09:53:00 msntp[82526]: msntp options: a=2 p=0 v=1 > e=0.100 E=5.000 > > P=2147483647.000 > > > > > > > > Roberto > > > > > > Holger Bauer wrote: > > > We have some reports that msntp is randomly not working > reliably at some systems. We are testing a replacement for it > right now. If everything works well we'll roll out an update > that will use another daemon to update the time soon. > > > > > > Holger > > > > > > > > >> -----Original Message----- > > >> From: Alvaro Pietrobono [mailto:[EMAIL PROTECTED] > > >> Sent: Tuesday, October 03, 2006 9:42 AM > > >> To: [email protected] > > >> Subject: Re: [pfSense Support] msntp > > >> > > >> > > >> Same installation of 1.0-RC3 (on WRAP) but msntp > > >> works fine... > > >> > > >> Oct 3 09:08:31 msntp[8889]: msntp: 2006 Oct 03 > > >> 09:08:31.947 + -0.000 ± > > >> 0.028 secs > > >> Oct 3 09:08:31 msntp[8889]: msntp: after 1.2 secs acc. > > >> 1 rej. 0 flush 0 > > >> max.off. 0.078 corr. 0.078 > > >> Oct 3 09:08:31 msntp[8889]: msntp: using NTP > server ntp.ien.it > > >> (193.204.114.105) > > >> Oct 3 09:08:31 msntp[8889]: msntp: different > > >> parameters for restart > > >> Oct 3 09:08:31 msntp[8889]: d=18000 c=5 x=18000 op=1 > > >> l=/var/run/msntp.pid > > >> f=/var/db/msntp.state 193.204.114.105 > > >> Oct 3 09:08:30 msntp[8889]: msntp options: a=2 p=0 v=1 > > >> e=0.100 E=5.000 > > >> P=2147483647.000 > > >> > > >> ~A > > >> > > >> > > >> > > >> ----- Original Message ----- > > >> From: "Scott Ullrich" <[EMAIL PROTECTED]> > > >> To: <[email protected]> > > >> Sent: Monday, October 02, 2006 9:12 PM > > >> Subject: Re: [pfSense Support] msntp > > >> > > >> > > >> > > >>> On 10/2/06, Roberto Greiner <[EMAIL PROTECTED]> wrote: > > >>> > > >>>> hi, > > >>>> > > >>>> I've just installed rc3, and got a problem with ntp. > > >>>> > > >>>> I've tried adding the ntp server both as a name and as an > > >>>> > > >> IP address, > > >> > > >>>> but in the logs I keep getting the following message: > > >>>> > > >>>> Oct 2 15:33:41 teste msntp[12662]: msntp options: a=2 p=0 > > >>>> > > >> v=1 e=0.100 > > >> > > >>>> E=5.000 P=2147483647.000 > > >>>> Oct 2 15:33:41 teste msntp[12662]: d=18000 c=5 > x=18000 op=1 > > >>>> l=/var/run/msntp.pid f=/var/db/msntp.state A.B.C.D > > >>>> Oct 2 15:33:41 teste msntp[12662]: msntp: bad daemon > > >>>> > > >> restart information > > >> > > >>>> Oct 2 15:33:41 teste msntp[12662]: msntp: unable to locate IP > > >>>> address/number > > >>>> Oct 2 15:33:41 teste msntp[12662]: msntp: Unknown error: 0 > > >>>> > > >>>> Putting a name gets the same message, just with the > > >>>> > > >> machine name instead > > >> > > >>>> of the A.B.C.D address. I'v also tried a rule in the > > >>>> > > >> firewall opening > > >> > > >>>> ntp udp port, using the ntp port both as source port and > > >>>> > > >> destination > > >> > > >>>> port, but it didn't work. Does anyone know what's > > >>>> > > >> happening? The message > > >> > > >>>> is beeing repeat every minute. > > >>>> > > >>>> > > >>> Thanks for the report. I'll look into it. At this point I am > > >>> strongly leaning toward dumping MSNTP and replacing it > with a sane > > >>> program. > > >>> > > >>> Scott > > >>> > > > > > > -- > > ------------------------------------------------------------------- > > | Marcos Roberto Greiner > | > > | > | > > | Os otimistas acham que estamos no melhor dos > mundos | > > | Os pessimistas tem medo de que isto seja verdade > | > > | > Murphy | > > ------------------------------------------------------------------- > > | [EMAIL PROTECTED] > | > > ------------------------------------------------------------------- > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
