Puppet users - Jun 2011 - Using Mcollective with Enterprise Ruby

We are using Enterprise Ruby - I want to dig into Mcollective;
however, there is no installation script in the *.tgz.   Also, the
rpms have various requirements from the stock distribution (RHEL5 in
my case) that are already present under our Enterprise Ruby
installation.

     Is there some clever way to weave this together.  How to install
the Mcollective without the typical setup.rb scripting.   I see the
*.spec file there, I suppose I could remove the dependencies and try
to build out individual *rpms.     Come to think of it, I wonder if
there''s a flag to RPM that I could override dependency checks with the
RPMS and be done with this?


Thanks.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

----- Original Message -----
> We are using Enterprise Ruby - I want to dig into Mcollective;
> however, there is no installation script in the *.tgz.   Also, the
> rpms have various requirements from the stock distribution (RHEL5 in
> my case) that are already present under our Enterprise Ruby
> installation.
> 
>      Is there some clever way to weave this together.  How to install
> the Mcollective without the typical setup.rb scripting.   I see the
> *.spec file there, I suppose I could remove the dependencies and try
> to build out individual *rpms.     Come to think of it, I wonder if
> there''s a flag to RPM that I could override dependency checks with
> the
> RPMS and be done with this?
you should have good milage with more or less:

git clone <puppet labs git repo>
git checkout 1.2.0
rake rpm

if your /usr/bin/env ruby does the right thing, you should end up with
rpms that are built for your ruby

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

>
> you should have good milage with more or less:
>
> git clone <puppet labs git repo>
> git checkout 1.2.0
> rake rpm
>
> if your /usr/bin/env ruby does the right thing, you should end up with
> rpms that are built for your ruby

This still leaves the dependencies issue with rubygems-stomp, ruby,
etc., all of which I already have installed in the Enterprise Ruby
installation.  I just tried it.

Is there a switch I can pass to RPM to tell it to ignore dependencies.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

----- Original Message -----
> 
> >
> > you should have good milage with more or less:
> >
> > git clone <puppet labs git repo>
> > git checkout 1.2.0
> > rake rpm
> >
> > if your /usr/bin/env ruby does the right thing, you should end up
> > with
> > rpms that are built for your ruby
> 
> 
> This still leaves the dependencies issue with rubygems-stomp, ruby,
> etc., all of which I already have installed in the Enterprise Ruby
> installation.  I just tried it.
> 
> Is there a switch I can pass to RPM to tell it to ignore
> dependencies.
not sure if there''s a way to tell rpmbuild to do that, but you can
just comment them out in the spec file. or when you install you can
do rpm -ivh --nodeps to skip them.

There''s a ticket open to make this kind of thing easier - being able
to rebuild the rpms for different rubies installed in weird places
but I havnt really had any good thoughts about how to achieve that.
-- 
R.I.Pienaar

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

> not sure if there''s a way to tell rpmbuild to do that, but you can
> just comment them out in the spec file. or when you install you can
> do rpm -ivh --nodeps to skip them.
>
> There''s a ticket open to make this kind of thing easier - being
able
> to rebuild the rpms for different rubies installed in weird places
> but I havnt really had any good thoughts about how to achieve that.
> --
> R.I.Pienaar
     This allowed me to get the product installed; however, it failed
with the /usr/bin/env -- so when I ran the commands, the
''require'' for
mcollective didn''t work (presumably because the installation
wasn''t
done properly, as it would have installed into the Enterprise Ruby
directory.

     The Enterprise Ruby executable is in my $PATH -- though the PATH
variable points to a symlink that goes to the full version named
directory -- shouldn''t make a difference here.

     Shouldn''t the mcollective tarball have a script to facilitate a
manual install?   That would be a good place to override/set some
variables.


Thanks...

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

----- Original Message -----
> 
> > not sure if there''s a way to tell rpmbuild to do that, but
you can
> > just comment them out in the spec file. or when you install you can
> > do rpm -ivh --nodeps to skip them.
> >
> > There''s a ticket open to make this kind of thing easier -
being
> > able
> > to rebuild the rpms for different rubies installed in weird places
> > but I havnt really had any good thoughts about how to achieve that.
> > --
> > R.I.Pienaar
> 
>      This allowed me to get the product installed; however, it failed
> with the /usr/bin/env -- so when I ran the commands, the
''require''
> for mcollective didn''t work (presumably because the installation
wasn''t
> done properly, as it would have installed into the Enterprise Ruby
> directory.
> 
>      The Enterprise Ruby executable is in my $PATH -- though the PATH
> variable points to a symlink that goes to the full version named
> directory -- shouldn''t make a difference here.
This is exactly why we use /usr/bin/env and not a hard coded path to your
ruby since everyone''s ruby is different.

/usr/bin/env will search your PATH and use the first one, I suspect you
have a local setup problem.
> 
>      Shouldn''t the mcollective tarball have a script to facilitate
a
> manual install?   That would be a good place to override/set some
> variables.
No I dont think we should have an install script that edit every ruby
script on install since this doesnt solve the problem - you will also
be installing other scripts from the plugins repo or what you found on
github etc.

Set your environment up correctly so that /usr/bin/env does what its
supposed to do and it will work fine.  If I add a custom ruby to the 
beginning of my PATH environment the mcollective scrips all just use
that ruby without a problem.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

My PATH is set with the /opt/ruby/bin pointer in the front.  When I
run /usr/bin/env on *any* of the many RHEL5 systems I have, it just
hangs.   Some of these I didn''t set up, some are just stock RHEL
installs.  So I don''t know whether this is a configuration problem or
not.

By install script, I meant one that actually installs mcollective.
Regardless of /usr/bin/env I think this makes some sense for people
that want to do a manual install vs. RPM.   As for the PATH issue with
ruby, I suppose that''s everyone''s personal choice.  I could
use
''alternatives'' to create links in standard locations to help 
mitigate
PATH issues, of course.


Thanks.


> >      This allowed me to get the product installed; however, it failed
> > with the /usr/bin/env -- so when I ran the commands, the
''require''
> > for mcollective didn''t work (presumably because the
installation wasn''t
> > done properly, as it would have installed into the Enterprise Ruby
> > directory.
>
> >      The Enterprise Ruby executable is in my $PATH -- though the PATH
> > variable points to a symlink that goes to the full version named
> > directory -- shouldn''t make a difference here.
>
> This is exactly why we use /usr/bin/env and not a hard coded path to your
> ruby since everyone''s ruby is different.
>
> /usr/bin/env will search your PATH and use the first one, I suspect you
> have a local setup problem.
>
>
>
> >      Shouldn''t the mcollective tarball have a script to
facilitate a
> > manual install?   That would be a good place to override/set some
> > variables.
>
> No I dont think we should have an install script that edit every ruby
> script on install since this doesnt solve the problem - you will also
> be installing other scripts from the plugins repo or what you found on
> github etc.
>
> Set your environment up correctly so that /usr/bin/env does what its
> supposed to do and it will work fine.  If I add a custom ruby to the
> beginning of my PATH environment the mcollective scrips all just use
> that ruby without a problem.
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

----- Original Message -----
> My PATH is set with the /opt/ruby/bin pointer in the front.  When I
> run /usr/bin/env on *any* of the many RHEL5 systems I have, it just
> hangs.   Some of these I didn''t set up, some are just stock RHEL
> installs.  So I don''t know whether this is a configuration problem
or
> not.
this all sounds like you have local configuration errors to be honest.

> By install script, I meant one that actually installs mcollective.
> Regardless of /usr/bin/env I think this makes some sense for people
> that want to do a manual install vs. RPM.   As for the PATH issue
> with ruby, I suppose that''s everyone''s personal choice. 
I could use
> ''alternatives'' to create links in standard locations to
help
>  mitigate PATH issues, of course.
Would you also expect this install script to be able to uninstall or 
upgrade?  Because generally they do not.

There''s a Makefile in ext/ that you can use with the normal unix tool
set to install it wherever you want.  It supports the usual DESTDIR 
variables etc.  It still cant make your broken ''env'' work
though.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

I think I presumed /usr/bin/env returned something.  It turns out, it
just executes the ruby binary.  So that part is working.

I now need to sort out the installation issue, mentioned above.
Would it be feasible to have an install.rb that you could pass flags
to for:

* common
* server
* client
* all (all of the above)

?  This would make it easy to manually install.

Failing that, I suppose directions about where to copy the files to,
init scripts, etc.  Something I think should be scripted.


Thanks.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

----- Original Message -----
> I think I presumed /usr/bin/env returned something.  It turns out, it
> just executes the ruby binary.  So that part is working.
> 
> I now need to sort out the installation issue, mentioned above.
> Would it be feasible to have an install.rb that you could pass flags
> to for:
> 
> * common
> * server
> * client
> * all (all of the above)
> 
> ?  This would make it easy to manually install.
> 
> Failing that, I suppose directions about where to copy the files to,
> init scripts, etc.  Something I think should be scripted.
> 
> 
it really sounds like you want to reinvent the packaging wheel, thats fine
by me - we accept contributed code and we have a public ticketing system
where you can file tickets and let us know where to find contributions.

I believe packaged sofware solve your problems much better than a script
could - since they take in mind things like your distributions rc system etc
so I dont think this is going to be a priority for us to script.  But
you''re
welcome to contribute.

-- 
R.I.Pienaar

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Point taken.

Back to the RPM issue.   For those of us that do not use a standard
system-provided ruby installation, such as Enterprise Ruby, how can we
mitigate the installation so that it works?

As I mentioned earlier, I tried this with --nodeps and the ruby script
could not "require" the mcollective bit.   Given that I just verified
that /usr/bin/env is working properly, I think we can safely eliminate
that.

What would be the best approach to get this working properly?
Enterprise Puppet also uses Enterprise Ruby, so I wonder how they''ve
handled it.

Thanks.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

----- Original Message -----
> Point taken.
> 
> Back to the RPM issue.   For those of us that do not use a standard
> system-provided ruby installation, such as Enterprise Ruby, how can
> we
> mitigate the installation so that it works?
> 
> As I mentioned earlier, I tried this with --nodeps and the ruby
> script
> could not "require" the mcollective bit.   Given that I just
verified
> that /usr/bin/env is working properly, I think we can safely
> eliminate
> that.
> 
> What would be the best approach to get this working properly?
> Enterprise Puppet also uses Enterprise Ruby, so I wonder how
they''ve
> handled it.

Did you rebuild the RPMs like I said yesterday with the ruby in your path
correctly setup?  Then the resulting RPMs will install into your enterprise
directory.

I also showed you how to install rpms bypassing the dependency checks and
also told you that you could just edit the requirements from the spec files.


-- 
R.I.Pienaar

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Here''s the output from the mcollective rpm install:

# rpm -ihv --nodeps *.rpm

Preparing...
########################################### [100%]
   1:mcollective-common
########################################### [ 33%]
   2:mcollective
########################################### [ 67%]
   3:mcollective-client
########################################### [100%]


note the 33% and 67% -- there''s an error somewhere?


Forrest

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

----- Original Message -----
> Here''s the output from the mcollective rpm install:
> 
> # rpm -ihv --nodeps *.rpm
> 
> Preparing...
> ########################################### [100%]
>    1:mcollective-common
> ########################################### [ 33%]
>    2:mcollective
> ########################################### [ 67%]
>    3:mcollective-client
> ########################################### [100%]
> 
> 
> note the 33% and 67% -- there''s an error somewhere?
> 
No, it installed 3 rpms.  The first was a 1/3 of the progress
the 2nd 2/3 and so forth.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Alright, so when I install it this way, I still get errors, which
indicates the installation may not be correct.  Here''s a log:




# rpm -ihv --nodeps *.rpm
warning: mcollective-1.2.0-5.el5.noarch.rpm: Header V3 RSA/SHA1
signature: NOKEY, key ID 4bd6ec30
Preparing...
########################################### [100%]
   1:mcollective-common
########################################### [ 33%]
   2:mcollective
########################################### [ 67%]
   3:mcollective-client
########################################### [100%]

# mc-facts
/usr/sbin/mc-facts:3:in `require'': no such file to load -- mcollective
(LoadError)
        from /usr/sbin/mc-facts:3

# head /usr/sbin/mc-facts
==> /usr/sbin/mc-facts <=#!/usr/bin/env ruby

require ''mcollective''

if $0 =~ /mc\-(.+)$/
    app_name = $1

    if MCollective::Applications.list.include?(app_name)
        MCollective::Applications.run(app_name)
    else


> No, it installed 3 rpms.  The first was a 1/3 of the progress
> the 2nd 2/3 and so forth.
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

----- Original Message -----
> Alright, so when I install it this way, I still get errors, which
> indicates the installation may not be correct.  Here''s a log:
are these RPMs you built like I said you should build them yesterday?

I dont think so.

> signature: NOKEY, key ID 4bd6ec30
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

I verified that this is not getting confused with /usr/bin/ruby, which
I removed also as a part of that test and removed/reinstalled
mcollective.

A "gem" would fit within the ruby paradigm.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Indeed, i was using the supplied RPMs.  The ones I built seem to be
doing something, tho I need to get RabbitMQ running first before I can
test it.   This error came up in the RPM build:

lib/mcollective/log.rb:83:79: Skipping require of dynamic string:
"mcollective/logger/#{logger_type.downcase}_logger"


Thanks.


On Jun 16, 3:22 pm, "R.I.Pienaar" <r...@devco.net>
wrote:
> ----- Original Message -----
> > Alright, so when I install it this way, I still get errors, which
> > indicates the installation may not be correct.  Here''s a log:
>
> are these RPMs you built like I said you should build them yesterday?
>
> I dont think so.
>
>
>
>
>
>
>
> > signature: NOKEY, key ID 4bd6ec30
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

As I''ve gotten to the point of configuring server.cfg and client.cfg,
based on the documentation in Pro Puppet (which also references use of
RPMs), it seems we have some configuration issues -- perhaps about
standards of where things need to be located.

The book refers to a non-existent directory, /usr/share/mcollective/
plugins.  The RPMs create /etc/mcollective/plugin.d (empty).   Thus,
when you start the server, it fails with the following errors:


E, [2011-06-28T16:16:19.419481 #25040] ERROR -- : pluginmanager.rb:
111:in `loadclass'' Failed to load Mcollective::Facts::Yaml_facts:
no such file to load -- mcollective/facts/yaml_facts.rb
E, [2011-06-28T16:16:19.419708 #25040] ERROR -- : pluginmanager.rb:
111:in `loadclass'' Failed to load Mcollective::Connector::Stomp: n
o such file to load -- mcollective/connector/stomp.rb
E, [2011-06-28T16:16:19.419891 #25040] ERROR -- : pluginmanager.rb:
111:in `loadclass'' Failed to load Mcollective::Security::Psk: no s
uch file to load -- mcollective/security/psk.rb
E, [2011-06-28T16:16:19.420036 #25040] ERROR -- : pluginmanager.rb:
111:in `loadclass'' Failed to load Mcollective::Registration::Agent
list: no such file to load -- mcollective/registration/agentlist.rb
I, [2011-06-28T16:16:19.420433 #25040]  INFO -- : mcollectived:31 The
Marionette Collective 1.2.0 started logging at info level


I could be mistaken.  What''s missing?


-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

you are using the RPMs? what version and what have you installed.

plugins.d is not where plugins go it would be /usr/share/mcollective
of /usr/libexec/mcollective depending on distro etc

----- Original Message -----
> As I''ve gotten to the point of configuring server.cfg and
client.cfg,
> based on the documentation in Pro Puppet (which also references use
> of
> RPMs), it seems we have some configuration issues -- perhaps about
> standards of where things need to be located.
> 
> The book refers to a non-existent directory, /usr/share/mcollective/
> plugins.  The RPMs create /etc/mcollective/plugin.d (empty).   Thus,
> when you start the server, it fails with the following errors:
> 
> 
> E, [2011-06-28T16:16:19.419481 #25040] ERROR -- : pluginmanager.rb:
> 111:in `loadclass'' Failed to load Mcollective::Facts::Yaml_facts:
> no such file to load -- mcollective/facts/yaml_facts.rb
> E, [2011-06-28T16:16:19.419708 #25040] ERROR -- : pluginmanager.rb:
> 111:in `loadclass'' Failed to load Mcollective::Connector::Stomp: n
> o such file to load -- mcollective/connector/stomp.rb
> E, [2011-06-28T16:16:19.419891 #25040] ERROR -- : pluginmanager.rb:
> 111:in `loadclass'' Failed to load Mcollective::Security::Psk: no s
> uch file to load -- mcollective/security/psk.rb
> E, [2011-06-28T16:16:19.420036 #25040] ERROR -- : pluginmanager.rb:
> 111:in `loadclass'' Failed to load Mcollective::Registration::Agent
> list: no such file to load -- mcollective/registration/agentlist.rb
> I, [2011-06-28T16:16:19.420433 #25040]  INFO -- : mcollectived:31 The
> Marionette Collective 1.2.0 started logging at info level
> 
> 
> I could be mistaken.  What''s missing?
> 
> 
> --
> 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+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
> 
> 
-- 
R.I.Pienaar

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Because I''m using Enterprise Ruby I had to manually run "make
rpm" and
use those.   This is on RHEL5.  It''s just confusing when a book says
one thing, the dist another.

I also noticed that /usr/libexec/mcollective may have been installed
incorrectly by the RPM.  It installs it as /usr/libexec/mcollective/
mcollective.

There is no plugin directory under it tho.

There is no /usr/share/mcollective created by the RPMs.


Thanks.



On Jun 28, 4:36 pm, "R.I.Pienaar" <r...@devco.net>
wrote:
> you are using the RPMs? what version and what have you installed.
>
> plugins.d is not where plugins go it would be /usr/share/mcollective
> of /usr/libexec/mcollectivedepending on distro etc
>
>
>
>
>
>
>
>
>
> ----- Original Message -----
> > As I''ve gotten to the point of configuring server.cfg and
client.cfg,
> > based on the documentation in Pro Puppet (which also references use
> > of
> > RPMs), it seems we have some configuration issues -- perhaps about
> > standards of where things need to be located.
>
> > The book refers to a non-existent directory, /usr/share/mcollective/
> > plugins.  The RPMs create /etc/mcollective/plugin.d (empty).   Thus,
> > when you start the server, it fails with the following errors:
>
> > E, [2011-06-28T16:16:19.419481 #25040] ERROR -- : pluginmanager.rb:
> > 111:in `loadclass'' Failed to
loadMcollective::Facts::Yaml_facts:
> > no such file to load --mcollective/facts/yaml_facts.rb
> > E, [2011-06-28T16:16:19.419708 #25040] ERROR -- : pluginmanager.rb:
> > 111:in `loadclass'' Failed to
loadMcollective::Connector::Stomp: n
> > o such file to load --mcollective/connector/stomp.rb
> > E, [2011-06-28T16:16:19.419891 #25040] ERROR -- : pluginmanager.rb:
> > 111:in `loadclass'' Failed to loadMcollective::Security::Psk:
no s
> > uch file to load --mcollective/security/psk.rb
> > E, [2011-06-28T16:16:19.420036 #25040] ERROR -- : pluginmanager.rb:
> > 111:in `loadclass'' Failed to
loadMcollective::Registration::Agent
> > list: no such file to load --mcollective/registration/agentlist.rb
> > I, [2011-06-28T16:16:19.420433 #25040]  INFO -- : mcollectived:31 The
> > Marionette Collective 1.2.0 started logging at info level
>
> > I could be mistaken.  What''s missing?
>
> > --
> > 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+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/puppet-users?hl=en.
>
> --
> R.I.Pienaar
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Where is the plugins directory supposed to be installed/located?

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

----- Original Message -----
> Where is the plugins directory supposed to be installed/located?
on redhat, /usr/libexec/mcollective/mcollective/agent, application, etc.

this differs between distros based on whatever the distro policies have
to say etc.

A detailed install guide for plugins exist that explains how it works:

http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/InstalingPlugins

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.