Hi there everyone, On my production server I start the mongrel server as follows: mongrel_rails start -e production -a 127.0.0.1 -p 3001 -d However when going to the domain I get the following error: #42000Unknown database ''satechevents_development'' Why is rails looking for the development database in production mode. Thanks for the help, Schalk --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
On 2 Oct 2008, at 15:43, Schalk Neethling wrote:> > Hi there everyone, > > On my production server I start the mongrel server as follows: > > mongrel_rails start -e production -a 127.0.0.1 -p 3001 -d > > However when going to the domain I get the following error: > > #42000Unknown database ''satechevents_development'' >Assuming your database.yml is sane, are you sure that the requests are actually going to that mongrel ? for example if you had a separate mongrel already running in dev mode, then the second one would just fail to start (possibly silently seing as you''ve passed -d). Fred> Why is rails looking for the development database in production mode. > > Thanks for the help, > Schalk > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Thanks Fred, I will look into this. How can I ensure that all instances of mongrel is stopped? Schalk Frederick Cheung wrote:> > On 2 Oct 2008, at 15:43, Schalk Neethling wrote: > >> Hi there everyone, >> >> On my production server I start the mongrel server as follows: >> >> mongrel_rails start -e production -a 127.0.0.1 -p 3001 -d >> >> However when going to the domain I get the following error: >> >> #42000Unknown database ''satechevents_development'' >> > Assuming your database.yml is sane, are you sure that the requests are > actually going to that mongrel ? for example if you had a separate > mongrel already running in dev mode, then the second one would just > fail to start (possibly silently seing as you''ve passed -d).--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
On 2 Oct 2008, at 15:51, Schalk Neethling wrote:> > Thanks Fred, > > I will look into this. How can I ensure that all instances of > mongrel is > stopped? >look at the output of ps ? Fred> Schalk > > Frederick Cheung wrote: >> >> On 2 Oct 2008, at 15:43, Schalk Neethling wrote: >> >>> Hi there everyone, >>> >>> On my production server I start the mongrel server as follows: >>> >>> mongrel_rails start -e production -a 127.0.0.1 -p 3001 -d >>> >>> However when going to the domain I get the following error: >>> >>> #42000Unknown database ''satechevents_development'' >>> >> Assuming your database.yml is sane, are you sure that the requests >> are >> actually going to that mongrel ? for example if you had a separate >> mongrel already running in dev mode, then the second one would just >> fail to start (possibly silently seing as you''ve passed -d). > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
ps -ef | grep ''mongrel'' On Oct 2, 4:01 pm, Frederick Cheung <frederick.che...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On 2 Oct 2008, at 15:51, Schalk Neethling wrote: > > > > > Thanks Fred, > > > I will look into this. How can I ensure that all instances of > > mongrel is > > stopped? > > look at the output of ps ? > > Fred > > > Schalk > > > Frederick Cheung wrote: > > >> On 2 Oct 2008, at 15:43, Schalk Neethling wrote: > > >>> Hi there everyone, > > >>> On my production server I start the mongrel server as follows: > > >>> mongrel_rails start -e production -a 127.0.0.1 -p 3001 -d > > >>> However when going to the domain I get the following error: > > >>> #42000Unknown database ''satechevents_development'' > > >> Assuming your database.yml is sane, are you sure that the requests > >> are > >> actually going to that mongrel ? for example if you had a separate > >> mongrel already running in dev mode, then the second one would just > >> fail to start (possibly silently seing as you''ve passed -d).--~--~---------~--~----~------------~-------~--~----~ 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@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
I''ve seen an issue before where non-root mysql accounts just don''t work. Even with full GRANT on the database in question. I can''t explain it. But for troubleshooting, try your root account in your production database.yml and retry. Secondly, in the same manner, database migrations sometimes give the same problem AFTER you get your app working. Lastly, you can try to give the production connection the path to your mysql.sock socket file. (find / -name mysql.sock) I''ve seen that cause issues as well. Good luck. H On Oct 2, 10:43 am, Schalk Neethling <volume4.sch...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Hi there everyone, > > On my production server I start the mongrel server as follows: > > mongrel_rails start -e production -a 127.0.0.1 -p 3001 -d > > However when going to the domain I get the following error: > > #42000Unknown database ''satechevents_development'' > > Why is rails looking for the development database in production mode. > > Thanks for the help, > Schalk--~--~---------~--~----~------------~-------~--~----~ 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@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---