Questions[time-server](server)

We have restricted NTP to listen only eth0 and rest should will ignore. However we can see that after making changes in ntp.conf it is trying to listen broadcast and failing to bind address with unexpected error.

ntpd[89217]: ./../lib/isc/unix/ifiter_ioctl.c:617: unexpected error:
ntpd[89217]: eth2:6: getting broadcast address: Cannot assign requested address
ntpd[89217]: i/o error on routing socket No buffer space available – disabling
ntpd[5410]: ./../lib/isc/unix/ifiter_ioctl.c:617: unexpected error:
ntpd[5410]: eth3.1238:0: getting broadcast address: Cannot assign requested address
ntpd[5410]: ntpd exiting on signal 15
ntpd[1508]: ntpd exiting on signal 15

Below is the ntp.conf from customer's server :-

cat ntp.conf

fudge 127.127.1.0 stratum 10

Authentication stuff

keys /etc/ntp.keys
path for keys file
trustedkey 1
define trusted keys
requestkey 1
server 172.23.5.8 iburst
server 172.23.5.9 iburst
restrict 172.23.5.8
restrict 172.23.5.9
key (7) for accessing server variables
controlkey 15 # key (6) for accessing server variables
extra lines to fix issue about NTP Daemon
interface listen eth0
interface ignore wildcard

This one is /var/lib/NTP log file you can see.

27 Sep 10:30:17 ntpd[89217]: ./../lib/isc/unix/ifiter_ioctl.c:617: unexpected error:
27 Sep 10:30:17 ntpd[89217]: eth2:6: getting broadcast address: Cannot assign requested address
27 Sep 10:30:17 ntpd[89217]: i/o error on routing socket No buffer space available - disabling
11 Oct 13:12:46 ntpd[5410]: ./../lib/isc/unix/ifiter_ioctl.c:617: unexpected error:
11 Oct 13:12:46 ntpd[5410]: eth3.1238:0: getting broadcast address: Cannot assign requested address
11 Oct 13:13:23 ntpd[5410]: ./../lib/isc/unix/ifiter_ioctl.c:617: unexpected error:
11 Oct 13:13:23 ntpd[5410]: eth3.1277:0: getting broadcast address: Cannot assign requested address
11 Oct 13:13:41 ntpd[5410]: i/o error on routing socket No buffer space available - disabling
13 Oct 21:11:05 ntpd[5410]: ntpd exiting on signal 15
13 Oct 20:50:18 ntpd[1508]: ntpd exiting on signal 15
13 Oct 22:49:52 ntpd[113345]: LOCAL(0) 8011 81 mobilize assoc 35168
13 Oct 22:49:52 ntpd[113345]: 172.23.5.8 8011 81 mobilize assoc 35169
13 Oct 22:49:52 ntpd[113345]: 172.23.5.9 8011 81 mobilize assoc 35170
13 Oct 22:49:52 ntpd[113345]: 0.0.0.0 c016 06 restart
13 Oct 22:49:52 ntpd[113345]: 0.0.0.0 c012 02 freq_set kernel -22.705 PPM
13 Oct 20:49:53 ntpd[113345]: LOCAL(0) 8024 84 reachable
13 Oct 20:49:53 ntpd[113345]: LOCAL(0) 963a 8a sys_peer
13 Oct 20:49:53 ntpd[113345]: 0.0.0.0 c515 05 clock_sync
13 Oct 20:49:54 ntpd[113345]: 172.23.5.8 8024 84 reachable
13 Oct 20:49:55 ntpd[113345]: 172.23.5.9 8024 84 reachable
13 Oct 20:50:57 ntpd[113345]: 172.23.5.9 963a 8a sys_peer
13 Oct 20:53:18 ntpd[113345]: LOCAL(0) 961a 8a sys_peer
13 Oct 20:59:48 ntpd[113345]: ntpd exiting on signal 15
13 Oct 22:59:40 ntpd[122930]: LOCAL(0) 8011 81 mobilize assoc 21051
13 Oct 22:59:40 ntpd[122930]: 172.23.5.8 8011 81 mobilize assoc 21052
13 Oct 22:59:40 ntpd[122930]: 172.23.5.9 8011 81 mobilize assoc 21053
13 Oct 22:59:40 ntpd[122930]: 0.0.0.0 c016 06 restart
13 Oct 22:59:40 ntpd[122930]: 0.0.0.0 c012 02 freq_set kernel -22.705 PPM
13 Oct 20:59:41 ntpd[122930]: LOCAL(0) 8024 84 reachable
13 Oct 20:59:41 ntpd[122930]: LOCAL(0) 963a 8a sys_peer
13 Oct 20:59:41 ntpd[122930]: 0.0.0.0 c515 05 clock_sync
13 Oct 21:00:39 ntpd[122930]: ntpd exiting on signal 15
13 Oct 23:00:39 ntpd[124181]: LOCAL(0) 8011 81 mobilize assoc 30350
13 Oct 23:00:39 ntpd[124181]: 172.23.5.8 8011 81 mobilize assoc 30351
13 Oct 23:00:39 ntpd[124181]: 172.23.5.9 8011 81 mobilize assoc 30352
13 Oct 23:00:39 ntpd[124181]: 0.0.0.0 c016 06 restart
13 Oct 23:00:39 ntpd[124181]: 0.0.0.0 c012 02 freq_set kernel -22.705 PPM
13 Oct 21:00:40 ntpd[124181]: LOCAL(0) 8024 84 reachable
13 Oct 21:00:40 ntpd[124181]: LOCAL(0) 963a 8a sys_peer
13 Oct 21:00:40 ntpd[124181]: 0.0.0.0 c515 05 clock_sync
13 Oct 21:00:41 ntpd[124181]: 172.23.5.8 8024 84 reachable
13 Oct 21:00:42 ntpd[124181]: 172.23.5.9 8024 84 reachable
13 Oct 21:01:44 ntpd[124181]: 172.23.5.9 963a 8a sys_peer
13 Oct 21:05:11 ntpd[124181]: LOCAL(0) 961a 8a sys_peer
13 Oct 21:16:23 ntpd[124181]: i/o error on routing socket No buffer space available - disabling
13 Oct 21:28:42 ntpd[124181]: ntpd exiting on signal 15
13 Oct 23:32:35 ntpd[5438]: LOCAL(0) 8011 81 mobilize assoc 54508
13 Oct 23:32:35 ntpd[5438]: 172.23.5.8 8011 81 mobilize assoc 54509
13 Oct 23:32:35 ntpd[5438]: 172.23.5.9 8011 81 mobilize assoc 54510
13 Oct 23:32:35 ntpd[5438]: 0.0.0.0 c016 06 restart
13 Oct 23:32:35 ntpd[5438]: 0.0.0.0 c012 02 freq_set kernel -22.705 PPM
13 Oct 21:32:36 ntpd[5438]: LOCAL(0) 8024 84 reachable
13 Oct 21:32:36 ntpd[5438]: LOCAL(0) 963a 8a sys_peer
13 Oct 21:32:36 ntpd[5438]: 0.0.0.0 c515 05 clock_sync
13 Oct 21:32:37 ntpd[5438]: 172.23.5.8 8024 84 reachable
13 Oct 21:32:38 ntpd[5438]: 172.23.5.9 8024 84 reachable
13 Oct 21:33:40 ntpd[5438]: 172.23.5.9 963a 8a sys_peer
13 Oct 21:37:05 ntpd[5438]: 172.23.5.8 943d 8d popcorn 0.011376 s
13 Oct 21:40:30 ntpd[5438]: 172.23.5.9 964d 8d popcorn 0.013156 s
13 Oct 21:42:12 ntpd[5438]: LOCAL(0) 8043 83 unreachable

Hope you got something.

Can any body tell me how to fix this error?

I have synced the time of my server to time.nist.gov. This server communicates with a client’s server which is also synced with time.nist.gov.

After noting that we seemed to be out of sync with the time server even after explicit syncing, I set up an hourly batch job to see if my hypothesis is correct and what is our time difference.

I set up the job on Friday and it has already checked the time 50 times. When I first checked on Friday, w32tm utility showed a difference of less than 10 milliseconds. The last check, a couple of hours ago, shows a difference of 20 second.

There have also been 9 cases (in 50 attempts) of error: 0x800705B4 which is a timeout error. The time difference seems to be increasing at the rate of 1 second every hours since Friday, 1/6/2012 5:35 PM EST

I have a Windows Server 2003 Enterprise Edition set up as a VMWare VM, the timezone is EST. Here’s my w32tm and DOS command that log the sync difference:

w32tm /stripchart /computer:time.nist.gov /samples:1 /dataonly >> D:\timedump.txt

Here are the last 4 entries:

Tracking time.nist.gov [192.43.244.18].
Collecting 1 samples.
The current time is 1/8/2012 10:35:00 AM (local time).
10:35:00, +20.3387625s

Tracking time.nist.gov [192.43.244.18].
Collecting 1 samples.
The current time is 1/8/2012 11:35:00 AM (local time).
11:35:00, +20.4854414s

Tracking time.nist.gov [192.43.244.18].
Collecting 1 samples.
The current time is 1/8/2012 12:35:00 PM (local time).
12:35:00, +20.6239407s

Tracking time.nist.gov [129.6.15.28].
Collecting 1 samples.
The current time is 1/8/2012 1:35:00 PM (local time).
13:35:00, error: 0x800705B4

I would like to load balance a group of windows 2003 servers. They are not on a domain, and I am not using active directory.

I would like the synchronize the time for these boxes.

What is the best way of doing this?

Thanks!!!

I have been trying to build and configure ntp clients and server, and used this line in the ntp.conf for the clients:

restrict default ignore

Still, I see that my client is listening on the local network interface. From the system log:

Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Listening on interface #1 wildcard, ::#123 Disabled
Listening on interface #2 vmnet8, fe80::250:56ff:fec0:8#123 Enabled
Listening on interface #3 lo, ::1#123 Enabled
Listening on interface #4 eth0, fe80::222:68ff:fe10:1529#123 Enabled
Listening on interface #5 vmnet1, fe80::250:56ff:fec0:1#123 Enabled
Listening on interface #6 lo, 127.0.0.1#123 Enabled
Listening on interface #7 eth0, 192.168.111.183#123 Enabled
Listening on interface #8 vmnet1, 172.16.139.1#123 Enabled

0-1 are disabled, which is good.

List of open ports using nmap -sUS -O 127.0.0.1:

Starting Nmap 4.53 ( http://insecure.org ) at 2009-08-03 12:25 IDT
Interesting ports on localhost (127.0.0.1):
Not shown: 3195 closed ports
PORT     STATE         SERVICE
22/tcp   open          ssh
631/tcp  open          ipp
902/tcp  open          iss-realsecure-sensor
5432/tcp open          postgres
68/udp   open|filtered dhcpc
123/udp  open|filtered ntp
5353/udp open|filtered zeroconf
Device type: general purpose
Running: Linux 2.6.X

As you can see, ntp is listening on port 123. Why?

Any ideas?

Udi

I want to sync some two dozen Linux servers which are spread all over the world. I was thinking about using NTPD, but I want to know the security implications of using it: Is there a possible vulnerability? Should I sync them to a local server and sync it manually?

Thanks,

Udi