Ask Your Question
0

Why mco ping only work one time and then client doens't appear anymore

asked 2014-08-08 09:49:12 -0500

dmo54 gravatar image

Hi everybody, I've installed a puppet master with four clients (included itself on CentOS 6.5) : one Debian, two CentOS 6.5 and one CentOS 5.2. Everything work fine, including "live management" on Console, except that after maybe 30 seconds after boot, the client on CentOS 5.2 is not responding at "mco ping" and accordingly in not seen in the "live management" discovery's tool (it is the only one). Whereas it is possible to make a "puppet agent -t" without problem on it, it applies the catalogue each time !! This client is not really loaded, I don't understand why "mco ping" fails on it after reboot and 30 seconds, the only difference I see with the others CentOS servers is an older release of OS. Does somebody have a clue regarding this issue ? Thanks in advance. regards Denis

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2014-08-12 07:03:06 -0500

dmo54 gravatar image

Forget it I found the problem, timestamp of the clientserver was changing by any package I don't know even if ntp module was loaded. Solution is usage of "ntpdate" in crontab to synchronize on regular basis.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2014-08-08 09:49:12 -0500

Seen: 235 times

Last updated: Aug 12 '14