About damon.jones

damon.jones · ‎11-05-2015

Yes, this helped me to better understand the issue but in the end we had a bad NTP server. I appreciate the help.

damon.jones · ‎08-28-2015

I think you may have found my issue. The output from running "ntpdc -np" does not have an entry with an asterisk. Do you know what the asterisk means? Thanks. $ ntpdc -np remote local st poll reach delay offset disp ======================================================================= =192.168.1.44 192.168.1.28 4 1024 377 0.00110 0.009895 0.18616 =192.168.1.43 192.168.1.28 4 1024 377 0.00099 0.004189 0.18646

damon.jones · ‎08-24-2015

Cloudera Community, I have two different Cloudera Manager(CM) managed clusters that I upgraded from 5.3.3 to (5.4.1 and 5.4.3). On both clusters I get random "Clock Offset Bad" messages thoughout the day. I checked the times on all nodes and they are all in sync. I also checked the NTP configuration and it appears to be accurate. I did not have these issues when running 5.3.3. I was wondering how the CM agent checks for bad offset clock? Is there something that changed between 5.3.3 and 5.4.x? I'm running: Cluster 1 OS: Redhat Enterprise 6.6 CDH: 5.4.1 CM: 5.4.1 Cluster 2 OS: Redhat Enterprise 6.6 CDH: 5.4.3 CM: 5.4.3 Thanks.

Online	Offline
Last Visited	‎09-03-2015 02:41 PM

Member Since	‎02-12-2015 03:42 PM
Last Visited	‎09-03-2015 02:41 PM
Posts	4
Kudos received	1

Cloudera Community

Re: Cloudera 5.4.x cluster randomly reports "Clock...

Re: Cloudera 5.4.x cluster randomly reports "Clock...

Cloudera 5.4.x cluster randomly reports "Clock Off...