NTP Server?

N

NICK_k

New Member
Sep 7, 2020
11
1
1
44
Can Procmox MG set the NTP SERVER to point to the internal server? In which file to modify?

Code: 
Oct 21 10:24:14 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 175.98.194.14:123 (0.debian.pool.ntp.org).
Oct 21 10:24:25 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 220.132.100.157:123 (0.debian.pool.ntp.org).
Oct 21 10:24:35 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 183.177.72.201:123 (0.debian.pool.ntp.org).
Oct 21 10:24:45 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 60.248.114.17:123 (0.debian.pool.ntp.org).
Oct 21 10:24:55 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 118.163.74.161:123 (1.debian.pool.ntp.org).
Oct 21 10:25:06 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 59.125.122.217:123 (1.debian.pool.ntp.org).
Oct 21 10:25:16 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 162.159.200.1:123 (1.debian.pool.ntp.org).
Oct 21 10:25:26 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 1.34.13.89:123 (1.debian.pool.ntp.org).
Oct 21 10:25:36 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 206.75.147.25:123 (2.debian.pool.ntp.org).
Oct 21 10:25:47 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 192.241.146.233:123 (2.debian.pool.ntp.org).
Oct 21 10:25:57 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 193.4.58.44:123 (2.debian.pool.ntp.org).
Oct 21 10:26:07 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 185.51.192.34:123 (2.debian.pool.ntp.org).
Oct 21 10:26:18 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 162.159.200.123:123 (3.debian.pool.ntp.org).
Oct 21 10:26:28 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 60.248.114.17:123 (3.debian.pool.ntp.org).
Oct 21 10:26:38 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 175.98.194.14:123 (3.debian.pool.ntp.org).
Oct 21 10:26:48 ProxmoxMG systemd-timesyncd[6708]: Timed out waiting for reply from 49.213.184.242:123 (3.debian.pool.ntp.org).
 
NICK_k said:
Can Procmox MG set the NTP SERVER to point to the internal server? In which file to modify?
Click to expand...
PMG is based on Debian/Linux and as far as ntp configuration is concerned you can configure it like any Debian system - see e.g. https://www.digitalocean.com/community/tutorials/how-to-set-up-time-synchronization-on-debian-10

from the posted logs it seems your system uses systemd-timesyncd for synchronization - the NTP servers for this are configured in /etc/systemd/timesyncd.conf (see `man timesyncd`)

I hope this helps!
 
I checked the linked article you provided, but the value of system clock synchronized is no. How can I solve it?

Code: 
root@ProxmoxMG2:~# timedatectl
               Local time: Wed 2020-10-21 16:56:09 CST
           Universal time: Wed 2020-10-21 08:56:09 UTC
                 RTC time: Wed 2020-10-21 08:56:10
                Time zone: Asia/Taipei (CST, +0800)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no
 
  • Like
Reactions: mikeinnyc
did you update /etc/systemd/timesyncd.conf to contain your internal ntp-server?

if yes
try running:
Code: 
timedatectl set-ntp true
systemctl status systemd-timesyncd.service
timedatectl timesync-status
and post the output
 
I have modified /etc/systemd/timesyncd.conf, and it contains internal ntp-server.
The command has been executed and the output is as follows.

Code: 
root@ProxmoxMG2:~# timedatectl set-ntp true
root@ProxmoxMG2:~# systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor pre
  Drop-In: /usr/lib/systemd/system/systemd-timesyncd.service.d
           └─disable-with-time-daemon.conf
   Active: active (running) since Wed 2020-10-21 13:25:23 CST; 3h 45min ago
     Docs: man:systemd-timesyncd.service(8)
 Main PID: 552 (systemd-timesyn)
   Status: "Idle."
    Tasks: 2 (limit: 4667)
   Memory: 1.4M
   CGroup: /system.slice/systemd-timesyncd.service
           └─552 /lib/systemd/systemd-timesyncd

Oct 21 13:25:23 ProxmoxMG2 systemd[1]: Starting Network Time Synchronization...
Oct 21 13:25:23 ProxmoxMG2 systemd[1]: Started Network Time Synchronization.
...skipping...
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor pre
  Drop-In: /usr/lib/systemd/system/systemd-timesyncd.service.d
           └─disable-with-time-daemon.conf
   Active: active (running) since Wed 2020-10-21 13:25:23 CST; 3h 45min ago
     Docs: man:systemd-timesyncd.service(8)
 Main PID: 552 (systemd-timesyn)
   Status: "Idle."
    Tasks: 2 (limit: 4667)
   Memory: 1.4M
   CGroup: /system.slice/systemd-timesyncd.service
           └─552 /lib/systemd/systemd-timesyncd

Oct 21 13:25:23 ProxmoxMG2 systemd[1]: Starting Network Time Synchronization...
Oct 21 13:25:23 ProxmoxMG2 systemd[1]: Started Network Time Synchronization.
~
~
~
~
~
~
~
~

root@ProxmoxMG2:~#
root@ProxmoxMG2:~#
root@ProxmoxMG2:~# timedatectl timesync-status
       Server: 172.23.5.1 (172.23.5.1)
Poll interval: 34min 8s (min: 32s; max 34min 8s)
 Packet count: 0
root@ProxmoxMG2:~#
 
NICK_k said:
Packet count: 0
Click to expand...
seems there is no reply from 172.23.5.1 - does the ntp daemon run there? are there any firewall policies in place which might prevent it from answering?

else check with tcpdump whether ntp-packets leave PMG and whether response arrive
 
You must log in or register to reply here.
Top Bottom