similar to: mongrel (0.3.12.4) blows up

Hi I have a rather strange problem with mongrel and I would be grateful if anyone could assist me with resolving. I have an application running mongrel 1.1.1 and rails 1.2.5 with ruby 1.8.6. It was all working fine and starting as expected. But I did a server reboot once and mongrel has refused to start up since. I get the following error:

Howdy, I''m getting an error message when trying to run one of my rails apps, which seems to have started after updating to 10.5.3. mattdaw-2:v1.5_patch mdaw$ mongrel_rails start ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... /usr/local/ruby-patched/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../ lib/mongrel/tcphack.rb:12:in

I assume some of you have run into this error before when trying to run mongrel on port 80 (or another port < 1024) in OSX: $ mongrel_rails start -p 80 ** Starting Mongrel listening at 0.0.0.0:80 /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.14/lib/mongrel/tcphack.rb:12:in `initialize_without_backlog'': Permission denied - bind(2) (Errno::EACCES) from

Hi, I am newbie started learning ruby on rails i had an application which used to run pretty well latter i upgraded from webbrick to mongrel 1.1.5 then I am getting the foloowing errors and a default application runs on port 3000 i have attached its screen shot as an attachement and error which i get in terminal below => Booting Mongrel (use ''script/server webrick'' to force

I''m trying to run mongrel on port 80 and switch to a different user/group from root. As root, this works: mongrel_rails start -p 3000 -u rails --group rails This: mongrel_rails start -p 80 -u rails --group rails dies with: --------------------------- ** Changing group to rails. ** Changing user to rails. ** Starting Mongrel listening at 0.0.0.0:80

I am followint this article, http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ ...but I keep getting this error in the log...not sure what to try next... ** Daemonized, any open files are closed. Look at log/mongrel.8000.pid and log/mongrel.log for info. ** Starting Mongrel listening at 127.0.0.1:8000

Hi, I am newbie started learning ruby on rails i had an application which used to run pretty well latter i upgraded from webbrick to mongrel 1.1.5 then I am getting the foloowing errors and a default application runs on port 3000 by name iphone configuration utility i am unable to attach the screen shot as it is saying file to large. Error which i get in terminal is listed below => Booting

I made a new rails app and when i started the server ,it gave following error message. => Booting Mongrel => Rails 2.3.8 application starting on http://0.0.0.0:3000 => Call with -d to detach => Ctrl-C to shutdown server Exiting /usr/lib/ruby/1.8/mongrel/tcphack.rb:12:in `initialize_without_backlog'': Address already in use - bind(2) (Errno::EADDRINUSE) from

After trying all things in : http://www.ruby-forum.com/topic/105271 I cannot find the pid of the clogger. So, I am still having trouble clearing whatever is active on my localhost port 3000. I can run on a different port "script/server -p 3001" . But my OC would like to have all ports on my machine clean and usable. Below is my error - please help. Thanks! When I try to start the

Hello there, I''ve a big problem -- I come now PC and started rails server and I got this huge report of errors. The rails server is not running, I''ve any idea, what is wrong. Yesterday everything worked yet... The statement after command "rails server" is here: => Booting Mongrel => Rails 3.0.5 application starting in development on http://0.0.0.0:3000 =>

Hi list, I have a problem with Mongrel which is really bugging me. I would really appreciate any help that anyone can provide to help me in solving this problem. 1. My setup: Apache front_end with mod_proxy_balancer in front of 4 mongrel/rails instances of my application. Rails 1.2.5 Ruby 1.8.6 Mongrel 1.1.1 2. I noticed that the CPU consumption on my server was 100% being consumed by ruby so I

Hello, I''ve got an InstantRails 1.7 app (ruby 1.86, rails 2.1.0) that will no longer start since I rebooted my windows server 2003 machine to complete some windows updates. However, I also deleted some gems earlier today, but it started right up perfectly fine. Anyway, here is whats happening: C:\InstantRails\rails_apps\dejavu>ruby script/server => Booting Mongrel (use

[using mongrel-0.3.13.4 pre-release, OX 10.4.7] I have a slightly annoying issue under OS X: If i terminate the session that ran the mongrel process (by closing terminal window -- hey, it happens!), subsequent attempts to start mongrel give me the following error: /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/ tcphack.rb:12:in `initialize_without_backlog'':

Hey y''all: I''ve added some new stuff to mongrel_cluster. Give it try and let me know if it works for you. * Added ''--clean'' to cluster::start to force removal of the pidfile before trying to start the cluster member. This is useful for recovering from unexpected process death. * Added ''--only PORT'' to cluster::* to support running a

background: One of our developers is just getting started with Capistrano, just getting together a rudimentary deploy.rb, copied from one of our contract developers who is just getting started a bit too. I''m the systems manager and a complete Rails and Ruby newbie (who, by the way, cannot thank Zed Shaw enough for mongrel and Bradley Taylor enough for mongrel_cluster :-)

Hi, I have Apache (2.2) setup to proxy requests through to Mongrel (0.3.12.4) for a Rails (1.1.2) application (on ruby 1.8.4). The setup is great, but I''m experiencing some nightly failures. I thought I''d post here before digging in too deeply, but it looks like Rails is going into lala land and Mongrel can''t recover... Seems like everything gets all backed up in

Hi, I''m new to mongrel and so far have liked it a lot during development. I just tried to stand up a production server following the guide here: http://blog.innerewut.de/articles/2006/04/21/scaling-rails-with-apache-2-2-mod_proxy_balancer-and-mongrel This was working well for a few days, until this weekend it crashed with the following stack trace. It''s running on redhat

I try to config XLSUITE in my system. I''m facing some problem i resolved it one by one. now im facing this error => Booting Mongrel (use ''script/server webrick'' to force WEBrick) => Rails 2.2.0 application starting on http://0.0.0.0:3000 => Call with -d to detach => Ctrl-C to shutdown server ** Starting Mongrel listening at 0.0.0.0:3000 Exiting

Hello, maybe someone can help with backgroundrb. I''ve written an application, which makes use of backgroundrb. Everything works fine on my development machine, but it crashes on my production server. Something seems to be wrong with backgroundrb, but I don''t know the cause. All I get is the error message attached below, which is extracted from the production.log. I

Hi, After following the excellent tutorials in the Agile Web Development with Rails book, I was able to get my webservice working pretty much perfectly :) I can access it via SOAP and XML-RPC and look at service.wsdl to find the API. What I can''t do however is get the API for the XML-RPC call. It fails with : Internal protocol error: NilClass is not a valid input stream. It must