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 puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52937238.2020502%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/groups/opt_out.
