Every body does it now and then - hehehe :-). Its a shame we need to use different interpreters to get things working in the first place really. Lets hope in time this ruby deployment fiasco becomes cleaner.
ken. On May 20, 1:07 am, Chad Huneycutt <chad.huneyc...@gmail.com> wrote: > Thanks for sanity check, Ken. I just copied the library to REE, and > it works fine. Kind of ugly, I guess. > > On Wed, May 19, 2010 at 8:04 PM, Chad Huneycutt > > > > > > <chad.huneyc...@gmail.com> wrote: > > lol. The 'shadow' gem is not the shadow password library! it is "a > > zero-configuration YAML RESTful ActiveRecord server". I guess that > > explains it. Let me see about getting the real library. > > > On Wed, May 19, 2010 at 7:59 PM, Ken <k...@bob.sh> wrote: > >> In the non-enterprise world I believe the library needed is: > > >> [...@obelisk ruby]$ rpm -ql ruby-shadow > >> /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/shadow.so > >> /usr/share/doc/ruby-shadow-1.4.1 > >> /usr/share/doc/ruby-shadow-1.4.1/HISTORY > >> /usr/share/doc/ruby-shadow-1.4.1/README > >> /usr/share/doc/ruby-shadow-1.4.1/README.ja > >> [...@obelisk ruby]$ > > >> Sounds like either there is a library mismatch or it is not installed > >> perhaps? I don't have a ruby-enterprise install here at home - but if > >> you can't see anything obvious about your version of the library I can > >> check on a machine tomorrow. > > >> ken. > > >> On May 20, 12:03 am, Chad Huneycutt <chad.huneyc...@gmail.com> wrote: > >>> So I just upgraded my master from 0.24.8 to 0.25.4. Apparently there > >>> is some bug with the EPEL version of rails that results in mysql "too > >>> many connections" with stored configs, so I just bailed from the > >>> packaged stuff and went to a standalone installation of REE and > >>> puppet. That is working fine, except for one case. There seems to be > >>> some issue with REE and the shadow gem. It installs properly, but > >>> when I get to a User resource, it errors with "Failed to retrieve > >>> current state of resource: uninitialized constant Shadow::Passwd" Is > >>> this a known issue? I guess it isn't really puppet's problem? > > >>> -- > >>> Chad M. Huneycutt > > >>> -- > >>> 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 > >>> athttp://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 > >> athttp://groups.google.com/group/puppet-users?hl=en. > > > -- > > Chad M. Huneycutt > > -- > Chad M. Huneycutt > > -- > 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 > athttp://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.
