On all 3 of my servers, after a routine aptitude upgrade, I''m now getting: ec2-www1# puppetd -tv info: Retrieving plugins info: Retrieving facts err: Could not retrieve catalog: Rails is missing; cannot store configurations warning: Not using cache on failed catalog When I went to restart puppetmasterd on the master, I got what I assume is the explanation: Failed to load feature test for rails: undefined method `synchronize'' for ActiveRecord::ConnectionAdapters::ConnectionPool:Class I guess some library changed, but I really don''t know enough about Rails to guess which one, and I haven''t seen anything that looks helpful in google yet. -Robin -- They say: "The first AIs will be built by the military as weapons." And I''m thinking: "Does it even occur to you to try for something other than the default outcome?" -- http://shorl.com/tydruhedufogre http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/ --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Sun, Mar 01, 2009 at 03:36:35PM -0800, Robin Lee Powell wrote:> > > On all 3 of my servers, after a routine aptitude upgrade, I''m now > getting: > > ec2-www1# puppetd -tv > info: Retrieving plugins > info: Retrieving facts > err: Could not retrieve catalog: Rails is missing; cannot store configurations > warning: Not using cache on failed catalog > > When I went to restart puppetmasterd on the master, I got what I > assume is the explanation: > > Failed to load feature test for rails: undefined method `synchronize'' for ActiveRecord::ConnectionAdapters::ConnectionPool:Class > > I guess some library changed, but I really don''t know enough about > Rails to guess which one, and I haven''t seen anything that looks > helpful in google yet.I''ve tried to dig through the Puppet code to find out where the check is occuring so I can shut it the hell up, since Rails *is* installed, but I can''t find it. I guess it might be /usr/src/puppet-0.24.7/lib/puppet/feature/rails.rb , but if so I don''t understand how. Puppet completely isn''t working; help would be greatly appreciated. -Robin -- They say: "The first AIs will be built by the military as weapons." And I''m thinking: "Does it even occur to you to try for something other than the default outcome?" -- http://shorl.com/tydruhedufogre http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/ --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
if you don''t use storeconfig, you can probably turn it off and avoid using rails at all. if not, I would guess you have a newer version of rails that puppet can handle, I''m *guessing* that you can remove your current rails version and install using gem rails-2.0.2 or similar... Cheers, Ohad On Mon, Mar 2, 2009 at 1:11 PM, Robin Lee Powell < rlpowell@digitalkingdom.org> wrote:> > On Sun, Mar 01, 2009 at 03:36:35PM -0800, Robin Lee Powell wrote: > > > > > > On all 3 of my servers, after a routine aptitude upgrade, I''m now > > getting: > > > > ec2-www1# puppetd -tv > > info: Retrieving plugins > > info: Retrieving facts > > err: Could not retrieve catalog: Rails is missing; cannot store > configurations > > warning: Not using cache on failed catalog > > > > When I went to restart puppetmasterd on the master, I got what I > > assume is the explanation: > > > > Failed to load feature test for rails: undefined method `synchronize'' > for ActiveRecord::ConnectionAdapters::ConnectionPool:Class > > > > I guess some library changed, but I really don''t know enough about > > Rails to guess which one, and I haven''t seen anything that looks > > helpful in google yet. > > I''ve tried to dig through the Puppet code to find out where the > check is occuring so I can shut it the hell up, since Rails *is* > installed, but I can''t find it. I guess it might be > /usr/src/puppet-0.24.7/lib/puppet/feature/rails.rb , but if so I > don''t understand how. > > Puppet completely isn''t working; help would be greatly appreciated. > > -Robin > > -- > They say: "The first AIs will be built by the military as weapons." > And I''m thinking: "Does it even occur to you to try for something > other than the default outcome?" -- http://shorl.com/tydruhedufogre > http://www.digitalkingdom.org/~rlpowell/<http://www.digitalkingdom.org/%7Erlpowell/>*** > http://www.lojban.org/ > > > >--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Robin Lee Powell wrote:> On Sun, Mar 01, 2009 at 03:36:35PM -0800, Robin Lee Powell wrote: >> >> On all 3 of my servers, after a routine aptitude upgrade, I''m now >> getting: >> >> ec2-www1# puppetd -tv >> info: Retrieving plugins >> info: Retrieving facts >> err: Could not retrieve catalog: Rails is missing; cannot store configurations >> warning: Not using cache on failed catalog >> >> When I went to restart puppetmasterd on the master, I got what I >> assume is the explanation: >> >> Failed to load feature test for rails: undefined method `synchronize'' for ActiveRecord::ConnectionAdapters::ConnectionPool:Class >> >> I guess some library changed, but I really don''t know enough about >> Rails to guess which one, and I haven''t seen anything that looks >> helpful in google yet. > > I''ve tried to dig through the Puppet code to find out where the > check is occuring so I can shut it the hell up, since Rails *is* > installed, but I can''t find it. I guess it might be > /usr/src/puppet-0.24.7/lib/puppet/feature/rails.rb , but if so I > don''t understand how. > > Puppet completely isn''t working; help would be greatly appreciated.Robin Platform? Rails version - old and upgraded to? Did Rails upgrade during your aptitude upgrade? Puppet version? Cheers James - -- Author of: * Pulling Strings with Puppet (http://www.amazon.com/gp/product/1590599780/) * Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) * Hardening Linux (http://www.amazon.com/gp/product/1590594444/) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJq3OD9hTGvAxC30ARAop9AJ9hPKTktM3sAtHEN7ksSzrrJVnezQCff8Oa JgVWkbrPSWrTbJRh+h/zk3c=m5Kv -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Mon, Mar 02, 2009 at 04:49:55PM +1100, James Turnbull wrote:> > Platform?Debian. All 3 seem to be lenny at this point, but at least on pulls testing as well.> Rails version - old and upgraded to? Did Rails upgrade > during your aptitude upgrade?I wasn''t paying attention to exactly what upgraded. It was a routine more-or-less weekly thing. The master says that the Debain rails package is 2.1.0-6. The other three don''t have it as Debian packages at all, and I don''t know where else to look for it.> Puppet version?0.24.7, from source. What does Puppet even need Rails for, anyways? I thought it was just storeconfigs, but I tried taking that out of the puppet.conf and it didn''t seem to help. -Robin -- They say: "The first AIs will be built by the military as weapons." And I''m thinking: "Does it even occur to you to try for something other than the default outcome?" -- http://shorl.com/tydruhedufogre http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/ --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Yeah, changing to "storeconfigs = false" in puppet.conf doesn''t seem to change the behaviour. Oh, wait, scratch that. It still emits the error, but then goes on to actually run. That is, it was doing this: $ puppetd -tv Failed to load feature test for rails: undefined method `synchronize'' for ActiveRecord::ConnectionAdapters::ConnectionPool:Class info: Retrieving plugins err: Could not retrieve catalog: Rails is missing; cannot store configurations warning: Not using cache on failed catalog $ Now it does this: $ puppetd -tv Failed to load feature test for rails: undefined method `synchronize'' for ActiveRecord::ConnectionAdapters::ConnectionPool:Class info: Retrieving plugins info: Caching catalog at /var/lib/puppet/state/localconfig.yaml notice: Starting catalog run notice: Finished catalog run in 9.99 seconds $ Switching storeconfigs and restarting puppetmasterd is enough to switch between the two behaviours. Downgrading rails (via dpkg) from 2.1.0-6 to 2.0.2-2 did not seem to make the error go away. I am now functional again; yay. If anyone wants more details to help track this down as a bug, please let me know. Hell, you can have a shell account if you like. :) -Robin On Mon, Mar 02, 2009 at 01:30:20PM +0800, Ohad Levy wrote:> if you don''t use storeconfig, you can probably turn it off and > avoid using rails at all. > > if not, I would guess you have a newer version of rails that puppet can > handle, I''m *guessing* that you can remove your current rails version and > install using gem rails-2.0.2 or similar... > > Cheers, > Ohad > > On Mon, Mar 2, 2009 at 1:11 PM, Robin Lee Powell < > rlpowell@digitalkingdom.org> wrote: > > > > > On Sun, Mar 01, 2009 at 03:36:35PM -0800, Robin Lee Powell wrote: > > > > > > > > > On all 3 of my servers, after a routine aptitude upgrade, I''m now > > > getting: > > > > > > ec2-www1# puppetd -tv > > > info: Retrieving plugins > > > info: Retrieving facts > > > err: Could not retrieve catalog: Rails is missing; cannot store > > configurations > > > warning: Not using cache on failed catalog > > > > > > When I went to restart puppetmasterd on the master, I got what I > > > assume is the explanation: > > > > > > Failed to load feature test for rails: undefined method `synchronize'' > > for ActiveRecord::ConnectionAdapters::ConnectionPool:Class > > > > > > I guess some library changed, but I really don''t know enough about > > > Rails to guess which one, and I haven''t seen anything that looks > > > helpful in google yet. > > > > I''ve tried to dig through the Puppet code to find out where the > > check is occuring so I can shut it the hell up, since Rails *is* > > installed, but I can''t find it. I guess it might be > > /usr/src/puppet-0.24.7/lib/puppet/feature/rails.rb , but if so I > > don''t understand how. > > > > Puppet completely isn''t working; help would be greatly appreciated. > > > > -Robin > > > > -- > > They say: "The first AIs will be built by the military as weapons." > > And I''m thinking: "Does it even occur to you to try for something > > other than the default outcome?" -- http://shorl.com/tydruhedufogre > > http://www.digitalkingdom.org/~rlpowell/<http://www.digitalkingdom.org/%7Erlpowell/>*** > > http://www.lojban.org/ > > > > > > > > > >-- They say: "The first AIs will be built by the military as weapons." And I''m thinking: "Does it even occur to you to try for something other than the default outcome?" -- http://shorl.com/tydruhedufogre http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/ --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Robin Lee Powell wrote:> Yeah, changing to "storeconfigs = false" in puppet.conf doesn''t seem > to change the behaviour. > > Oh, wait, scratch that. > > It still emits the error, but then goes on to actually run. That > is, it was doing this: > > $ puppetd -tv > Failed to load feature test for rails: undefined method `synchronize'' for ActiveRecord::ConnectionAdapters::ConnectionPool:Class > info: Retrieving plugins > err: Could not retrieve catalog: Rails is missing; cannot store configurations > warning: Not using cache on failed catalog > $ > > Now it does this: > > $ puppetd -tv > Failed to load feature test for rails: undefined method `synchronize'' for ActiveRecord::ConnectionAdapters::ConnectionPool:Class > info: Retrieving plugins > info: Caching catalog at /var/lib/puppet/state/localconfig.yaml > notice: Starting catalog run > notice: Finished catalog run in 9.99 seconds > $ > > Switching storeconfigs and restarting puppetmasterd is enough to > switch between the two behaviours. > > Downgrading rails (via dpkg) from 2.1.0-6 to 2.0.2-2 did not seem to > make the error go away. > > I am now functional again; yay. If anyone wants more details to > help track this down as a bug, please let me know. Hell, you can > have a shell account if you like. :)Any chance you could log as a ticket please Robin? Thanks James Turnbull - -- Author of: * Pulling Strings with Puppet (http://www.amazon.com/gp/product/1590599780/) * Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) * Hardening Linux (http://www.amazon.com/gp/product/1590594444/) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJq39/9hTGvAxC30ARArd6AJ4hxLvogNdjj9Pz63zMPpCBl317RACggyqV EsqhrQrBATvQuPs/b5GKELk=t/Hh -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Mon, Mar 02, 2009 at 05:41:03PM +1100, James Turnbull wrote:> Robin Lee Powell wrote: > > Yeah, changing to "storeconfigs = false" in puppet.conf doesn''t seem > > to change the behaviour. > > > > Oh, wait, scratch that. > > > > It still emits the error, but then goes on to actually run. That > > is, it was doing this: > > > > $ puppetd -tv > > Failed to load feature test for rails: undefined method `synchronize'' for ActiveRecord::ConnectionAdapters::ConnectionPool:Class > > info: Retrieving plugins > > err: Could not retrieve catalog: Rails is missing; cannot store configurations > > warning: Not using cache on failed catalog > > $ > > > > Now it does this: > > > > $ puppetd -tv > > Failed to load feature test for rails: undefined method `synchronize'' for ActiveRecord::ConnectionAdapters::ConnectionPool:Class > > info: Retrieving plugins > > info: Caching catalog at /var/lib/puppet/state/localconfig.yaml > > notice: Starting catalog run > > notice: Finished catalog run in 9.99 seconds > > $ > > > > Switching storeconfigs and restarting puppetmasterd is enough to > > switch between the two behaviours. > > > > Downgrading rails (via dpkg) from 2.1.0-6 to 2.0.2-2 did not seem to > > make the error go away. > > > > I am now functional again; yay. If anyone wants more details to > > help track this down as a bug, please let me know. Hell, you can > > have a shell account if you like. :) > > Any chance you could log as a ticket please Robin?Certainly. I don''t like to do that until I''ve checked with others to make sure I''m not just being a moron. :) http://projects.reductivelabs.com/issues/2041 -Robin -- They say: "The first AIs will be built by the military as weapons." And I''m thinking: "Does it even occur to you to try for something other than the default outcome?" -- http://shorl.com/tydruhedufogre http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/ --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---