Re: [Puppet Users] ANNOUNCE: Puppet Dashboard 1.0.3 released

2010-08-03 Thread Rob McBroom
On Aug 3, 2010, at 2:30 PM, Rein Henrichs wrote: > Rob, looks like you've already resolved the issue. Yes. Thanks everyone for the responses. -- Rob McBroom -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to

Re: [Puppet Users] ANNOUNCE: Puppet Dashboard 1.0.3 released

2010-08-03 Thread Rein Henrichs
Excerpts from Rein Henrichs's message of Tue Aug 03 10:15:05 -0700 2010: > Once we get some more information, we should be able to figure out > what's going on. > > Thanks! Rob, looks like you've already resolved the issue. I guess I was late to the party. Glad you got it sorted. -- Rein Henrich

Re: [Puppet Users] ANNOUNCE: Puppet Dashboard 1.0.3 released

2010-08-03 Thread Igal Koshevoy
On 08/03/2010 10:19 AM, Rob McBroom wrote: > On Aug 3, 2010, at 10:40 AM, Igal Koshevoy wrote: > > >> The application was failing at startup because it couldn't write its own >> log files, and now it's failing because it can't write its caches. >> >> Please give ownership of the "puppet-dashboar

Re: [Puppet Users] ANNOUNCE: Puppet Dashboard 1.0.3 released

2010-08-03 Thread James Turnbull
Rob McBroom wrote: > Now, some questions: > 3. If it is necessary, should it be mentioned in the installation > instructions? This one is my fault - I dropped the ball here - I tested the install but thought the permissions problem was my fault rather than an issue. Regards James Turnbull --

Re: [Puppet Users] ANNOUNCE: Puppet Dashboard 1.0.3 released

2010-08-03 Thread Igal Koshevoy
On 08/03/2010 06:01 AM, Rob McBroom wrote: > On Aug 2, 2010, at 5:39 PM, James Turnbull wrote: > > >> Is there anything in /var/log/apache/error.log? >> > What the…? Yes. Why isn’t it going to the ErrorLog for that virtual host? > > Anyway, there were a number of these: > > Rails Error:

Re: [Puppet Users] ANNOUNCE: Puppet Dashboard 1.0.3 released

2010-08-03 Thread Rob McBroom
On Aug 3, 2010, at 10:40 AM, Igal Koshevoy wrote: > The application was failing at startup because it couldn't write its own > log files, and now it's failing because it can't write its caches. > > Please give ownership of the "puppet-dashboard" directory and everything > in it to the same user,

Re: [Puppet Users] ANNOUNCE: Puppet Dashboard 1.0.3 released

2010-08-03 Thread Rein Henrichs
Excerpts from Rob McBroom's message of Mon Aug 02 12:40:21 -0700 2010: > I updated to 1.0.3 and now all I get from the web interface is the > “something went wrong” message. All I really need to know is where to > look for clues. There’s nothing in > `puppet-dashboard/log/production.log` and nothin

Re: [Puppet Users] ANNOUNCE: Puppet Dashboard 1.0.3 released

2010-08-03 Thread Rob McBroom
On Aug 2, 2010, at 5:39 PM, James Turnbull wrote: > Is there anything in /var/log/apache/error.log? What the…? Yes. Why isn’t it going to the ErrorLog for that virtual host? Anyway, there were a number of these: Rails Error: Unable to access log file. Please ensure that /opt/puppet-dashboa

Re: [Puppet Users] ANNOUNCE: Puppet Dashboard 1.0.3 released

2010-08-02 Thread James Turnbull
Rob McBroom wrote: > OK, I need some help here. > > I updated to 1.0.3 and now all I get from the web interface is the “something > went wrong” message. All I really need to know is where to look for clues. > There’s nothing in `puppet-dashboard/log/production.log` and nothing from > Apache in

Re: [Puppet Users] ANNOUNCE: Puppet Dashboard 1.0.3 released

2010-08-02 Thread Rob McBroom
OK, I need some help here. I updated to 1.0.3 and now all I get from the web interface is the “something went wrong” message. All I really need to know is where to look for clues. There’s nothing in `puppet-dashboard/log/production.log` and nothing from Apache in `/var/log/puppet/dashboard_erro

[Puppet Users] ANNOUNCE: Puppet Dashboard 1.0.3 released

2010-07-30 Thread James Turnbull
And we're back fast and furious with another Dashboard release ... 1.0.3 ... this one so hot we skipped 1.0.2 altogether. The 1.0.3 release is another maintenance release that fixes bugs and issues with the 1.0.1 release. We're planning a 1.1 release in the near future that will add additional fe