perhaps you're running out of file descriptors or ephemeral ports?
On 25 October 2011 21:20, Ron Dyck <[email protected]> wrote: > I'm working with AWS EC2 instances and have ensured that the proper > ports are open. I'm able to access the server from remote locations > and test using curl successfully. The problem is that it's very > inconsistent. Today, except for earlier in am it's working just fine. > I'm wondering if the issue is latency, and connections are timing out. > Is that a possibility? > > Cheers, > ron > > On Tue, Oct 25, 2011 at 3:29 PM, CGS <[email protected]> wrote: >> Try to remove the firewall and see if it is working. If it still doesn't >> work it may be a problem of permissions (if everything was installed >> correctly) or path. >> >> >> >> >> On 10/25/2011 02:58 PM, Ron Dyck wrote: >>> >>> I've been having intermittent connection problems with my couchdb >>> installation. The error is: "Could not connect to server at >>> <myipaddress>:5984: '111: Connection refused' " >>> >>> I have a remote installation with the binding address set to 0.0.0.0 >>> My installation is on a AWS linux instance: Amazon Linux AMI x86_64 >>> using the https://github.com/iriscouch/build-couchdb install script. >>> >>> The problem is very sporadic, occasionally a reload of the page >>> connects, most other times it does not. I've checked the logs >>> immediately after the connection loss with no evidence of anything. >>> When I test the connection locally: curl 127.0.0.1:5984 I get error >>> connecting. The process is still running when I check ps ax | grep >>> beam. I'm forced to kill the process and start the server. >>> >>> Currently we access the server from 3 different locations and my >>> firewall is set to restrict access to port 5984 from specified IP >>> addresses. >>> >>> Any help is really appreciated. >>> >>> Regards, >>> ron >> >> > > > > -- > ================= > Ron Dyck > [email protected] > www.webbtech.net > ================= >
