about2flip
2009-Sep-22 11:15 UTC
RE: We''re sorry something went wrong when I use -d mysql
Hi: I am trying to make an application using mysql. When I do rails name -- d mysql, and then run mongrel. I will go to localhost:3000 and when i check my application environment, I get an error We''re sorry something went wrong. Now, when I do the same procedure without using --d mysql and just use the defalt sqllite. When I check my application environment it shows the information. Why does it not work when I try to use mysql? Thanks
Norm Scherer
2009-Sep-22 16:46 UTC
Re: We''re sorry something went wrong when I use -d mysql
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> about2flip wrote: <blockquote cite="mid:694860ef-a057-4049-869b-252894a90a05-PyBfabkJhOvuWmCA52lKz1YGCWtFR9XvxddQ6fo/n9Y@public.gmane.orgom" type="cite"> <pre wrap="">Hi: I am trying to make an application using mysql. When I do rails name -- d mysql, and then run mongrel. I will go to localhost:3000 and when i check my application environment, I get an error We''re sorry something went wrong. Now, when I do the same procedure without using --d mysql and just use the defalt sqllite. When I check my application environment it shows the information. Why does it not work when I try to use mysql? Thanks </pre> </blockquote> I would look in database.yml to see that things are like you expect. Maybe rails has a different idea of what the socket should be. Check the values of the socket, username and password (if used) and make sure the database exists with the name shown in the database.yml.<br> <br> Norm<br> <br> --~--~---------~--~----~------------~-------~--~----~<br> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. <br> To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <br> To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <br> For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en<br> -~----------~----~----~----~------~----~------~--~---<br> </body> </html> <br>
Ludmila Moraes
2009-Sep-22 16:58 UTC
Re: We''re sorry something went wrong when I use -d mysql
check in your file database.yml Maybe you have to configure the adapter: mysql or check if you are using password in mysql 2009/9/22 Norm Scherer <normscherer-ihVZJaRskl1bRRN4PJnoQQ@public.gmane.org>> about2flip wrote: > > Hi: > > I am trying to make an application using mysql. When I do rails name -- > d mysql, and then run mongrel. I will go to localhost:3000 and when i > check my application environment, I get an error We''re sorry something > went wrong. > > Now, when I do the same procedure without using --d mysql and just use > the defalt sqllite. When I check my application environment it shows > the information. > > Why does it not work when I try to use mysql? > > Thanks > > > I would look in database.yml to see that things are like you expect. > Maybe rails has a different idea of what the socket should be. Check the > values of the socket, username and password (if used) and make sure the > database exists with the name shown in the database.yml. > > Norm > > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Hassan Schroeder
2009-Sep-22 17:08 UTC
Re: We''re sorry something went wrong when I use -d mysql
> check in your file database.yml> or check if you are using password in mysql*or* look at the log file to find out what *actually* went wrong... -- Hassan Schroeder ------------------------ hassan.schroeder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org twitter: @hassan
Reasonably Related Threads
- Authlogic Password confirmation is too short Error. NEED HELP.
- moved from ruby 1.8.6 to 1.8.7 and "We're sorry, but something went wrong."
- Image_tag Positioning/Alignment
- We're sorry, but something went wrong.
- We're sorry, but something went wrong on Tomcat