On Tuesday, January 31, 2017 at 3:36:20 AM UTC-5, Isabell Cowan wrote:
>
> I've been trying all do to set up MCollective on my puppet cluster. No
> matter what I do, I can't seem to get the MCollective server to connect.
> The MCollective server(s) are running mostly on Ubnutu Xenial. The
> A
Thank you! I opened a ticket earlier as well after posting this
(https://tickets.puppetlabs.com/browse/MCO-722) - I didn't see the two that
you posted.
(In the meantime, I'll be trying to work around by installing from source
into the 'libdir' if I can.)
On Friday, September 4, 2015 at 8:15:1
There are some jira tickets on this;
https://tickets.puppetlabs.com/browse/MCOP-516
https://tickets.puppetlabs.com/browse/MCOP-529
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it
Nice one :)
Think the MCO plugins where forgotten with the new puppet-agent setup, the
plugin documentation still refers to the non-puppetlabs directories.
On Tuesday, September 1, 2015 at 12:34:08 AM UTC+2, Chad Thompson wrote:
> To all:
>
> This is hopefully a simple question:
>
> Prior to
I have a PE 3.7 master running on a Red Hat Enterprise Linux 6 (RHEL6)
server and PE 3.7 agents running on a Windows7 (64-bit) box and a RHEL5
(32-bit) box. The agent for the Master is the only one that reports so far.
So far, the agent on the RHEL5 box has not reported at all.
However, the Wi
The underlying mcollective only bumped from 2.5 to 2.6 so it should be
compatible. Could you show some logs, try restarting the mco daemon...
Also, can you try updating one agent to see if it shows up?
On Tuesday, November 11, 2014 5:52:20 PM UTC-8, Vadym Chepkov wrote:
>
> Hi,
>
> I just instal
Example of external fact that not worked:
#!/bin/bash
role=`/usr/bin/aws ec2 describe-tags --filters
"Name=resource-id,Values=
> Hello
>
> I met following issue with mcollective puppet agent.
>
> I have custom fact that read tags from AWS cli and transform them to facts.
>
> Facter.add("role") do
I've did more checks. I've updated aws api. Now command looks like:
aws ec2 describe-tags --filters "Name=resource-id,Values=" |
grep Role | /bin/cut -f5
Custom and external facts with this string still not works. Facter see it's
ok, but mcollective - doesn't.
I've created cronjob that run this
To get the agent, you need to install mcollective-service-agent as well,
not just mcollective-service-common. Don't forget to restart the
mcollective daemon after installing.
On Thursday, October 10, 2013 2:34:07 AM UTC-7, Vincent Nawrocki wrote:
>
> Hi all !
>
> I'm working on mcollective for a
Was there ever a solution to this issue?
I appear to be having a similar (if not the same) issue:
By adding some debug code to client.rb, it appears that the replies I'm
getting have no requestid at all.
< Log.warn("Ignoring a message that did not pass security
validations")
---
>
Anybody else had any luck solving this? I've tried on 3 separate boxes now
all seem to suffer the same problem, and the logs are somewhat unhelpful is
tracking down why this is occurring.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsu
I've been having the same issue with my new MCollective setup and a quick
look in the client.rb file reveals this function on the line 99 area:
raise(MsgDoesNotMatchRequestID, "Message reqid #{requestid} does not match
our reqid #{reply.requestid}") unless reply.requestid == requestid
rescue S
Had the same problem, but worked when i have commented out path.
filebucket { 'main':
server => 'learn.localdomain',
#path => false,
}
and it was only one time weird, then i uncommented it out and worked fine
filebucket { 'main':
server => 'learn.localdomain',
path => false,
}
Dont
I encountered the same exactly problem.
The reason for my case is that the error was caused by the /etc/hosts.
The agent node's /etc/hosts didn't contain the master node's host name,
although I added its IP named puppet in /etc/hosts before.
On Tuesday, August 21, 2012 7:46:52 PM UTC-4,
Thanks, Nick!
Worked perfectly!
On Fri, Feb 1, 2013 at 4:32 PM, Nick Fagerlund <
nick.fagerl...@puppetlabs.com> wrote:
> You've gotta:
>
>- Set a fact source
>- Configure that fact source
>- Make sure that fact source has access to good data
>
> By default, mcollective is using the
You've gotta:
- Set a fact source
- Configure that fact source
- Make sure that fact source has access to good data
By default, mcollective is using the 'yaml' fact source, which is looking
for a file that may not exist and which may not have good data in it.
Check the instructions her
- Original Message -
> From: "Keith Burdis"
> To: "puppet-users"
> Sent: Friday, February 1, 2013 12:40:17 PM
> Subject: Re: [Puppet Users] Re: mcollective puppetd plugin does not work
>
> I can't check at the moment but shouldn't that b
I can't check at the moment but shouldn't that be 'mco puppet runonce fqdn=
puppet.example.net' ?
- Keith
On 1 February 2013 11:23, wrote:
> Hey i have installed mcollective server cleint and puppet master, agent
> successfully. I have also installed puppet agent plugin. But when i run
> mco
Hey i have installed mcollective server cleint and puppet master, agent
successfully. I have also installed puppet agent plugin. But when i run
mco puppet runonce
* [ > ] 2 / 2
Finished processing 2 / 2 hosts in 1093.05 ms
This comma
Any reply to my questions is hugely appreciated..
On Tuesday, December 6, 2011 4:19:46 PM UTC+5:30, Jens Braeuer wrote:
>
> Hi everyone,
>
> I run MCollective 1.2.1 together with ActiveMQ 5.5 under Scientific Linux
> 6.1 on Amazon EC2. Overall it works like a
> charm, but sometimes (eg. 1/30) dis
uot;
>> To: puppet-users@googlegroups.com
>> Sent: Monday, July 30, 2012 4:24:37 PM
>> Subject: Re: [Puppet Users] Re: mcollective puppetd plugin does not work
>>
>> wired, I installed the service plugin on the puppet master and a node
>> ca
- Original Message -
> From: "Hai Tao"
> To: puppet-users@googlegroups.com
> Sent: Monday, July 30, 2012 4:24:37 PM
> Subject: Re: [Puppet Users] Re: mcollective puppetd plugin does not work
>
> wired, I installed the service plugin on the puppet mast
wired, I installed the service plugin on the puppet master and a node
called nodeA, however,
# mco service sshd -I nodeA status
| [ > ] 0 / 1
service summary
Nodes: 1 / 0
Statuses: No responses received
The agent enable/disable is documented in the output of 'puppet help agent' as
well as here:
http://docs.puppetlabs.com/man/agent.html
Your output of 'puppet agent --server=puppet --test --noop' shows that you have
a 'puppetdlock' file (in /var/lib/puppet/state by default), but that puppet is
This makes sense and is interesting. I was suspecting disable means
turning off in chkconfig, but it is not as I checked.
# puppet agent --server=puppet --test --noop
notice: Run of Puppet configuration client already in progress; skipping
so can you explain what "administratively disables" mean,
On Monday, July 30, 2012 12:17:33 AM UTC-4, Hai wrote:
> I used the puppetd plugin to disable the puppet service on a node,
> however the puppet is still running on the node. Can someone explain
> why?
>
> # mco puppetd -I test-01 disable
>
> * [ ==
- Original Message -
> From: "Matt Warren"
> To: "Puppet Users"
> Sent: Tuesday, March 20, 2012 1:47:46 PM
> Subject: [Puppet Users] Re: mcollective bits
>
> On Mar 19, 1:45 pm, Douglas Garstang wrote:
> > I've always found the
On Mar 19, 1:45 pm, Douglas Garstang wrote:
> I've always found the mcollective docs
> athttp://docs.puppetlabs.com/mcollective/reference/basic/gettingstarted...
> very confusing.
>
> What _exactly_ goes on the client (i.e. the remote system)? The docs
> talk about editing both the server.cfg and
I've not used it, but this looks to fit the bill:
https://github.com/joemiller/shellcmd-agent
Justin
On Feb 21, 9:46 am, Kenneth Lo wrote:
> We've been using mcollective primarily for coordinate service restart across
> nodes as well as facts-finding, which are all well and good.
>
> One thing
On Mon, Jan 24, 2011 at 3:23 AM, eshamow wrote:
> The Fedora 13 SRPMs backport pretty easily, and you get the advantage
> of Ruby 1.8.6.
>
> -Eric
>
Sure, but for those who don't want to replace/break the internals of ruby on
rhel4... :)
>
> On Jan 22, 11:32 am, Ohad Levy wrote:
> > On Sat, Ja
The Fedora 13 SRPMs backport pretty easily, and you get the advantage
of Ruby 1.8.6.
-Eric
On Jan 22, 11:32 am, Ohad Levy wrote:
> On Sat, Jan 22, 2011 at 12:59 PM, R.I.Pienaar wrote:
> > hey,
>
> > - Original Message -
> > > Is their a mcollective rpm for rhel4? If not, is their a src
On Thu, 2010-05-06 at 20:29 -0400, Eric Shamow wrote:
> Matt,
>
> Really great posts -- you've inspired me to take a crack at MCollective.
Thanks Eric,
Let us know how you get on!
M.
>
> -Eric
>
>
> On Thu, May 6, 2010 at 4:11 AM, Matt Wallace
> wrote:
> > On Wed, 2010-05-05 at 23:31 -0700
Matt,
Really great posts -- you've inspired me to take a crack at MCollective.
-Eric
On Thu, May 6, 2010 at 4:11 AM, Matt Wallace
wrote:
> On Wed, 2010-05-05 at 23:31 -0700, donavan wrote:
>> > 2000 nodes certainly is within my goals with the design, that said there
>> > has not been such a b
On Wed, 2010-05-05 at 23:31 -0700, donavan wrote:
> > 2000 nodes certainly is within my goals with the design, that said there
> > has not been such a big deploy.
>
> We've got 500+ nodes on mcollective currently. Nothing special as far
> as setup, a few of the contrib agents and few more in hous
> 2000 nodes certainly is within my goals with the design, that said there has
> not been such a big deploy.
We've got 500+ nodes on mcollective currently. Nothing special as far
as setup, a few of the contrib agents and few more in house agents.
Nodes are primarily split between two buildings co
35 matches
Mail list logo
