Hoo~~Ray!!!
The problem has been solved!
could someone tell me why I have to write ferret_server.yml like this:
..... production:
host: 127.0.0.1
....
neither
..
production:
host: localhost
..
nor
...
production:
host: [the IP of my instance]
... why?

It seems that I have make a stupid mistake...and this mistake takes me
about 10 days to find the answer...
During finding how to solve the problem,I learned something about the
port of amazon computing service,see here:
https://cloud-support.engineyard.com/discussions/problems/44-firewalled-ports
Before setting the host to 127.0.0.1,I tried this method,but it
doesn't work...may be this will be useful for somebody,so I put the
link above.


On Aug 31, 10:51 pm, Hassan Schroeder <[email protected]>
wrote:
> 2009/8/30 刘子嘉 <[email protected]>:
>
> > ferret_server.log,it shows "Cannot assign request address - bind(2)".
>
> So either you're trying to use a privileged port as a non-privileged
> user, or that port's already being used by some other process.
>
> If you have sudo rights, you can try starting ferret_server as root;
> if that fails, the problem is the second one -- find a different port to
> run on and configure appropriately.
>
> --
> Hassan Schroeder ------------------------ [email protected]
> twitter: @hassan
--~--~---------~--~----~------------~-------~--~----~
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