Puppet users - Nov 2013 - Permission denied - /usr/share/puppet-dashboard/public/javascripts/all.js

Yes, I know that error has been posted before.  I also know why it occurs. 
 Yet, getting the Dashboard working has become a nightmare.  And for 
someone who wants to eval the entire Puppet package, this is really turning 
me off of it.

A previous post has listed this as a method of making the Dashboard work 
under apache: http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger. 
 But, The instructions listed are for RHEL and I''m using CentOS, which 
shouldn''t be a big deal.  However, it seems to be a problem. 
I''m really
rather stuck on this:

cp /usr/share/puppet/ext/rack/files/apache2.conf 
/etc/httpd/conf.d/rack.conf vim /etc/httpd/conf.d/puppetmaster.conf 
(replace cert paths/filenames with corrent values) mkdir -p 
/etc/puppet/rack/public mkdir -p /etc/puppet/rack/tmp cp 
/usr/share/puppet/ext/rack/files/config.ru /etc/puppet/rack chown puppet 
/etc/puppet/rack/config.ru


These are the RHEL6 instructions, but what gets me is do I copy config.ru 
like it says?  In the Dashboard documentation for the apache setup there is 
absolutely no mention of setting up /etc/puppet/rack.  So far, I''ve
been
incredibly underwhelmed, not by the quantity of the documentation but by 
the fact that it seems to be organized based on chaos theory.  

Has anyone get the dashboard to work under CentOS6?  How did you do it?

If not, where on earth do I start debugging this nightmare?

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/76b6f244-3daa-46aa-b564-858b829d6d03%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

On Friday, November 22, 2013 1:07:21 PM UTC-6, Mark Haney
wrote:
>
> Yes, I know that error has been posted before.  I also know why it occurs. 
>  Yet, getting the Dashboard working has become a nightmare.  And for 
> someone who wants to eval the entire Puppet package, this is really turning
> me off of it.
>

That''s a shame, because Dashboard is an add-on, not part of Puppet.  In
fact, my understanding is that it is no longer supported by PuppetLabs, but 
rather that a third party has assumed maintenance of it.  Puppet Enterprise 
has a built-in, PuppetLabs-supported GUI for what that''s worth.  Or
there
are other GUIs, such as Foreman, for the open-source base product.  Such 
add-ons add value for some users, but they are by no means essential.  I 
don''t use one, for example.


John

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/94dc4fda-bdfc-478a-a7aa-a0eba0684114%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Well, if that''s the case (i.e. you don''t use one), where are
some good
documents on how to manage puppet via CLI?  I''m not married to having a
GUI, but so far the docs on the puppetlabs seem to be organized by chaos 
theory.  I can''t seem to find any decent
''Fisher-Price'' version (IOW,
someone who''s starting with puppet and is quite adept at CLI, but not 
Ruby-adept) documentation to get me started.  It''s incredibly
frustrating.


On Monday, November 25, 2013 10:30:49 AM UTC-5, jcbollinger
wrote:
>
>
>
> On Friday, November 22, 2013 1:07:21 PM UTC-6, Mark Haney wrote:
>>
>> Yes, I know that error has been posted before.  I also know why it 
>> occurs.  Yet, getting the Dashboard working has become a nightmare. 
And
>> for someone who wants to eval the entire Puppet package, this is really
>> turning me off of it.
>>
>
>
> That''s a shame, because Dashboard is an add-on, not part of
Puppet.  In
> fact, my understanding is that it is no longer supported by PuppetLabs, but
> rather that a third party has assumed maintenance of it.  Puppet Enterprise
> has a built-in, PuppetLabs-supported GUI for what that''s worth. 
Or there
> are other GUIs, such as Foreman, for the open-source base product.  Such 
> add-ons add value for some users, but they are by no means essential.  I 
> don''t use one, for example.
>
>
> John
>
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/45d8afa0-d352-42a0-b44f-8c40b5c4638d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi,

I can''t give you much on this, because I''ve never touched
dashboard and
my knowledge of passenger is passing at best. (Also I don''t do
RHEL/CentOS :-)

I believe that the important part is that your rack application
(dashboard) as a home (/etc/puppet/rack) and that is correctly
configured (e.g. in /etc/httpd/conf.d/rack.conf, although I think you
want a vhost-like configuration snippet per rack application).

Do things match up so far?

Next steps:
- restart apache and watch logs for errors
- visit a URI that is supposed to be served through passenger
- watch both apache logs and passenger logs

Rack applications typically do logging in their home tree,
/etc/puppet/rack in your case, I believe.

HTH,
Felix

On 11/22/2013 08:07 PM, Mark Haney wrote:
> 
> If not, where on earth do I start debugging this nightmare?
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/5294A793.3030007%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.