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 nothing from Apache in > `/var/log/puppet/dashboard_error.log`.
Hi Rob, The "something went wrong" message is shown in the Rails production environment instead of the error message and stack trace you would see in the development environment. Unfortunately, it tells us nothing about what's actually wrong. If the production.log file is empty, it might be a permissions issue for the user you use to run Apache (can't write to the log). Since the production log doesn't show anything, you can try running script/server from the Dashboard's directory. This will start a Ruby server (probably Webrick) in development mode. If the problem is during boot, it'll dump an error message. Otherwise, if you make a request to that machine's host at port 3000, you should see an actual error report in your browser and in the standard output of the server (and in your log/development.log). If not, it may be specific to the production environment (unlikely) or to your Passenger setup (more likely). Let us know and we can continue to troubleshoot. Once we get some more information, we should be able to figure out what's going on. Thanks! -- Rein Henrichs http://puppetlabs.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
