Ask Your Question

Passenger won't start - undefined method `settings' for Puppet:Module

asked 2012-11-01 16:57:45 -0500

Dawn gravatar image

updated 2013-01-03 14:24:54 -0500

llowder gravatar image

Attribution: Thomas originally asked this question on puppet-users

After upgrading my puppet server to Puppet 3.0 I got the following error every time a client connect to the server:

[ pid=1532 thr=70147393710520 file=utils.rb:176 time=2012-10-08 11:17:56.504 ]: *** Exception
NoMethodError in PhusionPassenger::Rack::ApplicationSpawner (undefined method `settings' for
Puppet:Module) (process 1532, thread #<Thread:0x7f98ecf7d370>):
        from /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:273:in `run_mode'
        from /usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:5
        from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require'
        from ...
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2012-11-01 17:11:46 -0500

updated 2012-11-01 17:13:43 -0500

This error message is a bit misleading, this issue is caused by a passenger configuration file that does not specify the --confdir and --vardir settings. Please make sure you have these two options set to the confdir and vardir Puppet 2.7 was using and Puppet 3.0 should start right up.

For example,

# a, for use with every rack-compatible webserver.
# SSL needs to be handled outside this, though.

# if puppet is not in your RUBYLIB:
# $LOAD_PATH.unshift('/opt/puppet/lib')

$0 = "master"

# if you want debugging:
# ARGV << "--debug"

ARGV << "--rack"

# Rack applications typically don't ...
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2012-11-01 16:57:45 -0500

Seen: 614 times

Last updated: Nov 01 '12