Hi folks, I am having the exact same problem. The Webrick works fine but the apache/passenger server does not. What would I need to have installed in ruby in order to ensure the connection between dashboard-passenger and the mysql that I don't need with the webrick? The /tmp (or do you mean the mysql.socket file?) the permission would have to be 777 right?
ps.: I also got the migration version (no_migration_check) error (probably because passenger can't read/write from/to mysql ) so when I set the env no_migration_check = 1 I got the 500 error... Thanks! On Monday, November 25, 2013 1:52:24 PM UTC-2, Felix.Frank wrote: > > Hi, > > my guess would be that this error is handed through from MySQL itself. > > Are there perhaps problems with the permissions on your /tmp? > > It is indeed strange that Webrick behaves different from passenger for > this use case, though. Can you somehow make absolutely certain that ruby > is contacting the correct MySQL instance? > > Cheers, > Felix > > On 11/21/2013 05:40 PM, Jason Friedrich wrote: > > When I try to hit the site though, I am getting the message "Puppet > > Dashboard encountered an error. Something went wrong, and Puppet > > Dashboard was unable to render the requested page [...]" and a strange > > errror output in the production.log file (http://pastebin.com/aYYBRkEX). > > > > > I do not understand why Puppet Dashboard tries to create a MYI file in > > /tmp. It should not create anything locally at all. It should use the > > configured MySQL server. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/cd862ddd-e8bf-4643-b59d-07f226e548c6%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
