- 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 exis
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+unsu
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/mcol
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 o
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,
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}_l
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 pos
- 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
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...
##
- Original Message -
> Here's the output from the mcollective rpm install:
>
> # rpm -ihv --nodeps *.rpm
>
> Preparing...
> ### [100%]
>1:mcollective-common
> ### [ 33%]
>2:mcollective
>
Here's the output from the mcollective rpm install:
# rpm -ihv --nodeps *.rpm
Preparing...
### [100%]
1:mcollective-common
### [ 33%]
2:mcollective
### [ 67%]
3:mcollec
- 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
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 mcolle
- 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 fla
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
*
- 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
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 m
- 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
>
> 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 instal
- Original Message -
>
> >
> > you should have good milage with more or less:
> >
> > git clone
> > 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 depe
>
> you should have good milage with more or less:
>
> git clone
> 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
21 matches
Mail list logo
