puppet-dashboard issue using apache/passenger

214 views
Skip to first unread message

Sans

unread,
May 8, 2012, 1:03:06 PM5/8/12
to puppet...@googlegroups.com
Dear all,

I've switched to apache/passenger for puppet-dashboard, following the instruction here:
 
http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#running-dashboard-in-a-production-quality-server
 

httpd
is running okay but I see it's dashboard still seems to use WEBrick (and default port 3000); I see this if I start  puppet-dashboard

[root@serv05 puppet-dashboard]# service puppet-dashboard start
Starting Puppet Dashboard: => Booting WEBrick
=> Rails 2.3.14 application starting on http://0.0.0.0:3000
                                                           [  OK  ]

(and also puppet-dashboard GUI doesn't run on the port I specified in the apache configuration file). What am I still missing? Cheers!!

Walter Heck

unread,
May 8, 2012, 5:01:02 PM5/8/12
to puppet...@googlegroups.com

don't start the puppet-dashboard service anymore. Once you have defined your vhost in apache properly, starting apache will make it start serving your dashboard.

Sent from my galaxy tab

--
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/-/hXU0QAukuTsJ.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

Sans

unread,
May 8, 2012, 5:10:13 PM5/8/12
to puppet...@googlegroups.com

aahh....... that's what I was wondering.
So, does it also mean there is no need for reports, reportdir and reporturl in the puppet.conf as well? Cheers!!

Craig White

unread,
May 9, 2012, 11:42:01 AM5/9/12
to puppet...@googlegroups.com
-----
No - you will still want to have configuration for reporting but you should note that if you used specific port notations such as port 3000 for the webrick server that it isn't needed.

Craig

Reply all
Reply to author
Forward
0 new messages