Re: [Puppet Users] Re: Installing puppet 0.25.5 on SLES 9 64bit

2010-10-01 Thread Thorsten Biel

Hi,

I have a self-packaged Ruby 1.8.7 running on SLES9 64bit. If you wish, I can 
send you the binary RPMs (rather large), if building the package isn't your cup 
of tea.

Anybody else interested in the Spec file or binaries?

Cheers,
-Thorsten


On 1 Oct 2010, at 13:27, Christian  wrote:

> Sandor,
> 
> I'm not sure if it is a SUSE problem. As described the same setup
> works perfectly on SLES 9 32 bit workstations. I more think there is
> something wrong with the 64 bit rpms or the 64 bit ruby version.
> 
> I used now the ldd command to list the libraries ruby is linked
> against.
> As you recognized already the openssl is actually not linked to ruby.
> 
> libdl.so.2 => /lib64/libdl.so.2 (0x002a9566d000)
> libcrypt.so.1 => /lib64/libcrypt.so.1 (0x002a9577)
> libm.so.6 => /lib64/tls/libm.so.6 (0x002a958a8000)
> libc.so.6 => /lib64/tls/libc.so.6 (0x002a95a0)
> /lib64/ld-linux-x86-64.so.2 (0x002a95556000)
> 
> Your solution suggestion i don't understand completely ...
> $ ruby -e 'require "openssl"; puts OpenSSL::Digest::MD5.digest "foo"'
> 
> Which term i should use to replace "foo"? Sorry i'm not (yet) a ruby
> expert.
> 
> Christian
> 
> 
> 
> 
> On Oct 1, 8:50 am, Sandor Szuecs  wrote:
>> On Oct 1, 2010, at 10:29 AM, Christian wrote:
>> 
>>> Some idea how to solve that problem and how i can make the ./
>>> openssl.so loadable?
>> 
>> You can try the following:
>> $ ruby -e 'require "openssl"; puts OpenSSL::Digest::MD5.digest "foo"'
>> 
>> Is you ruby installation linked against openssl.so?
>> 
>> I am not sure if it should be, because on my system it's not linked or I
>> just do not understand how it is working.
>> $ otool -L /usr/bin/ruby   /usr/bin/ruby:
>> 
>> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/libruby.1.dylib
>>  (compatibility version 1.8.0, current version 1.8.7)
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
>> version 125.2.0)
>> 
>> Anyway in my opinion this should be fixed by the SuSe team.
>> 
>> All the best, Sandor Szücs
>> --
> 
> -- 
> 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.



Re: [Puppet Users] Re: Installing puppet 0.25.5 on SLES 9 64bit

2010-10-01 Thread Sandor Szuecs

On Oct 1, 2010, at 1:27 PM, Christian wrote:
> 
> Your solution suggestion i don't understand completely ...
> $ ruby -e 'require "openssl"; puts OpenSSL::Digest::MD5.digest "foo"'
> 
> Which term i should use to replace "foo"? Sorry i'm not (yet) a ruby
> expert.

Sorry it was not a solution suggestion. I thought you should test, if
you can use ruby's openssl bindings. The oneliner just test this. I 
should be more explicit in my last e-mail. If this line does not return 
an error, then the openssl part of your 64 bit ruby installation seems 
to be ok.

I really have no idea to fix your issue. Maybe you can e-mail the 
maintainer of your package. He/She should know how to fix it.

All the best, Sandor Szücs
--

-- 
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: Installing puppet 0.25.5 on SLES 9 64bit

2010-10-01 Thread Christian
Sandor,

I'm not sure if it is a SUSE problem. As described the same setup
works perfectly on SLES 9 32 bit workstations. I more think there is
something wrong with the 64 bit rpms or the 64 bit ruby version.

I used now the ldd command to list the libraries ruby is linked
against.
As you recognized already the openssl is actually not linked to ruby.

libdl.so.2 => /lib64/libdl.so.2 (0x002a9566d000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x002a9577)
libm.so.6 => /lib64/tls/libm.so.6 (0x002a958a8000)
libc.so.6 => /lib64/tls/libc.so.6 (0x002a95a0)
/lib64/ld-linux-x86-64.so.2 (0x002a95556000)

Your solution suggestion i don't understand completely ...
$ ruby -e 'require "openssl"; puts OpenSSL::Digest::MD5.digest "foo"'

Which term i should use to replace "foo"? Sorry i'm not (yet) a ruby
expert.

Christian




On Oct 1, 8:50 am, Sandor Szuecs  wrote:
> On Oct 1, 2010, at 10:29 AM, Christian wrote:
>
> > Some idea how to solve that problem and how i can make the ./
> > openssl.so loadable?
>
> You can try the following:
> $ ruby -e 'require "openssl"; puts OpenSSL::Digest::MD5.digest "foo"'
>
> Is you ruby installation linked against openssl.so?
>
> I am not sure if it should be, because on my system it's not linked or I
> just do not understand how it is working.
> $ otool -L /usr/bin/ruby               /usr/bin/ruby:
>         
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/libruby.1.dylib
>  (compatibility version 1.8.0, current version 1.8.7)
>         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
> version 125.2.0)
>
> Anyway in my opinion this should be fixed by the SuSe team.
>
> All the best, Sandor Szücs
> --

-- 
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: Installing puppet 0.25.5 on SLES 9 64bit

2010-10-01 Thread Sandor Szuecs

On Oct 1, 2010, at 10:29 AM, Christian wrote:

> Some idea how to solve that problem and how i can make the ./
> openssl.so loadable?


You can try the following:
$ ruby -e 'require "openssl"; puts OpenSSL::Digest::MD5.digest "foo"'

Is you ruby installation linked against openssl.so?

I am not sure if it should be, because on my system it's not linked or I
just do not understand how it is working.
$ otool -L /usr/bin/ruby   /usr/bin/ruby:

/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/libruby.1.dylib 
(compatibility version 1.8.0, current version 1.8.7)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
version 125.2.0)


Anyway in my opinion this should be fixed by the SuSe team.


All the best, Sandor Szücs
--

-- 
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: Installing puppet 0.25.5 on SLES 9 64bit

2010-10-01 Thread Christian
Thanks to Sandor's suggestion i was able to run facter. By running
puppetd with the right ruby path a new error message appeared.

It seems that it can't be found the ./openssl.so library.

Following message appears:
Cannot open shared object file: No such file or directory - ./
openssl.so (LoadError)

The file openssl.so i was able to find on the system so i pointed also
a second ruby loadpath on that folder. However without success...

Some idea how to solve that problem and how i can make the ./
openssl.so loadable?

Christian

On 30 Sep., 10:26, Sandor Szuecs  wrote:
> On Sep 29, 2010, at 3:45 PM, Christian wrote:
>
> > /usr/sbin/puppetd:159:in `require': No such file to load -- puppet/
> > application/puppetd (LoadError)
> >        from /usr/sbin/puppetd:159
>
> > What went wrong here? Is there a bug in the rpm? Or do i have to set a
> > path somewhere?
>
> It seems you have to set the ruby loadpath, $:, yourself to the folder
> where the files puppet.rb and facter.rb are.
> You can add a load path with `ruby -Ipath/to/load` or add it to GEM_PATH
> env variable. You can add a path to $GEM_PATH separated with ':', like
> bash/zsh $PATH.
>
> All the best, Sandor Szücs
> --

-- 
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: Installing puppet 0.25.5 on SLES 9 64bit

2010-09-29 Thread Christian
By the way the same happens when i want to start facter

/usr/bin/facter:50:in `require': No such file to load -- facter
(LoadError)
from /usr/bin/facter:50


-- 
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.