22.12.2016, 08:31
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?
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?