Re: [ntp:questions] ***Response from server was incomplete

2014-03-15 Thread nikolay
Hello, after restart monlist output work normal to ~ 600 line requests: root@ntp:/var/log # service ntpd restart Stopping ntpd. Waiting for PIDS: 1037. Starting ntpd. root@ntp:/var/log # ntpdc -n -c monlist remote address port local address count m ver code avgint lstint

Re: [ntp:questions] Synchronizing contrived time

2014-03-15 Thread Amit Dor-Shifer
Thanks to Per for spotting my usage error. ntpd seems to be working fine. Still client refuses to sync from the server, with the same error message as before: 192.168.1.11: Server dropped: strata too high server 192.168.1.11, port 123 stratum 16, precision -23, leap 11, trust 000 While this has

Re: [ntp:questions] ***Response from server was incomplete

2014-03-15 Thread Harlan Stenn
niko...@rootshells.eu writes: ... You are correct,there is 2 reports about version: root@ntp:/usr/ports/net/ntp # /usr/sbin/ntpd --version ntpd - NTP daemon program - Ver. 4.2.4p8 ntpq -c rv 0 version assID=0 status=0944 leap_none, sync_telephone, 4 events, event_peer/strat_chg,

Re: [ntp:questions] Not being able to sync the embedded target (client) with the host (server)

2014-03-15 Thread Laszlo Papp
Nvm, I solved it by using busybox's ntp for the time being. On Fri, Mar 14, 2014 at 6:18 PM, Charles Swiger cswi...@mac.com wrote: Hi-- On Mar 14, 2014, at 9:05 AM, Laszlo Papp lp...@kde.org wrote: I was told that this would not be a bug, although I could not figure out yet why it is not

Re: [ntp:questions] Not being able to sync the embedded target (client) with the host (server)

2014-03-15 Thread Rob
Laszlo Papp lp...@kde.org wrote: Yep, that was there. The interesting part is that it works for the first time after a while, and it gets broken when I try to set the date explicitly by the corresponding command. For some reason, ntp cannot sync afterwards. Reboot and/or restarting the daemons

Re: [ntp:questions] Synchronizing contrived time

2014-03-15 Thread William Unruh
On 2014-03-15, Amit Dor-Shifer amit.dor.shi...@gmail.com wrote: Thanks to Per for spotting my usage error. ntpd seems to be working fine. Still client refuses to sync from the server, with the same error message as before: 192.168.1.11: Server dropped: strata too high server 192.168.1.11,

Re: [ntp:questions] Not being able to sync the embedded target (client) with the host (server)

2014-03-15 Thread William Unruh
On 2014-03-14, Laszlo Papp lp...@kde.org wrote: Nvm, I solved it by using busybox's ntp for the time being. On Fri, Mar 14, 2014 at 6:18 PM, Charles Swiger cswi...@mac.com wrote: Hi-- On Mar 14, 2014, at 9:05 AM, Laszlo Papp lp...@kde.org wrote: I was told that this would not be a bug,

Re: [ntp:questions] Not being able to sync the embedded target (client) with the host (server)

2014-03-15 Thread Harlan Stenn
Laszlo Papp writes: Yep, that was there. The interesting part is that it works for the first time after a while, and it gets broken when I try to set the date explicitly by the corresponding command. For some reason, ntp cannot sync afterwards. Reboot and/or restarting the daemons may help

Re: [ntp:questions] Synchronizing contrived time

2014-03-15 Thread Amit Dor-Shifer
William, earlier along this post, I was asking (David, specifically) for a suggested fix to this error. Can you offer a possible fix? ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Synchronizing contrived time

2014-03-15 Thread William Unruh
On 2014-03-15, Amit Dor-Shifer amit.dor.shi...@gmail.com wrote: William, earlier along this post, I was asking (David, specifically) for a suggested fix to this error. Can you offer a possible fix? Try adding fudge 127.127.1.0 stratum 10 to the server, which tell is to assign stratum 10 to the

Re: [ntp:questions] Synchronizing contrived time

2014-03-15 Thread E-Mail Sent to this address will be added to the BlackLists
On 3/15/2014 10:21 AM, William Unruh wrote: On 2014-03-15, Amit Dor-Shifer amit.dor.shi...@gmail.com wrote: Thanks to Per for spotting my usage error. ntpd seems to be working fine. Still client refuses to sync from the server, with the same error message as before: 192.168.1.11: Server