Hi Richard, This is caused by Puppet::Application::Agent attempting to reference Puppet::Network::Handler before it's been loaded. It's one of these load-order issues where it may work in some cases because some other code, e.g. lib/puppet/network/client.rb, requires puppet/network/handler, and happens to be loaded before lib/puppet/application/agent.rb. The easiest thing is to add:
require 'puppet/network/handler' to lib/puppet/application/agent.rb. Also note that the 2.6.13 "release is the final maintenance release of the 2.6.x series of Puppet. Further releases in this series will only be issues to address security concerns"[1] I'd recommend upgrading to the latest 2.7.x version to see if the error persists, and if so, open a ticket. Josh [1] http://groups.google.com/group/puppet-announce/browse_thread/thread/1b51a0bfb662082f On Wed, Dec 28, 2011 at 3:39 AM, eRefre <[email protected]> wrote: > Bump. > > No one that has a clue? > > On Dec 14, 4:00 am, Richard Olofsson <[email protected]> wrote: > > Hi. > > > > We have started to receive some strange errors when running puppet agent > on > > some hosts in our datacenter. > > We have about 500 clients and there are about 30 that gives us this > error: > > > > /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:53:in > > `handle_serve': uninitialized constant Puppet::Network::Handler > (NameError) > > from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:329:in `send' > > from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:329:in > > `parse_options' > > from /usr/lib/ruby/1.8/optparse.rb:1247:in `call' > > from /usr/lib/ruby/1.8/optparse.rb:1247:in `order!' > > from /usr/lib/ruby/1.8/optparse.rb:1205:in `catch' > > from /usr/lib/ruby/1.8/optparse.rb:1205:in `order!' > > from /usr/lib/ruby/1.8/optparse.rb:1279:in `permute!' > > from /usr/lib/ruby/1.8/optparse.rb:1300:in `parse!' > > from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:335:in > > `parse_options' > > from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:284:in `run' > > from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:393:in > > `exit_on_fail' > > from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:284:in `run' > > from /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:55:in > > `execute' > > from /usr/bin/puppet:4 > > > > It has worked before and there has not been any change to the system > > configuration. > > > > This affects both Suse and Redhat servers. > > > > I have reinstalled the ruby dependencies and puppet but the error still > > persists. > > > > When checking the logs it says that the service has been executed and i > can > > see that the files and configuration has been applied. > > *puppet-agent[7067]: Finished catalog run in 1.11 seconds > > * > > *puppet agent --version* > > 2.6.4 > > * > > ruby-libs-1.8.5-5.el5_4.8 > > ruby-1.8.5-5.el5_4.8 > > > > puppetmasterd --version* > > 2.6.4 > > > > Any clues what might be the problem? > > > > Regards > > Richard. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
