Hmm.. I try choria, seem like it tries to install mcollective to roots..
this will not work in our environment. This is too much works. We only need
a tool to actually tell puppet to do update once there is changes to the
manifest. any other tools better than mcollective.
On Friday, August 4,
What do you mean to root? To trigger puppet you need to be running as root.
---
R.I.Pienaar
> On 7 Aug 2017, at 09:00, Muhammad Al-Iman Mohd Zain wrote:
>
> Hmm.. I try choria, seem like it tries to install mcollective to roots.. this
> will not work in our environment. This is too much works
okay, I found my problem.. it cause by time drift, the time between the
server and client was huge.. so the msg was dropped.
thanks all.
On Friday, August 4, 2017 at 11:22:45 PM UTC+8, Muhammad Al-Iman Mohd Zain
wrote:
>
> Hi all.. Thank you for having me here. I need some help configuring new
We do not run our puppet instance in root. Maybe because of some security
concern or just our policy. so puppet and mco will be running on normal
user. for now, it is working again.. thanks to the clock sync.. my bad..
btw.. I dont see any debug info saying msg is dropped when time is correct.
You should have seen a message like:
"Message #{description} created at #{msgtime} is #{msg_age} seconds
old, TTL is #{ttl}. Rejecting message."
---
R.I.Pienaar
> On 8 Aug 2017, at 03:36, Muhammad Al-Iman Mohd Zain wrote:
>
> We do not run our puppet instance in root. Maybe because
