couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (Commented) (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1400) Critical crash of Futon after misconfigured bind_address
Date Fri, 03 Feb 2012 21:15:00 GMT


Robert Newson commented on COUCHDB-1400:


You should stop couchdb (and verify that the process is not running), then fix local.ini (restore for bind_address) and then start it up again.

I suggest hopping on our IRC channel #couchdb on or the user@ mailing list.
JIRA is for bug reports, not support.

> Critical crash of Futon after misconfigured bind_address
> --------------------------------------------------------
>                 Key: COUCHDB-1400
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Futon
>    Affects Versions: 0.11.2
>         Environment: CentOS 5.5 (64-bit)
>            Reporter: Tim
>              Labels: Futon,, crash
>         Attachments: screenshot-1.jpg
> I made a mistake to change the configuration table's httpd/bind_address parameter to
my domain, the domain that looks like etc. That was supposed to be left at or I remember making this mistake long time ago but now basically I can't
access anything from either localhost and external. 
> Please check screenshot to see what it looks like when I try to access Futon after misconfiguration.
> I am unable to reverse my setting because working with /etc/couchdb/default.ini or local.ini
never affected this in the first place (spent 2 hours trying to modify these fails in order
to get external access of couchDB). 
> So Futon must have changed something when I set it. When I change the value, it stuck
at the error: Some of the changes require database restart. Since then, I can never access
my couchDB. 
> I tried to yum remove erlang, yum remove couchdb several times. Checked to see if any
default.ini or local.ini remains, restart system, log out users, but none of above works.

> Please help me with this problem as soon as possible. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message