On Tue, Oct 9, 2012 at 9:59 AM, Joe Hillenbrand <joehil...@gmail.com> wrote: > Same story here. Started with puppet 2.7 on Ubuntu 10.04, did apt-get > upgrade, then it broke. > > I have since switched from storedconfig to PuppetDB, which I highly > recommend to anyone else having this issue. > > On Tue, Oct 9, 2012 at 9:54 AM, Jonathan Gazeley > <jonathan.gaze...@bristol.ac.uk> wrote: >> My version of puppet 2.7 was installed on CentOS 6 from the puppetlabs RPM >> repo with "yum install puppet". When puppet 3 was released, I did a "yum >> update" to get the latest. The issue does not occur with a blank CentOS box >> starting out with puppet 3. >> >> Want me to add this information to the tracked issue? Don't want to add >> unwanted noise to the issue unnecessarily :) >> >> Cheers, >> Jonathan >> >> >> >> On 09/10/12 16:53, Josh Cooper wrote: >>> >>> Jonathan and Luca, >>> >>> How did you install puppet (from source, gem, apt-get, ...)? In the >>> cases that fail, is it always that you installed 2.7.x and upgraded >>> from there? If so, how did you update? >>> >>> We are tracking this issue at http://projects.puppetlabs.com/issues/16770 >>> >>> Josh >>> >>> On Tue, Oct 9, 2012 at 7:30 AM, Luca Gioppo <lucagio...@gmail.com> wrote: >>>> >>>> Same problem for me: >>>> >>>> here is the trace: >>>> Error: Cached catalog for backup.cortile.cloudlabcsi.local failed: Could >>>> not >>>> autoload puppet/indirector/catalog/active_record: uninitialized constant >>>> ActiveRecord >>>> /usr/lib/ruby/site_ruby/1.8/puppet/util/autoload.rb:75:in `load_file' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/util/autoload.rb:208:in `load' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/util/instance_loader.rb:68:in >>>> `loaded_instance' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/indirector/terminus.rb:108:in >>>> `terminus_class' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:313:in >>>> `make_terminus' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:126:in >>>> `terminus' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/indirector/store_configs.rb:6:in >>>> `initialize' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:316:in `new' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:316:in >>>> `make_terminus' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:126:in >>>> `terminus' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:47:in >>>> `cache' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:217:in >>>> `find_in_cache' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:186:in >>>> `find' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:108:in >>>> `do_find' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:71:in `send' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:71:in >>>> `process' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick/rest.rb:24:in >>>> `service' >>>> /usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service' >>>> /usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:33:in `listen' >>>> /usr/lib/ruby/1.8/webrick/server.rb:173:in `call' >>>> /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' >>>> /usr/lib/ruby/1.8/webrick/server.rb:162:in `start' >>>> /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' >>>> /usr/lib/ruby/1.8/webrick/server.rb:95:in `start' >>>> /usr/lib/ruby/1.8/webrick/server.rb:92:in `each' >>>> /usr/lib/ruby/1.8/webrick/server.rb:92:in `start' >>>> /usr/lib/ruby/1.8/webrick/server.rb:23:in `start' >>>> /usr/lib/ruby/1.8/webrick/server.rb:82:in `start' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:30:in `listen' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:29:in >>>> `initialize' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:29:in `new' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:29:in `listen' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:26:in >>>> `synchronize' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:26:in `listen' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:92:in `listen' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:104:in `start' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:136:in `start' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:199:in `main' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:148:in >>>> `run_command' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:438:in `plugin_hook' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:500:in `exit_on_fail' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:346:in `run' >>>> /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:76:in `execute' >>>> /usr/bin/puppet:10 >>>> >>>> and >>>> gem list >>>> >>>> *** LOCAL GEMS *** >>>> >>>> json (1.5.1) >>>> rake (0.8.7) >>>> stomp (1.2.2) >>>> >>>> >>>> >>>> Il giorno mercoledě 3 ottobre 2012 11:26:42 UTC+2, Jonathan Gazeley ha >>>> >>>> scritto: >>>>> >>>>> >>>>> Yesterday my puppetmaster and nodes got upgraded to puppet-3.0.0. >>>>> >>>>> Since then, all puppet runs have been failing with this error: >>>>> >>>>> Error: Could not retrieve catalog from remote server: Error 400 on >>>>> SERVER: Could not autoload puppet/indirector/node/active_record: >>>>> uninitialized constant ActiveRecord >>>>> >>>>> >>>>> My colleague and I have put a few hours into trying to work out what's >>>>> wrong. rubygem-activerecord-2.1.1-2.el6.noarch is installed from the >>>>> puppetlabs RPM repo. We've reinstalled all components but made no >>>>> progress. >>>>> >>>>> I found this thread which seems to describe the same behaviour, but >>>>> there are no replies: >>>>> >>>>> >>>>> https://groups.google.com/forum/?fromgroups=#!topic/puppet-dev/D85TsZ70LKQ >>>>> >>>>> Anyone got any ideas? >>>>> >>>>> Thanks, >>>>> Jonathan >>>> >>>> >>>> -- >>>> 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/-/ZaGpkrLIlRAJ. >>>> >>>> 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. >>> >>> >>> >>> >> >> -- >> 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. >> > > -- > 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. >
We've been able to reproduce this issue in a variety of ways. As far as we can tell, it is always caused by using incompatible versions of activerecord gems. Removing all active* gems and installing the platform-specific packaging containing the activerecord ruby bindings, e.g. apt-get install libactiverecord-ruby, seems to resolve the problem. Can users who are experiencing this problem, please give that a try and let us know? When replying please include the OS & version, ruby versions, gem list and whatever active* packages you are using. Also if you are using alternatives to select ruby 1.9, then puppet 3 will automatically start using it due to its dependency on ruby in addition to ruby1.8. This can cause problems if you were using older activerecord gems, e.g. 2.2.2, in puppet 2.7.x and then upgraded to puppet 3. However, deleting the old gems and installing the platform specific package should resolve the issue. Josh -- Josh Cooper Developer, 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.
