+- Logic Machine Forum (https://forum.logicmachine.net)
+-- Forum: LogicMachine eco-system (https://forum.logicmachine.net/forumdisplay.php?fid=1)
+--- Forum: General (https://forum.logicmachine.net/forumdisplay.php?fid=2)
+--- Thread: NTP Problem (/showthread.php?tid=59)
NTP Problem - RSV4 - 10.08.2015
Hi all,
I am using the following NTP servers on the LM3:Reactor
0.ch.pool.ntp.org
1.ch.pool.ntp.org
2.ch.pool.ntp.org
3.ch.pool.ntp.org
They work on my PC, but on the LM3:Reactor I have no success. Time drifts significantly and is now 9 (!) mins ahead of my PC after 3 months. I have a DCF77 synced watch as reference as well, perfectly in sync with my PC. So I must be doing something wrong on the LM. Changing NTP servers did not help. And the servers above work flawlessly.
Any hints?
Best regards!
RE: NTP Problem - admin - 11.08.2015
Do you have correct DNS settings on your LM? Have you tried pinging one of the servers from System config?
RE: NTP Problem - RSV4 - 11.08.2015
How do I ping the servers from system config? And what should the DNS settings be?
RE: NTP Problem - admin - 11.08.2015
You can put 8.8.8.8 as DNS server. Ping is in Status / Network utilities menu.
RE: NTP Problem - RSV4 - 11.08.2015
Thanks. Will check tonight and let you know.
RE: NTP Problem - RSV4 - 11.08.2015
Ping was unsuccessful. I get
Quote:ping: bad address '0.ch.pool.ntp.org'
256
Where do I set the DNS Server?
Best regards,
Robin
RE: NTP Problem - admin - 12.08.2015
In System config / Network / Interfaces click "eth0"
RE: NTP Problem - RSV4 - 14.08.2015
I now have
Protocol: Static IP
IP address: 10.0.x.xx (fix IP address of my LogicMachine)
Network mask: 255.255.255.0
Gateway IP: 10.0.x.xx (fix IP address of my Router)
DNS Server 1: 8.8.8.8
DNS Server 2: 8.8.4.4
MTU: [empty]
The time now seems to be perfectly correct, pinging the servers is successful. A few questions:
1.) For what else is the DNS Server used? Is it simply just the resolution of the NTP servers addresses? Or is there more communication 'to the outside'?
2.) Is it correct to leave MTU empty?
3.) I think the information of setting name servers and the router/gateway address should be displayed in the NTP window (unless the answer to question 1 contains more applications)
Best regards,
Robin
RE: NTP Problem - admin - 18.08.2015
1. DNS server is used for domain name resolution for "outside" communications that require it (HTTP requests, for example). The same thing for Gateway, it is required for any communication from/to LM outside of local network.
2. Yes, empty MTU is fine.
3. No
Apart from NTP LM won't do any communication on its own by default.
RE: NTP Problem - RSV4 - 20.03.2016
Hi,
I still have the problem that my time runs away. Just checked and the LM time is more than 8 mins ahead? Hints?
Thanks
RE: NTP Problem - admin - 21.03.2016
Try executing this script, it should provide some info on why NTP might be failing:
Code:
res = io.readproc('ntpd -dnq -p 0.ch.pool.ntp.org 2>&1')
log(res)RE: NTP Problem - RSV4 - 21.03.2016
Thank you, will do this evening and post result!
RE: NTP Problem - RSV4 - 24.04.2016
This is what I get as result:
* string: ntpd: resolved peer 0.ch.pool.ntp.org to 81.94.123.16
ntpd: sending query to 81.94.123.16
ntpd: reply from 81.94.123.16: offset:-466.137866 delay:0.030351 status:0x24 strat:2 refid:0x4a199e55 rootdelay:0.000214 reach:0x01
ntpd: sending query to 81.94.123.16
ntpd: reply from 81.94.123.16: offset:-466.134459 delay:0.038311 status:0x24 strat:2 refid:0x4a199e55 rootdelay:0.000214 reach:0x03
ntpd: sending query to 81.94.123.16
ntpd: reply from 81.94.123.16: offset:-466.134637 delay:0.038405 status:0x24 strat:2 refid:0x4a199e55 rootdelay:0.000214 reach:0x07
ntpd: sending query to 81.94.123.16
ntpd: reply from 81.94.123.16: offset:-466.134215 delay:0.037433 status:0x24 strat:2 refid:0x4a199e55 rootdelay:0.000214 reach:0x0f
ntpd: sending query to 81.94.123.16
ntpd: reply from 81.94.123.16: offset:-466.135192 delay:0.038626 status:0x24 strat:2 refid:0x4a199e55 rootdelay:0.000214 reach:0x1f
ntpd: setting time to 2016-04-24 09:09:34.944574 (offset -466.135192s)
Running the script set the time correctly, however it was wrong before. I export data every minute to a .csv file, you can see the time jump backwards from 9:17:00 to 09:10:30. The time was running away before and I did not change anything in the NTP settings, I just ran the script, nothing else.
2016.04.24 09:16:41 Keller Differenz abs. Feuchtigkeit zu Umgebung 3.89938163757
2016.04.24 09:17:00 Aussen rel. Feuchtigkeit 86.4
2016.04.24 09:17:00 Aussen Taupunkt 0.4
2016.04.24 09:17:00 Helligkeit Nord 4275.2
2016.04.24 09:17:00 Aussen abs. Feuchtigkeit 4.95355892181
2016.04.24 09:17:00 Aussen Temperatur 2.4
2016.04.24 09:10:30 Aussen Temperatur 2.4
2016.04.24 09:10:40 Keller abs. Feuchtigkeit 8.84268665314
2016.04.24 09:10:40 Keller Temperatur 15.9
RE: NTP Problem - Håvard Fosså - 22.12.2016
I have a similar problem:
After power failures, the date is set back to January, and never corrected automatically. I tried this script:
res = io.readproc('ntpd -dnq -p 0.ch.pool.ntp.org 2>&1')
log(res)
This is the result:
* string: ntpd: bad address '0.ch.pool.ntp.org'
ntpd: could not resolve peer 0.ch.pool.ntp.org, skipping
Alarm clock
The ntp-client is set up like this
0.europe.pool.ntp.org
1.europe.pool.ntp.org
2.europe.pool.ntp.org
3.europe.pool.ntp.org
Is there a way to solve this problem?
RE: NTP Problem - admin - 22.12.2016
Do you have DNS and gateway configured. Try pinging one of the NTP servers from the System Config