[Puppet Users] Re: MCollective server cannot connect to ActiveMQ broker
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 > ActiveMQ broker (5.14.3) is running on Debian Stretch. I'm running puppet > 4.x on all nodes. I've used every transport connector I can thing if, and > they all fail to connect. Let me dump some log files at you. > > In mcollective.log I'm getting `Connection reset by peer`: > Any time I see "connection reset by peer", my first instinct is that there is some device in between that's breaking the traffic. Unfortunately, one of the newer "tricks" is so-called intelligent firewalls that base their rules on traffic, not ports-- so the initial connection may be allowed, but data transfer, not so much. Have you tried using nmap from the mcollective server against the 61614 port on the broker? -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/9804f683-20f4-415a-b1c2-b62e0f22546d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: MCollective Plugins - Can I Install with Puppet Collections?
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:11 AM UTC-5, Stefan Heijmans wrote: > > 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/fc435819-8287-4c62-8547-eec0ad9a249c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: MCollective Plugins - Can I Install with Puppet Collections?
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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/753e6e82-075a-4322-ad6f-12de581e699a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: MCollective Plugins - Can I Install with Puppet Collections?
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 the Puppet 4 upgrade, I was using the Puppetlabs repo to install > the Puppet agent along with MCollective and a few (puppet, service) > MCollective plugins. > > With the upgraded install using Puppet Collections (which includes the mco > binary and client/server configurations) I can no longer find the plugin > packages for MCollective. > > (See: https://docs.puppetlabs.com/mcollective/deploy/plugins.html and > the yum repositories at https://yum.puppetlabs.com/el/6.5/PC1/x86_64/ as > an example) > > Do I need to enable a different repository - or is there something else > I'm missing? > > Thanks! > > Chad > > --- > chad.o@gmail.com > -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/8ec0a990-a876-4c7e-9ed0-09ace34e36a6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: mcollective compatibility in PE 3.7
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 Windows7 box reports about 16 failures out of 88 resources and
all of the failures seem to be related to the wrong path for MCollective
defined on the server:
content change from {md5}f54bc3eab9020cf794d8c40c03198cb6
https://cm-elite311-01.web.mba.lan/reports/26# to
{md5}6c75df0f35313ca47c839caccbb07289 failed: No such file or directory -
C:/ProgramData/PuppetLabs/mcollective/etc/
plugins/mcollective/agent/puppet.ddl20141122-3488-1upfdhk.lock
The path on the Windows7 box is:
C:\Program Files\Puppet Labs\Puppet Enterprise\mcollective\etc
The help that I need is where and how to change the path that the server is
searching for.
On Tuesday, November 11, 2014 5:52:20 PM UTC-8, Vadym Chepkov wrote:
Hi,
I just installed PE3.7 and master can't see any PE3.3 mcollective nodes,
only itself.
Is there compatibility issue or some setting which can be tweaked?
Thanks,
Vadym
--
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, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/8d815162-18f6-406f-8d3c-e214ef21d638%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: mcollective compatibility in PE 3.7
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 installed PE3.7 and master can't see any PE3.3 mcollective nodes, only itself. Is there compatibility issue or some setting which can be tweaked? Thanks, Vadym -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/3799ee8e-769e-4b3c-a0b7-4ba6e30b1375%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Mcollective puppet-agent doesn't execute commands from custom facts
I've did more checks. I've updated aws api. Now command looks like:
aws ec2 describe-tags --filters Name=resource-id,Values=instance_id |
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 command and send value to file. Created
external fact that cat file and echo role=$role. Mcollective worked fine.
On Saturday, August 2, 2014 9:57:07 PM UTC+3, Maxim Nikolaev wrote:
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
setcode do
iregion = Facter.value(ec2_region)
Facter::Util::Resolution.exec(ec2-describe-tags --region #{iregion} -O
KEY -W SEC_KEY --filter \resource-id=$(ec2-metadata -i | cut -d \ \
-f2)\ --filter \key=Role\ | cut -f5 -)
end
end
When I run facter from instance aor puppet agent from instance itself -
everything working fine.
When I run pupper runnonce from mcollective server - it doesn't read this
fact and apply only common manifest.
I checked several times and found, that if I set static file with role and
use external fact like:
#!/bin/bash
role=`grep Role /etc/server_facts | awk '{print $NF}'`
echo role=$role
Mcollective works fine. If Itry to use AWS cli command in script - again
fact doesn't wrk.
Have someone met such problem with mcollective? Can someone advise?
Puppet 3.6.2
Mcollective 2.5.3
--
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, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/db88a075-bf5c-4697-be6d-cb463397c436%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Mcollective puppet-agent doesn't execute commands from custom facts
Example of external fact that not worked:
#!/bin/bash
role=`/usr/bin/aws ec2 describe-tags --filters
Name=resource-id,Values=instance_id | grep Role | /bin/cut -f5`
echo role=$role
Fact see this, but mcollective doesn't get.
On Saturday, August 2, 2014 9:57:07 PM UTC+3, Maxim Nikolaev wrote:
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
setcode do
iregion = Facter.value(ec2_region)
Facter::Util::Resolution.exec(ec2-describe-tags --region #{iregion} -O
KEY -W SEC_KEY --filter \resource-id=$(ec2-metadata -i | cut -d \ \
-f2)\ --filter \key=Role\ | cut -f5 -)
end
end
When I run facter from instance aor puppet agent from instance itself -
everything working fine.
When I run pupper runnonce from mcollective server - it doesn't read this
fact and apply only common manifest.
I checked several times and found, that if I set static file with role and
use external fact like:
#!/bin/bash
role=`grep Role /etc/server_facts | awk '{print $NF}'`
echo role=$role
Mcollective works fine. If Itry to use AWS cli command in script - again
fact doesn't wrk.
Have someone met such problem with mcollective? Can someone advise?
Puppet 3.6.2
Mcollective 2.5.3
--
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, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/a1b3b84a-a58b-46ed-8ce6-ffba7225abf5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: [mcollective] mc does not discover any nodes
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 few days and I have a problem using agents. I'm on CentOS 6.4, using activeMQ 5.8.0 and mcollective 2.2.4. I Installed the service agent using yum on the client : yum install mcollective-service-common I can see it in the doc list using mco plugin doc. But now I want to use it and nodes never respond : -- [root@poste306 puppet]# mco ping poste306.s11.pfd time=161.65 ms poste302.s11.pfd time=163.25 ms poste304.s11.pfd time=166.48 ms ping statistics 3 replies max: 166.48 min: 161.65 avg: 163.79 [root@poste306 puppet]# mco rpc service status service=httpd Discovering hosts using the mc method for 2 second(s) 0 No request sent, we did not discover any nodes. --- I don't see what's wrong. No input in the mcollective.log file. Nothing on both servers and client sides. I appreciate any help or hint about this issue. Regards, Vincent. -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: mcollective setup question
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)
---
Log.warn(Ignoring a message that did not pass security
validations: requestid #{requestid} - #{reply.requestid})
Which produces the following message when I run mco ping (or any other
command):
warn 2013/10/14 10:26:13: client.rb:99:in `rescue in receive' Ignoring a
message that did not pass security validations: requestid
8d0b3938113259a3ac7d878b365ad522 -
Looking at mcollective.log on the server (set to 'debug' level), I see the
request being processed:
D, [2013-10-14T10:26:13.237675 #12265] DEBUG -- : runnerstats.rb:49:in
`received' Incrementing total stat
D, [2013-10-14T10:26:13.237794 #12265] DEBUG -- : pluginmanager.rb:83:in
`[]' Returning cached plugin security_plugin with class
MCollective::Security::Ssl
D, [2013-10-14T10:26:13.237896 #12265] DEBUG -- : ssl.rb:222:in
`deserialize' De-Serializing using marshal
D, [2013-10-14T10:26:13.238027 #12265] DEBUG -- : ssl.rb:175:in
`validrequest?' Validating request from cert=jeg-mc
D, [2013-10-14T10:26:13.238868 #12265] DEBUG -- : runnerstats.rb:38:in
`validated' Incrementing validated stat
D, [2013-10-14T10:26:13.238958 #12265] DEBUG -- : ssl.rb:222:in
`deserialize' De-Serializing using marshal
D, [2013-10-14T10:26:13.239067 #12265] DEBUG -- : pluginmanager.rb:83:in
`[]' Returning cached plugin security_plugin with class
MCollective::Security::Ssl
D, [2013-10-14T10:26:13.239186 #12265] DEBUG -- : pluginmanager.rb:83:in
`[]' Returning cached plugin security_plugin with class
MCollective::Security::Ssl
D, [2013-10-14T10:26:13.239316 #12265] DEBUG -- : base.rb:153:in
`validate_filter?' Message passed the filter checks
D, [2013-10-14T10:26:13.239487 #12265] DEBUG -- : runnerstats.rb:26:in
`passed' Incrementing passed stat
D, [2013-10-14T10:26:13.239557 #12265] DEBUG -- : runner.rb:80:in
`agentmsg' Handling message for agent 'discovery' on collective
'mcollective'
D, [2013-10-14T10:26:13.239624 #12265] DEBUG -- : agents.rb:119:in
`dispatch' Dispatching a message to agent discovery
D, [2013-10-14T10:26:13.239713 #12265] DEBUG -- : pluginmanager.rb:83:in
`[]' Returning cached plugin discovery_agent with class
MCollective::Agent::Discovery
D, [2013-10-14T10:26:13.239782 #12265] DEBUG -- : activemq.rb:233:in
`receive' Waiting for a message from ActiveMQ
D, [2013-10-14T10:26:13.240053 #12265] DEBUG -- : pluginmanager.rb:83:in
`[]' Returning cached plugin security_plugin with class
MCollective::Security::Ssl
D, [2013-10-14T10:26:13.240360 #12265] DEBUG -- : pluginmanager.rb:83:in
`[]' Returning cached plugin security_plugin with class
MCollective::Security::Ssl
D, [2013-10-14T10:26:13.240440 #12265] DEBUG -- : ssl.rb:208:in `serialize'
Serializing using marshal
D, [2013-10-14T10:26:13.240525 #12265] DEBUG -- : ssl.rb:307:in `makehash'
Creating message hash using /etc/mcollective/server_private.pem
D, [2013-10-14T10:26:13.243567 #12265] DEBUG -- : base.rb:168:in
`create_reply' Encoded a message for request
8d0b3938113259a3ac7d878b365ad522
D, [2013-10-14T10:26:13.243670 #12265] DEBUG -- : ssl.rb:208:in `serialize'
Serializing using marshal
D, [2013-10-14T10:26:13.243956 #12265] DEBUG -- : pluginmanager.rb:83:in
`[]' Returning cached plugin connector_plugin with class
MCollective::Connector::Activemq
D, [2013-10-14T10:26:13.244059 #12265] DEBUG -- : activemq.rb:266:in
`publish' Sending a broadcast message to ActiveMQ target
'/queue/mcollective.reply.wolf.shands.ufl.edu_24887' with headers '{}'
D, [2013-10-14T10:26:13.245763 #12265] DEBUG -- : runnerstats.rb:56:in
`sent' Incrementing replies stat
It looks suspiciously like the reply created by base.rb is empty-- But I'm
not sure how to proceed from here with troubleshooting since I don't know
what a valid reply looks like.
On Friday, June 7, 2013 4:25:19 AM UTC-4, Richard Knight wrote:
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 unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: mcollective setup question
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 unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: mcollective setup question
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 SecurityValidationFailed = e
Log.warn(Ignoring a message that did not pass security validations)
and looking in the logs you can find the request ID for the mco command:
base.rb:178:in `create_request' Encoding a request for agent 'discovery' in
collective mcollective with request id 2f1214f66d1f5741bb79daa26ed6316e
client.rb:51:in `sendreq' Sending request 2f1214f66d1f5741bb79daa26ed6316e
to the discovery agent with ttl 60 in collective mcollective
So it would seem that the client is expecting the reponse from the server
to have the same requestid as the one it sent, but for some reason they are
different. If the server is using SSL to generate/verify these request id's
it may point to a cert or pki mismatch issue but so far I haven't been able
to sport anything wrong with either. Ruvy isn't my strong suit so it will
probably need a ruby dev or one of the puppet team to explain how these ids
are generated and verified.
--
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, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: mcollective getaddrinfo: Name or service not known
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 Know Why
--
amd
On Tuesday, August 21, 2012 6:46:52 PM UTC-5, James Trier wrote:
I'm getting these errors when running 'puppet agent --test' after doing a
new installation of an agent:
err:
/Stage[main]/Pe_mcollective::Plugins/File[/opt/puppet/libexec/mcollective/mcollective/security/sshkey.rb]/content:
change from {md5}512f42272699eaa085c83d2cc67c27ea to
{md5}8fa3e9125fd917948445e3d2621d40e5 failed: Could not back up
/opt/puppet/libexec/mcollective/mcollective/security/sshkey.rb:
getaddrinfo: Name or service not known
err:
/Stage[main]/Pe_mcollective::Posix/File[/etc/puppetlabs/mcollective/server.cfg]/content:
change from {md5}a9c7335a83c5ac9f6a19bb195ea0c63e to
{md5}db6aa935c128b6d7bd12b41dfbe33b91 failed: Could not back up
/etc/puppetlabs/mcollective/server.cfg: getaddrinfo: Name or service not
known
I know the above error is commonly related to DNS but I'm not sure where
the disconnect it. These are brand new agent installations. server field in
the agent puppet.conf is the server hostname which is also the listed
certname shown when 'puppet master --configprint certname,certdnsnames' is
typed from the server (certdnsname is blank).
Any help or direction?
Thanks -- James
--
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, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: mcollective getaddrinfo: Name or service not known
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, James Trier wrote:
I'm getting these errors when running 'puppet agent --test' after doing a
new installation of an agent:
err:
/Stage[main]/Pe_mcollective::Plugins/File[/opt/puppet/libexec/mcollective/mcollective/security/sshkey.rb]/content:
change from {md5}512f42272699eaa085c83d2cc67c27ea to
{md5}8fa3e9125fd917948445e3d2621d40e5 failed: Could not back up
/opt/puppet/libexec/mcollective/mcollective/security/sshkey.rb:
getaddrinfo: Name or service not known
err:
/Stage[main]/Pe_mcollective::Posix/File[/etc/puppetlabs/mcollective/server.cfg]/content:
change from {md5}a9c7335a83c5ac9f6a19bb195ea0c63e to
{md5}db6aa935c128b6d7bd12b41dfbe33b91 failed: Could not back up
/etc/puppetlabs/mcollective/server.cfg: getaddrinfo: Name or service not
known
I know the above error is commonly related to DNS but I'm not sure where
the disconnect it. These are brand new agent installations. server field in
the agent puppet.conf is the server hostname which is also the listed
certname shown when 'puppet master --configprint certname,certdnsnames' is
typed from the server (certdnsname is blank).
Any help or direction?
Thanks -- James
--
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, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: mcollective puppetd plugin does not work
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 command runs successfully for all nodes. But i want to run puppet agent for only the specified server. For this i m using .. mco puppet runonce --server puppet.example.net I m getting following error === The puppet application failed to run, use -v for full error details: Cannot validate input server: Unknown validator: 'puppet_server_address'. I m unable to find put the issue. Please help me?? -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: mcollective puppetd plugin does not work
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, snlsingha...@gmail.com 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 puppet runonce * [ ] 2 / 2 Finished processing 2 / 2 hosts in 1093.05 ms This command runs successfully for all nodes. But i want to run puppet agent for only the specified server. For this i m using .. mco puppet runonce --server puppet.example.net I m getting following error === The puppet application failed to run, use -v for full error details: Cannot validate input server: Unknown validator: 'puppet_server_address'. I m unable to find put the issue. Please help me?? -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Mcollective
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 here, they cover how to get that set up (assuming you're using Puppet): http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML On Friday, February 1, 2013 12:44:49 PM UTC-8, Worker Bee wrote: Hi Everyone; I am just starting with MCollective and I am struggling to find information about how to properly configure it. I have it installed but, I cannot seem to get mco facts working.. mco facts does not return the request information. Any help would be greatly appreciated! [root@mydev5 ~]# mco facts hostname mydev5 Report for fact: hostname Finished processing 1 / 1 hosts in 54.62 ms Thanks! Bee -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Mcollective
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 '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 here, they cover how to get that set up (assuming you're using Puppet): http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML On Friday, February 1, 2013 12:44:49 PM UTC-8, Worker Bee wrote: Hi Everyone; I am just starting with MCollective and I am struggling to find information about how to properly configure it. I have it installed but, I cannot seem to get mco facts working.. mco facts does not return the request information. Any help would be greatly appreciated! [root@mydev5 ~]# mco facts hostname mydev5 Report for fact: hostname Finished processing 1 / 1 hosts in 54.62 ms Thanks! Bee -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: mcollective puppetd plugin does not work
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, and where I can find doc for this? Thanks. Hai T. On Mon, Jul 30, 2012 at 8:27 AM, pmbuko pmb...@gmail.com wrote: 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 * [ ] 1 / 1 test-01 Request Aborted Already disabled Finished processing 1 / 1 hosts in 64.07 ms # mco puppetd -I test-01 status * [ ] 1 / 1 test-01 Currently disabled; last completed run 1550 seconds ago Finished processing 1 / 1 hosts in 60.37 ms Hai, When you tell mcollective to disable puppet on a node, it *administratively disables* the agent but it does not stop the puppetd process. If you try 'puppet agent -t' on an node that has been administratively disabled you will see that puppet won't actually run. -- Peter -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/AFPGM7_T5SwJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Hai Tao -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: mcollective puppetd plugin does not work
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 interpreting the lock file's presence as a run in progress. If there is no run in progress when you disable the agent, then you should be seeing this output when you try to run puppet (with version 2.6+) : notice: Skipping run of Puppet configuration client; administratively disabled; use 'puppet agent --enable' to re-enable. If you try 'puppet agent --enable' does the puppetdlock file disappear from this location? It should. -- Peter On Jul 30, 2012, at 12:23 PM, Hai Tao wrote: 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, and where I can find doc for this? Thanks. Hai T. On Mon, Jul 30, 2012 at 8:27 AM, pmbuko pmb...@gmail.com wrote: 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 * [ ] 1 / 1 test-01 Request Aborted Already disabled Finished processing 1 / 1 hosts in 64.07 ms # mco puppetd -I test-01 status * [ ] 1 / 1 test-01 Currently disabled; last completed run 1550 seconds ago Finished processing 1 / 1 hosts in 60.37 ms Hai, When you tell mcollective to disable puppet on a node, it *administratively disables* the agent but it does not stop the puppetd process. If you try 'puppet agent -t' on an node that has been administratively disabled you will see that puppet won't actually run. -- Peter -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/AFPGM7_T5SwJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Hai Tao -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Peter -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: mcollective puppetd plugin does not work
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 Elapsed Time: 62.07 s why do not I get the service sshd status of the node? On Mon, Jul 30, 2012 at 9:36 AM, Peter Bukowinski pmb...@gmail.com wrote: 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 interpreting the lock file's presence as a run in progress. If there is no run in progress when you disable the agent, then you should be seeing this output when you try to run puppet (with version 2.6+) : notice: Skipping run of Puppet configuration client; administratively disabled; use 'puppet agent --enable' to re-enable. If you try 'puppet agent --enable' does the puppetdlock file disappear from this location? It should. -- Peter On Jul 30, 2012, at 12:23 PM, Hai Tao wrote: 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, and where I can find doc for this? Thanks. Hai T. On Mon, Jul 30, 2012 at 8:27 AM, pmbuko pmb...@gmail.com wrote: 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 * [ ] 1 / 1 test-01 Request Aborted Already disabled Finished processing 1 / 1 hosts in 64.07 ms # mco puppetd -I test-01 status * [ ] 1 / 1 test-01 Currently disabled; last completed run 1550 seconds ago Finished processing 1 / 1 hosts in 60.37 ms Hai, When you tell mcollective to disable puppet on a node, it *administratively disables* the agent but it does not stop the puppetd process. If you try 'puppet agent -t' on an node that has been administratively disabled you will see that puppet won't actually run. -- Peter -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/AFPGM7_T5SwJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Hai Tao -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Peter -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Hai Tao -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: mcollective puppetd plugin does not work
- Original Message - From: Hai Tao ehai...@gmail.com 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 called nodeA, however, # mco service sshd -I nodeA status | [ ] | 0 / 1 service summary Nodes: 1 / 0 Statuses: No responses received Elapsed Time: 62.07 s why do not I get the service sshd status of the node? anything weird logged on your server mcollective.log? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: mcollective puppetd plugin does not work
I changed puppet-service.rb to service.rb, and it works now. why the plugin use puppet-service.rb, but with service.ddl, and we have to manually change it? On Mon, Jul 30, 2012 at 5:36 PM, R.I.Pienaar r...@devco.net wrote: - Original Message - From: Hai Tao ehai...@gmail.com 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 called nodeA, however, # mco service sshd -I nodeA status | [ ] | 0 / 1 service summary Nodes: 1 / 0 Statuses: No responses received Elapsed Time: 62.07 s why do not I get the service sshd status of the node? anything weird logged on your server mcollective.log? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Hai Tao -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: mcollective bits
On Mar 19, 1:45 pm, Douglas Garstang doug.garst...@gmail.com 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 the client.cfg files. The server.cfg file is part of the collective package and the client.cfg file is part of the client.cfg package. However, I though the client package was installed on the single querying system? As you can see, it's all quite confusing and the documentation doesn't clearly explain it. Doug I had the same issue trying to comprehend the notion of which was client and server. After I bit of friendly explanation, it made more sense. The explanation was as follows, MCollective's notion of server/client is based on which is actually the TCP/IP server, e.g. the one that accepts the connection request. Meaning, each of your puppet clients runs an MCollective server and your central MCollective client, that is the one that runs mco, initiates a connection to each MCollective server for any command you may run. So your server.cfg should go out to all servers and the client.cfg should only be on one (or a handful of) server(s). Hope that helps, -Matt -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: mcollective bits
- Original Message - From: Matt Warren mattwwar...@gmail.com To: Puppet Users puppet-users@googlegroups.com Sent: Tuesday, March 20, 2012 1:47:46 PM Subject: [Puppet Users] Re: mcollective bits On Mar 19, 1:45 pm, Douglas Garstang doug.garst...@gmail.com 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 the client.cfg files. The server.cfg file is part of the collective package and the client.cfg file is part of the client.cfg package. However, I though the client package was installed on the single querying system? As you can see, it's all quite confusing and the documentation doesn't clearly explain it. Doug I had the same issue trying to comprehend the notion of which was client and server. After I bit of friendly explanation, it made more sense. The explanation was as follows, MCollective's notion of server/client is based on which is actually the TCP/IP server, e.g. the one that accepts the connection request. Meaning, each of your puppet clients runs an MCollective server and your central MCollective client, that is the one that runs mco, initiates a connection to each MCollective server for any command you may run. So your server.cfg should go out to all servers and the client.cfg should only be on one (or a handful of) server(s). See http://docs.puppetlabs.com/mcollective/reference/basic/messageflow.html and the screencast it links to -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: mcollective plugin question
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 k...@paydiant.com 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 we would like to utilize this tool is to create an arbitrary shell command plugins/services so our master can really act as a command center. I spoke with a couple folks and know that this is just as a matter of writing the plugin itself, but I'm wondering if folks here already have a solution for it or if you have any pointers we can check. :) Thx in advance. --KL This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: mcollective for rhel 4
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 ohadl...@gmail.com wrote: On Sat, Jan 22, 2011 at 12:59 PM, R.I.Pienaar r...@devco.net wrote: hey, - Original Message - Is their a mcollective rpm for rhel4? If not, is their a src rpm for 1.0 I can compile for rhel4? I looked around the web site and could not find anything. There are src rpms on the puppet labs download and the spec is in the tarball and in git. There's a slight problem though with rhel 4 the spec force the package into noarch mode while on rhel 4 that makes no sense cos they have their packages set up for i386/x86_64 with arch specific lib dirs etc. don't forget that rhel4 doesnt have rubygems, so you'll have to figure out how to ship the stomp lib as well... I created a long time ago a package for rhel4, but its fairly out of date by now. Ohad -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: mcollective scalability
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 li...@truthisfreedom.org.uk 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 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 connected by gigE. 95% response from mc-ping is 300ms, average 200ms. I'm expecting at least 1000 nodes in three geo areas by the end of the year. My todo list for this summer has federating some more activemqs into the setup. You'd probably want a few activemq instances in a cluster in such a setup, though I've heard of much larger client counts on activemq. The above all runs off of a single activemq server currently. Quad core xeon w/ 3gb ram sitting at 99% idle. For those of you that are interested, I've put up a few blogposts about configuring ActiveMQ and Mcollective on both Centos and Ubuntu at http://www.threedrunkensysadsonthe.net/ Kind regards, Matt -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: mcollective scalability
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 connected by gigE. 95% response from mc-ping is 300ms, average 200ms. I'm expecting at least 1000 nodes in three geo areas by the end of the year. My todo list for this summer has federating some more activemqs into the setup. You'd probably want a few activemq instances in a cluster in such a setup, though I've heard of much larger client counts on activemq. The above all runs off of a single activemq server currently. Quad core xeon w/ 3gb ram sitting at 99% idle. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: mcollective scalability
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 house agents. Nodes are primarily split between two buildings connected by gigE. 95% response from mc-ping is 300ms, average 200ms. I'm expecting at least 1000 nodes in three geo areas by the end of the year. My todo list for this summer has federating some more activemqs into the setup. You'd probably want a few activemq instances in a cluster in such a setup, though I've heard of much larger client counts on activemq. The above all runs off of a single activemq server currently. Quad core xeon w/ 3gb ram sitting at 99% idle. For those of you that are interested, I've put up a few blogposts about configuring ActiveMQ and Mcollective on both Centos and Ubuntu at http://www.threedrunkensysadsonthe.net/ Kind regards, Matt -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: mcollective scalability
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 li...@truthisfreedom.org.uk 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 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 connected by gigE. 95% response from mc-ping is 300ms, average 200ms. I'm expecting at least 1000 nodes in three geo areas by the end of the year. My todo list for this summer has federating some more activemqs into the setup. You'd probably want a few activemq instances in a cluster in such a setup, though I've heard of much larger client counts on activemq. The above all runs off of a single activemq server currently. Quad core xeon w/ 3gb ram sitting at 99% idle. For those of you that are interested, I've put up a few blogposts about configuring ActiveMQ and Mcollective on both Centos and Ubuntu at http://www.threedrunkensysadsonthe.net/ Kind regards, Matt -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
