Tim Booher wrote:
> 
> Here is my mongrel_cluster.yml
> -------------------------------
> ---
> cwd: /var/www/apps/MyApplication
> log_file: log/mongrel.log
> port: "8000"
> environment: production
> address: 127.0.0.1
> pid_file: tmp/pids/mongrel.pid
> servers: 2
> 
> Now I type:
>> mongrel_rails cluster::restart
> already stopped port 8000
> already stopped port 8001
> starting port 8000
> starting port 8001
> 
> And then:
> curl -I http://127.0.0.1:8000/
> curl: (7) couldn't connect to host
> 
> No mongrel!
> 
> further:
> nmap 127.0.0.1
> 
> Starting Nmap 4.53 ( http://insecure.org ) at 2008-03-19 01:08 EDT
> Interesting ports on localhost (127.0.0.1):
> Not shown: 1706 closed ports
> PORT     STATE SERVICE
> 22/tcp   open  ssh
> 80/tcp   open  http
> 139/tcp  open  netbios-ssn
> 445/tcp  open  microsoft-ds
> 631/tcp  open  ipp
> 3000/tcp open  ppp
> 3001/tcp open  nessusd
> 3306/tcp open  mysql
> 
> no mongrel!
> 
> also, when i try to see my site (after deploying via capistrano):
> [Wed Mar 19 01:09:04 2008] [error] (111)Connection refused: proxy: HTTP:
> attempt to connect to 127.0.0.1:8001 (127.0.0.1) failed
> [Wed Mar 19 01:09:04 2008] [error] ap_proxy_connect_backend disabling
> worker for (127.0.0.1)
> [Wed Mar 19 01:09:04 2008] [error] (111)Connection refused: proxy: HTTP:
> attempt to connect to 127.0.0.1:8000 (127.0.0.1) failed
> [Wed Mar 19 01:09:04 2008] [error] ap_proxy_connect_backend disabling
> worker for (127.0.0.1)
> 
> This has been many hours of frustration -- any help _greatly_
> appreciated.
> 
> best,
> 
> tim

I am experiencing the same problem as I switch my production server from 
one colo to another. Needless to say, this all works fine on the current 
machine. But the new machine has this problem.

Here is what I know: if I run webrick or mongrel on (say) port 3000,
-I cannot hit that from the local machine (via curl, wget)
-lsof (when run as sudo) shows the listener;
-On my 'working' machine I can use curl to get localhost:3000 just fine.

So, needless to say, Apache cannot hit the mongrel ports either.

I think that the problem isnt mongrel or webrick, it is something in the 
OS configuration.

N.B. selinux is off for this machine.
The old machine is RHEL4 the new is CentOS 4.5 (at gogrid)

Hers output from lsof:
mongrel_r 7729 mike    3u  IPv4 118549       TCP gogrid-centos4:9000 
(LISTEN)
Any idea what the gogrid-centos4 column is for (it is also * for other 
processes).

Any ideas on what to try or fix here?

Mike
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to