-
DescriptionProduction instance suddenly failed (no recent software updates). Curl/Telnet to 127.0.01:5984 now results in "CouchDB 2.3.1 Connection Refused". Have tried restarting the couchdb service, rebooting the server (x-large on AWS). I don't see any issues in the logs other than a seemingly one-time reduce error. Steps to Reproduce
Have also tried with curl and other ports (5986, 6984). I have also tried changing the bind_address from 127.0.0.1 to 0.0.0.0 but that had no apparent effect. I have an identical production server (that replicates with this one) that is still running fine. Expected BehaviourCouchDB should accepted incoming connections and Fauxton should be available. Your EnvironmentCouchDB 2.3.1 Additional ContextLog of the initial crash and my subsequent attempts to reboot
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Your log shows:
That |
Beta Was this translation helpful? Give feedback.
-
Thank you so much!!! I increased the AWS Volume Size and now I can connect again. |
Beta Was this translation helpful? Give feedback.
Your log shows:
That
error,enospc
means your disk is out of space.