The problem was that our el5 rubygem-json package was the el6 src
rebuilt, without the patch, against ruby 1.8.5. Rebuilding the
rubygem-json package against the ruby 1.8.7 packages in our
dependencies repo resolved the parser.so linking errors. I've included
the ldd of the parser.so before and after below as well. The updated
package is now available in our dependencies repo. Please let us know
if this doesn't address your problem.
Apologies for the problems this caused you and thanks much for
bringing the issue to our attention.
Here is the ldd of parser.so with the broken rubygem-json package
ldd -r /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so
undefined symbol:
RSTRING_PTR (/usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so)
undefined symbol:
RSTRING_LEN (/usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so)
linux-vdso.so.1 => (0x00002ae120f0c000)
libruby.so.1.8 => /usr/lib64/libruby.so.1.8 (0x00002ae12131b000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00002ae121619000)
libdl.so.2 => /lib64/libdl.so.2 (0x00002ae121835000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00002ae121a39000)
libm.so.6 => /lib64/libm.so.6 (0x00002ae121c71000)
libc.so.6 => /lib64/libc.so.6 (0x00002ae121ef5000)
librt.so.1 => /lib64/librt.so.1 (0x00002ae12224c000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002ae122455000)
/lib64/ld-linux-x86-64.so.2 (0x00002ae120ef0000)
And the ldd of parser.so from the rebuilt package
ldd -r /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so
linux-vdso.so.1 => (0x00007fff02dfc000)
libruby.so.1.8 => /usr/lib64/libruby.so.1.8 (0x00002b58c627f000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00002b58c657d000)
librt.so.1 => /lib64/librt.so.1 (0x00002b58c6799000)
libdl.so.2 => /lib64/libdl.so.2 (0x00002b58c69a2000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00002b58c6ba6000)
libm.so.6 => /lib64/libm.so.6 (0x00002b58c6ddf000)
libc.so.6 => /lib64/libc.so.6 (0x00002b58c7062000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002b58c73b9000)
/lib64/ld-linux-x86-64.so.2 (0x00002b58c5e54000)
On Wed, Nov 28, 2012 at 9:59 AM, Jeff McCune <j...@puppetlabs.com> wrote:
> On Fri, Nov 23, 2012 at 2:46 PM, Alaric <paxindust...@gmail.com> wrote:
>> Hi,
>>
>> I'm having a weird issue and was wondering if anyone else had run into it.
>> I recently upgraded from puppet 2.7 -> 3.0.1 After cleaning up some gems on
>> my puppet master everything seemed to be working ok. I had originally used
>> the EPEL repo's to deploy puppet, but switched to the Puppet Labs repos so I
>> could upgrade to 2.7 then 3. On RHEL5 only, I get a RSTRING_PTR error if I
>> upgrade to the Puppet Labs version (1.4.6) if I roll back to the EPEL
>> veriosn of rubygem-json (1.4.3) Everything works again.
>
> Has anyone affected by this issue seen
> https://bugzilla.redhat.com/show_bug.cgi?id=634380 ?
>
> This information leads me to believe the rubygem-json package from
> Puppet Labs may not be carrying the same patch that the rubygem-json
> 1.4.3 package from the Fedora Project is carrying. This difference
> may be the cause of the error. Can anyone confirm?
>
> -Jeff
>
> --
> 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.
>
--
Matthaus Owens
Release Manager, Puppet Labs
--
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.
