Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Ntp daemon operates inside vrouter namespace

root@node-2:~# ip netns exec vrouter netstat -lpen --udp | grep ntpd
udp        0      0 240.1.0.4:123           0.0.0.0:*                           0          71394       27631/ntpd
udp        0      0 192.168.0.1:123         0.0.0.0:*                           0          71392       27631/ntpd
udp        0      0 172.16.0.2:123          0.0.0.0:*                           0          71390       27631/ntpd
udp        0      0 240.0.0.6:123           0.0.0.0:*                           0          71388       27631/ntpd
udp        0      0 127.0.0.1:123           0.0.0.0:*                           0          71386       27631/ntpd
udp        0      0 0.0.0.0:123             0.0.0.0:*                           0          71380       27631/ntpd

You should run ntpq in the context of this namespace:

root@node-2:~# ip netns exec vrouter ntpq -c lpeer 127.0.0.1
remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 pob01.aplu.fr   .INIT.          16 u    - 1024    0    0.000    0.000   0.000
+fr1.tomhek.net  95.81.173.8      3 u   31   64  377    0.665    0.275   0.085
*fairy.mattnordh 200.98.196.212   2 u   44   64  377   90.178   -0.979   0.148

When you used standard init script to restart ntpd (which you should avoid), daemon start out of the namespace and you was able to use ntpq from cmdline. Instead you can do:

root@node-2:~# crm resource restart p_ntp
INFO: ordering p_ntp to stop
waiting for stop to finish .. done
INFO: ordering p_ntp to start