On Nov 26, 2012, at 10:29 PM, Michael Stahnke <stah...@puppetlabs.com> wrote:
> On Mon, Nov 26, 2012 at 2:16 PM, Alaric <paxindust...@gmail.com> wrote: >> >> On Nov 26, 2012, at 4:46 PM, Michael Stahnke <stah...@puppetlabs.com> wrote: >> >>> >>> I tried to reproduce this and just couldn't. Does this happen on >>> other systems? >>> >>> Is there any more information you could think of? >>> >> >> >> Sadly, it's happening on every RHEL5 system I have! All packages are either >> RedHat or EPEL, or now PuppetLabs, I can't really think of anything that >> would cause a conflict. It happens on both VM's and Physical hardware. I >> did have a number of gems running to support hiera before I upgrade to >> Puppet 3.0.1 but I got rid of them on the master when I upgraded. It's >> really perplexing, especially since all the other packages from puppetlabs >> seem to have been installed and are working... > > If you disable hiera (like have a really simple catalog or something) > does it still happen? > Yup, I get the same error: /usr/bin/ruby: symbol lookup error: /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so: undefined symbol: RSTRING_PTR My one thought is that maybe my version stdlib is old... I checked and it's version 2.3.1 I'll give it an upgrade and see if that helps, it's just weird that on the RHEL6 servers nothing seems off. -- 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.
