How do I resolve clock offset issue?

[#1 · Accepted solution]

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

[#2]

Thanks for the help 

just 2 steps my issue is resolved might usefull to other 

i tried

/etc/init.d/ntpd start

/etc/init.d/ntpd stop

it works for me

[#3]

Thanks, it works for me too

[#4]

I have installed ntpd on all 8 nodes, checked the ntp.conf file across the nodes, its same..

So i stopped the ntpd and tried running the ntpupdate command and its saying command not found.. So could you please  explain this step?

-> connected to the ntp server named in the ntp.conf file: ntpupdate <ntp_server>

[#5]

There is no ntpupdate command.

You can update ntp by typing

# ntpdate -u {Main node sync'ed to NTP server IP address or Domain name
here}

Example

# ntpdate -u domains.ntp.com

OR

# ntpdate -u 192.168.0.2

You should only have 1 node announcing NTP and other nodes getting time
from main node.

[#6]

Thanks a lot.. :)

[#7]

I found this article which was super helpful.

http://www.linuxsecrets.com/categories/linux-performance/performance-tips/redhat-prerequisites-bench...

[#8]

I had to restart Cloudera SCM Agent to fix this alert after NTP reconfiguration:

service cloudera-scm-agent restart

[#9]

I use puppet and foreman to configure each system the same for all ntp
clients to a central ntp server.

Great information here
http://www.linuxsecrets.com/blog/4tutorial-and-install-howto/2014/06/26/906-how-to-install-and-confi...