Hi San,
Do you still have your httpd puppet master vhost listening on the non
standard port? That is fine, as long as you configure your clients like has
been mentioned before. Puppet clients will try to reach port 8140 unless
you specify otherwise.
In your config.ru you can see how passenger calls the puppet master
application:
# therefore we need to call run *here*.
> run Puppet::Application[:master].run
>
You don't need to have the webrick puppet master running at all. The
config.ru which is read by apache/passenger handles the launching of the
puppet master application. You should make sure you are not running the
master as a webrick server.
But it not going to work unless you have your clients hitting the port you
have configured your puppet master vhost in apache (which ever port you
choose to run it on) - they should be the same.
Cheers,
Den
On 12/06/2012, at 16:32, Sans <r.santanu....@gmail.com> wrote:
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 <r.santanu....@gmail.com> 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 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.
