What I found was that you need to gem uninstall ALL of the active* gems, then reinstall and specify 3.0.xx version. Just replacing ActiveRecord won't fix the problem.
I have more notes in my wiki at work, if that doesn't do it I'll grab them for you Monday. On Friday, May 4, 2012 8:52:53 AM UTC-7, Jeff Chapin wrote: > > Is anyone successfully running a puppet master with stored configs on RHEL > 6? If so, would they be able to share version information or setup > documentation? > > Thanks, > Jeff > > On Tue, May 1, 2012 at 1:57 PM, Jeff Chapin <jeff.cha...@uni.edu> wrote: > >> All, >> >> I am trying to install puppet master version 2.7.13 on Red Hat >> Enterprise Linux 6, and utilize stored configs. >> >> I followed the guide here: >> http://projects.puppetlabs.com/projects/1/wiki/Using_Stored_Configuration >> >> When I run puppet --noop on one of the clients, I get the following >> error: >> >> err: Could not retrieve catalog from remote server: Error 400 on >> SERVER: Could not autoload active_record: uninitialized constant >> ActiveRecord >> warning: Not using cache on failed catalog >> err: Could not retrieve catalog; skipping run >> >> Googling this error has a smattering of hits, including one that >> recommends using the 3.0.11 version of the Active Record gem, but I >> get the same error. >> >> I have installed both the 3.2.3 and 3.0.11 versions of the >> ActiveRecord gem (3.0.11 was recomended here: >> >> https://groups.google.com/group/puppet-users/browse_thread/thread/55f29e9454ad5675 >> ) >> >> This error occurs regardless of the DB backend I tie to. I have tried >> both the postgres and mysql documentation. >> >> # ruby --version >> ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] >> # puppet --version >> 2.7.13 >> # puppetmasterd --version >> 2.7.13 >> >> I have searched the puppetlabs issue tracker and found a possibly >> related issue:"Debian Squeeze package puppetmaster: Could not autoload >> active_record: uninitialized constant ActiveRecord"(http:// >> projects.puppetlabs.com/issues/14080). This indicates that I may be >> missing a related package or gem -- but I don't even know where to >> start tracking down the missing package. >> >> On IRC it has been suggested that I install rubygem-activerecord, but >> this does not appear to be in the EPEL repo -- Haus on IRC found a >> 2.3.8 version of this package that I installed to test, but I get the >> same error. I managed to get a different error briefly, when I was >> running multiple versions of activerecord, activeresource and >> activesupport -- installed through a mix of gem and yum. Deleting the >> non-yum versions returned me to the existing error, so I am chalking >> that up as a fluke at this time. >> >> >> Any help would be appreciated. >> >> 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. >> >> > > > -- > > Jeff Chapin, > Assistant Systems/Applications Administrator > ITS-IS, University of Northern Iowa > Phone: 319-273-3162 Email: jeff.cha...@uni.edu > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/VcX6X79A2WsJ. 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.
