similar to: Weird Mongrel error: Not starting.

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

Whenever I tried to start mongrel_rails with the upload progress script, it would die with the following error: /usr/local/lib/ruby/1.8/drb/drb.rb:837:in `getaddrinfo'': getaddrinfo: No address associated with nodename (SocketError) from /usr/local/lib/ruby/1.8/drb/drb.rb:837:in `open_server_inaddr_any'' from /usr/local/lib/ruby/1.8/drb/drb.rb:860:in

Hi, I can''t get breakpointer to work on locomotive. Pretty sure it used to work... Any ideas?? Jeroen jeroen$ ruby script/breakpointer /Applications/Locomotive/Bundles/rails-1.0.0-max.bundle/Contents/Resources/ports/lib/ruby/1.8/drb/drb.rb:828:in `getaddrinfo'': getaddrinfo: No address associated with nodename (SocketError) from

Hi, all- I started playing with RSpec in a new Rails app. I''ve installed the plugin and bootstrapped it, and run ''script/rails_spec_runner'' (not rails_spec_server as the website currently reads, btw) in a separate shell, then in another shell I run ''script/rails_spec'' and get the following: /usr/local/lib/ruby/1.8/drb/drb.rb:837:in

Hi, I''m rather new to backgrounDRb and DRb itself. I tried to run backgrounDRb on my shared hosting site at Railsplayground.com using rake backgroundrb:start and got this error: /usr/local/lib/ruby/1.8/drb/drb.rb:862:in `initialize'': getaddrinfo: Name or service not known (SocketError) from /usr/local/lib/ruby/1.8/drb/drb.rb:862:in `open_server'' from

I''m not sure what has changed that could have caused this, but lately, I''m unable to run the script/breakpointer script with my application. The application is just loaded up as webrick like: => Booting WEBrick... => Rails application started on http://0.0.0.0:3000 => Ctrl-C to shutdown server; call with --help for options [2006-03-20 12:42:48] INFO WEBrick 1.3.1

Hello, I am in the middle of my first ROR project and suddently the breakpointer script (./script/breakpointer) does allways return the error listed below. All time before it was working without problems - but the funny think, I did not change anything on the system (despite downloading the Suse Security Patches). I am running: Suse 9.3 Rails 1.00 Ruby 1.8.3 Please help, if you have any

Hey there, I got a new workstation going on here an Intel iMac, and I''ve compiled and installed everything with intel binaries. Everything works fine, I even got that cool clever lighttpd script running (http://www.bigbold.com/snippets/posts/show/303). But the one thing that doesn''t work is breakpoints and the breakpointer script. When I run script/breakpointer, I get the

I''ve run into a problem on one of my development machines. I''m trying to run multiple rails apps on one dev machine that runs Windows. Problem is that is seems that I can only run one scgi_service at a time, meaning that only one of my apps will function at a time. Anyone know how I can get around this, other than getting a *nix box (which I should have soon, hopefully) ?

I''m deploying new rails applications. Everything works well except when it comes to the db migration: * executing "cd /var/rails/benefits_test/releases/20101129190121 && /opt/ruby-enterprise-1.8.7-2010.02/bin/rake RAILS_ENV=production db:util:migrate" servers: ["ps-test-app1"] [ps-test-app1] executing command ** [out :: ps-test-app1] (in

I am using Rails 2.2.2 and try to do a DB migration, but got the following error. I am using Centos 5.4. Can someone give me a clue? >> rake db:migrate RAILS_ENV="production" rake aborted! getaddrinfo: Name or service not known (See full trace by running task with --trace) [current]$ rake db:migrate RAILS_ENV="production" --trace ** Invoke db:migrate (first_time) **

I''m deploying new rails applications. Everything works well except when it comes to the db migration: * executing "cd /var/rails/benefits_test/releases/20101129190121 && /opt/ruby-enterprise-1.8.7-2010.02/bin/rake RAILS_ENV=production db:util:migrate" servers: ["ps-test-app1"] [ps-test-app1] executing command ** [out :: ps-test-app1] (in

I''m playing with the mongrel clustering, and am having a problem getting 2 mongrels to start up reliably. This should be a pretty simple cluster, with just 2 instances running. My mongrel config (mongrel_cluster.yml) looks like: cwd: /deployment/installed/myapp/current log_file: log/mongrel.log port: "8000" environment: production address: 127.0.0.1 pid_file:

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

Hello, I don''t know if this is really relevant anymore because a new version is about to be released it seems, however I''ve been trying to run mongrel 0.3.12.4 on a development server in development mode (simply with mongrel_rails start). I try to access the server and the first page (static file) loads, but then the server dies and I get this in the logs. I''m

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

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

hi, how to configure mongrel_cluster in windows. mongrel_rails cluster::configure -e development -p 3000 -N 2 i have used this one its configured correctly then if i start the server it is throwing error.if any one knows how to configure help me with regards shiva -- Posted via http://www.ruby-forum.com/.

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