>
> Did you build this on a system with openssl-devel or equivalent installed? Or
> install openssl+devel headers into your /local location?
BINGO! That was the problem. THANK YOU.
What really gets me is that I would never have figured this out, based
on the ambiguous error message.
I just
>Here are the errors in full, and demonstrating the entire path:
>
>
>[ /local]# bin/gem list
>
>*** LOCAL GEMS ***
>
>facter (1.6.5)
>puppet (2.7.11)
>
>
>[ /local]# bin/puppet --version
>
>/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in
>`gem_original_require': no such file to load
Here are the errors in full, and demonstrating the entire path:
[ /local]# bin/gem list
*** LOCAL GEMS ***
facter (1.6.5)
puppet (2.7.11)
[ /local]# bin/puppet --version
/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in
`gem_original_require': no such file to load -- openssl (Lo
I installed this using the full path to the shared gem, simply:
/local/bin/gem install puppet
The puppet code, et al, is in the proper place under /local/lib/
I don't need to worry about the installation, I can overwrite it any
time -- this is my test platform.
I did bootstrap ruby and inst
On Feb 24, 1:38 pm, Forrie wrote:
> Also, the puppet I'm using (on all systems) is installed from the gem.
You did not directly answer the key question, which I now think is
this:
>Is it possible that you used the system's Ruby (or the system's gem)
>to install the openssl or puppet gem into th
Also, the puppet I'm using (on all systems) is installed from the gem.
--
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-user
I built Ruby with:
./configure --prefix=/local
I see that you can specify a number of options with ./configure,
including:
--with-sitedir=DIR site libraries in DIR [LIBDIR/ruby/site_ruby]
but the defaults for this should just work with that switch. I see
these options, too:
--exec-pre
On Feb 23, 2:10 pm, Forrie wrote:
> I just did a basic find statement and found:
>
> # pwd
> /local/lib/ruby/gems/1.8/gems/puppet-2.7.11
>
> # find . -exec grep -i site_ruby {} \;
>
> SITELIBDIR="/usr/lib/ruby/site_ruby/1.8"
> sitelibdir = $LOAD_PATH.find { |x| x =~ /site_ruby/ }
>
On Feb 23, 1:53 pm, Forrie wrote:
> This is what I did, I did a make/make install into the shared
> location. But I wonder if there is some hard-coded PATH in there
> somewhere. I'll have to poke around. I don't see where I can do a
> trace on executing this to see what it's calling.
Did y
I just did a basic find statement and found:
# pwd
/local/lib/ruby/gems/1.8/gems/puppet-2.7.11
# find . -exec grep -i site_ruby {} \;
SITELIBDIR="/usr/lib/ruby/site_ruby/1.8"
sitelibdir = $LOAD_PATH.find { |x| x =~ /site_ruby/ }
sitelibdir = File.join(libdir, "site_ruby")
This must have to do with an include path, as here is where I find the
code:
/local/lib/ruby/site_ruby/1.8/rubygems/gem_openssl.rb
it's been a while, but I think the SITE_RUBY include is configured
somewhere - and that may be the issue.
--
You received this message because you are subscribed to
> This is probably not an issue with the executable search path, but
> rather with the Ruby path. It looks like whichever Ruby interpreter
> you are using to run Puppet is unable to find one of the files
> (probably openssl.rb) that it expects to see in the Ruby library. The
> Ruby interpreter i
On Feb 22, 6:50 pm, Forrie wrote:
> I'm attempting to deploy puppet via an NFS share. It's on a local-only
> network, and it will contain only ruby (gems) and whatever is needed.
>
> Seems simple enough, but tonight I am having an issue with this error:
>
> # service puppet start
> Starting pupp
13 matches
Mail list logo
