Hi Jeff,
Here is my *config.ru* (after adding the debug option):
*## cat /etc/puppet/rack/config.ru*
# a config.ru, for use with every rack-compatible webserver.
> # SSL needs to be handled outside this, though.
>
> # if puppet is not in your RUBYLIB:
> # $:.unshift('/opt/puppet/lib')
>
> $0 = "master"
>
> # if you want debugging:
> ARGV << "--debug"
> # ARGV << "--trace"
> ARGV << "--rack"
> require 'puppet/application/master'
> # we're usually running inside a Rack::Builder.new {} block,
> # therefore we need to call run *here*.
> run Puppet::Application[:master].run
>
Anything unusual you see in there?
-San
On Monday, June 11, 2012 10:14:59 PM UTC+1, Jeff McCune wrote:
>
> On Mon, Jun 11, 2012 at 1:49 PM, Sans <[email protected]> wrote:
> > Hi Den, jeff,
> > Sorry for my late reply.
> >
> > Yes, I do have puppetmaster-vost.conf and I've separated the passenger
> > config file. So, this is what I have:
>
> I'd try and enable moer debugging information. It seems to me Puppet
> is refusing to start for some reason and passenger doesn't know what
> to do with a process that is dying underneath it.
>
> In config.ru you can pass the --debug and --trace options to the
> puppet master startup process. These should then show up in the HTTP
> response from passenger or the httpd_error log.
>
> Could you also paste the config.ru file you're using?
>
> -Jeff
>
--
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/-/So7egVCZkHgJ.
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.
