Saved us as well... had the same problem and ours was in group: http:www in
stead of puppet:puppet. Changing it made everything work once again.
Thanks a bunch!
Andrew.
On Saturday, July 27, 2013 at 2:14:36 AM UTC+2, GregC wrote:
>
> i just went through same issue.
>
> 1. /etc/puppet/rack/pupp
Thank you. I just ran into this also, and your post had the info I needed.
--
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+unsubscr...@googlegroups
I found that. And I was royally peeved, as nowhere in the logs was there
any indication there was an issue. The developers of Passenger pointed
out that I can set options in the httpd.conf to specify a user and group --
but these products should be logging better data.
I literally spent days
i just went through same issue.
1. /etc/puppet/rack/puppetmaster/config.ru should be puppet:puppet
2. /var/log/puppet/masterhttp.log neexds to have permission set, not at my
computer but i think its 644.
youWill see error message in /var/log/messages. hope this helps
--
You received this messa
As I recall, if the config.ru itself isn't owned by the puppet user, we'll
get similar errors from Passenger (spewing out an HTML error page, which
the agents then unhelpfully log).
It might be something else -- given that it's HTML, you might want to just
go to https://:8140 in a browser and s
