I think the help text is correct (and it's exactly what thin says for the equivalent option)
It seems to me the problem is in the error message we and thin produce: 'no acceptor' seems to be the standard error message when _anything_ with binding to the IP address goes wrong - you get this also if you start the server twice. It would be great if we could get something clearer like 'cannot bind to port $host:$port' for those cases. David On Mon, 2012-05-07 at 10:39 +1000, Koper, Dies wrote: > Hi all, > > Stefan found me on irc and we resolved the issue: > > The -r is to specify the local nic's ip address the DeltaCloud server will be > running on, not the public ip address of the cloud provider or the VM > instance you want to work with. > > -r, --hostname HOSTNAME Bind to HOST address (default: localhost) > > Can we improve the description? > Something like: > > -r, --hostname HOSTNAME Run Deltacloud server on network card > with HOST address (default: localhost) > > Regards, > Dies Koper > > > -----Original Message----- > > From: stefan düsing [mailto:[email protected]] > > Sent: Saturday, 5 May 2012 12:30 PM > > To: [email protected] > > Subject: deltacloud-server with ec2 > > > > Hello, > > > > I hope you can help me :-) > > > > i'm running the deltacloud-server on localhost. With this one i want to > > connect to a ec2 server. > > So i run deltacloudd -i ec2 -r ip -p3001 > > But i get a RuntimeError > > eventmachine.rb:572: in 'start_tcp_server': no acceptor (RuntimeError) > > > > Do i have to install the seltacloud-server on every ec2 server? Or must > > i install sth on my ec2 server? > > > > I hope you can give me an answer soon. > > > > Best regards > > > > Stefan Duesing > >
