VMware Cloud Community
russjar
Enthusiast
Enthusiast
Jump to solution

NTP failing

Hi,

I have configured the NTP as per this documentation http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1339&slice...

however when I restart the NTPD I get the following (see below). I have followed the configuration to the tee but it aint workin' and I don't know why...

Shutting down ntpd: \[ OK ]

ntpd: Synchronizing with time server: \[FAILED]

Starting ntpd: \[ OK ]

Thanks...

VCP,MCSE NT4/W2k/W2k3, MCSA W2k3
Reply
0 Kudos
1 Solution

Accepted Solutions
Texiwill
Leadership
Leadership
Jump to solution

Hello,

If you can not resolve the name to an IP then there is a name resolution error and the contents of /etc/resolv.conf may be suspect. Verify that the contents of this file point to a valid nameserver. Ensure that nameserver can resolve the host in question.

Using the VI Client you can verify there is a nameserver listed. It should match what is in /etc/resolv.conf.

Best regards,

Edward

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill

View solution in original post

Reply
0 Kudos
8 Replies
russjar
Enthusiast
Enthusiast
Jump to solution

I have an update...

ntpd_initres\[1939]: couldn't resolve `0.oceania.pool.ntp.org', giving up on it

ntpd_initres\[1939]: couldn't resolve `1.oceania.pool.ntp.org', giving up on it

ntpd_initres\[1939]: couldn't resolve `2.oceania.pool.ntp.org', giving up on it

Name resolution but what is causing this?

VCP,MCSE NT4/W2k/W2k3, MCSA W2k3
Reply
0 Kudos
Dave_Mishchenko
Immortal
Immortal
Jump to solution

If your network / firewalls are setup to allow this, you should be able to ping these hosts from the console / ssh of your ESX host? Since you can't resolve the addresses, you might want to go to Configuration \ DNS and Routing and check that your primary and alternate DNS servers are set correctly.

Reply
0 Kudos
russjar
Enthusiast
Enthusiast
Jump to solution

Thanks for the reply...

I'm thinking you would need port 123 open for NTP, DNS is correctly configured and I'm sure I have had this working before. I will have to check with comms to see what's going on...

Is there a work-around?

VCP,MCSE NT4/W2k/W2k3, MCSA W2k3
Reply
0 Kudos
Dave_Mishchenko
Immortal
Immortal
Jump to solution

You will have to open the port for NTP as part of the setup. Go to configuration \ security profile and then click on the properties for the firewall. You'll see an entry for NTP client.

Are you able to ping these hosts from the server?

Reply
0 Kudos
russjar
Enthusiast
Enthusiast
Jump to solution

Yeah I have opened up port 123 on the server via the command line "esxcfg-firewall --enableService ntpClient"

VCP,MCSE NT4/W2k/W2k3, MCSA W2k3
Reply
0 Kudos
russjar
Enthusiast
Enthusiast
Jump to solution

And cannot ping via the FQDN...

VCP,MCSE NT4/W2k/W2k3, MCSA W2k3
Reply
0 Kudos
patk
Contributor
Contributor
Jump to solution

Try pinging the 0.oceania.pool.ntp.org[/b] NTP pool by using its IP addresss:

192.189.54.17

This would tell us if traffic is routeable to that location from your host. If you are able to ping you may consider adding a host file entry for one of the NTP pools while you work on root cause. Most likely the problem would be with name resolution at some level in your environment.

Reply
0 Kudos
Texiwill
Leadership
Leadership
Jump to solution

Hello,

If you can not resolve the name to an IP then there is a name resolution error and the contents of /etc/resolv.conf may be suspect. Verify that the contents of this file point to a valid nameserver. Ensure that nameserver can resolve the host in question.

Using the VI Client you can verify there is a nameserver listed. It should match what is in /etc/resolv.conf.

Best regards,

Edward

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
Reply
0 Kudos