I wanted to show a Rails site to someone so I set up Mongrel and it ran fine, This is my mongrel_cluster.yml, port: ?80" environment: production pid_file: log/mongrel.pid servers: 4 Now, after going back to Apache/Tomcat I can''t get the Mongrel site up and running again...? Any suggestions? (When I run Mongrel, I stop Apache first) Jim
> I wanted to show a Rails site to someone so I set up Mongrel and it ran fine, > > This is my mongrel_cluster.yml, > > port: ?80" > environment: production > pid_file: log/mongrel.pid > servers: 4 > > Now, after going back to Apache/Tomcat I can''t get the Mongrel site up and > running again...? > > Any suggestions? > > (When I run Mongrel, I stop Apache first)How long do you wait after stopping apache before staring mongrel? I know some OS''s won''t let you connect/bind to the same port if it''s just been released... and some OS''s have an option to override that behavior... what happens if you change your port to 81 or something other than 80?
>From: Philip Hallstrom <mongrel at philip.pjkh.com> >Reply-To: mongrel-users at rubyforge.org >To: mongrel-users at rubyforge.org >Subject: Re: [Mongrel] Mongrel browse problem >Date: Tue, 29 Aug 2006 17:39:25 -0500 (CDT) > >>I wanted to show a Rails site to someone so I set up Mongrel and it ran >>fine, >> >>This is my mongrel_cluster.yml, >> >>port: ?80" >>environment: production >>pid_file: log/mongrel.pid >>servers: 4 >> >>Now, after going back to Apache/Tomcat I can''t get the Mongrel site up and >>running again...? >> >>Any suggestions? >> >>(When I run Mongrel, I stop Apache first) > >How long do you wait after stopping apache before staring mongrel? I know >some OS''s won''t let you connect/bind to the same port if it''s just been >released... and some OS''s have an option to override that behavior... what >happens if you change your port to 81 or something other than 80?>_______________________________________________ >Mongrel-users mailing list >Mongrel-users at rubyforge.org >http://rubyforge.org/mailman/listinfo/mongrel-usersI was trying to connect on the wrong port...my bad. It should be www.mysite.com:3000 Do you know how I can make it so a user can browse http://www.mysite.com/railsemo w/o the 3000? I know I can just start mongrel on port 80 and not use Apache, but I need my Tomcat/Apache sites up also. Thanks, Jim
>>> I wanted to show a Rails site to someone so I set up Mongrel and it ran >>> fine, >>> >>> This is my mongrel_cluster.yml, >>> >>> port: ?80" >>> environment: production >>> pid_file: log/mongrel.pid >>> servers: 4 >>> >>> Now, after going back to Apache/Tomcat I can''t get the Mongrel site up and >>> running again...? >>> >>> Any suggestions? >>> >>> (When I run Mongrel, I stop Apache first) >> >> How long do you wait after stopping apache before staring mongrel? I know >> some OS''s won''t let you connect/bind to the same port if it''s just been >> released... and some OS''s have an option to override that behavior... what >> happens if you change your port to 81 or something other than 80? > > I was trying to connect on the wrong port...my bad. It should be > www.mysite.com:3000 > > Do you know how I can make it so a user can browse > http://www.mysite.com/railsemo w/o the 3000? > > I know I can just start mongrel on port 80 and not use Apache, but I need my > Tomcat/Apache sites up also.I don''t personally, but Zed always mentions the latest pre-release and the --prefix option and something else... search the lists... I''m sure you''ll find it... -philip
On 8/29/06, Jim Douglas <jdz99 at hotmail.com> wrote:> I was trying to connect on the wrong port...my bad. It should be > www.mysite.com:3000 > > Do you know how I can make it so a user can browse > http://www.mysite.com/railsemo w/o the 3000? > > I know I can just start mongrel on port 80 and not use Apache, but I need my > Tomcat/Apache sites up also.Proxying, virtual hosts, and a lot more are covered here. http://tinyurl.com/hdwf4 http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ -- James