- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
How do I resolve clock offset issue?
Created ‎07-01-2014 02:34 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I get following health issue.
The host's NTP service did not respond to a request for the clock offset.
How do I resolve it?
Thanks,
Kewal
Created ‎06-17-2015 08:54 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, the problem was at the Firewall , one of the rules was changes ;
after the problem was fix the NTP was updated.
Thanks so much for your help
Created ‎07-01-2014 06:08 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just saw this after an office move. The servers were offline for a while.
This is what I did for our CentOS Linux servers (similar, but not the same, steps would work for Ubuntu/Debian):
* verified/updated the /etc/ntp.conf file to be the same across the cluster
* stopped the ntp daemon: /etc/init.d/ntpd stop
* connected to the ntp server named in the ntp.conf file: ntpupdate <ntp_server>
* started the ntp daemon: /etc/init.d/ntpd start
* added ntpd to the startup manager: chkconfig add ntpd
* set ntpd to start in default reunlevels: chkconfig ntpd on
This cleared the offset issue. If this doesn't do it for you, you might also have to look into drift, or dig deeper into the time synchronization.
Created ‎07-01-2014 07:44 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks a lot for you detailed answer.
I deleted the cluster and rebuilt it from scratch. Now, it is working fine.(Fingers crossed)
But, It seems, your procedure would definitely solve the problem.
Created ‎02-04-2015 11:27 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for your detailed answer. it helped me!
I had to repeat the step 4 and 5 twice; but it fixed my issue. I'm keeping the fingers crossed now! 🙂
Created on ‎02-21-2015 09:51 PM - edited ‎02-21-2015 09:52 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Many thanks. I followed these steps and it fixed my clock offset issue.
* verified/updated the /etc/ntp.conf file to be the same across the cluster
* stopped the ntp daemon: /etc/init.d/ntpd stop
* connected to the ntp server named in the ntp.conf file: ntpupdate <ntp_server>
* started the ntp daemon: /etc/init.d/ntpd start
* added ntpd to the startup manager: chkconfig add ntpd
* set ntpd to start in default reunlevels: chkconfig ntpd on
Created ‎06-10-2015 11:55 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
i got the next:
$sudo service ntp stop
* Stopping NTP server ntpd [ OK ]
root@cluster-01:~# sudo ntpdate ntp.ubuntu.com
11 Jun 06:47:14 ntpdate[29757]: no server suitable for synchronization found
i try to do it with the with NTP .. instead NTPD
....
Created ‎06-11-2015 09:24 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Created ‎06-11-2015 09:36 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi nauseous,
apprently, the problem is at my firewall, where I can't ping my gateway neither other sites out of my network.
so that's way i can't see it.
Created ‎06-17-2015 06:12 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
If firewall is the problem you can ask network admin to open add chains to that specific URL . or the other way you can set up your own NTP server within that network itself.
Thanks,
Sathish
Sathish (Satz)
Created ‎06-17-2015 08:47 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
point to most likely within the firewall.
