[
https://issues.apache.org/jira/browse/COUCHDB-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim updated COUCHDB-1400:
-------------------------
Description:
Bug1: Unable to reflect bind_address in local.ini
Bug2: Unable to revert changes doing clean install
Bug3: Can only change bind_address in Futon
I made a mistake to change the configuration table's httpd/bind_address
parameter to my domain, the domain that looks like www.google.com etc. That was
supposed to be left at 0.0.0.0 or 127.0.0.1. 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.
was:
I made a mistake to change the configuration table's httpd/bind_address
parameter to my domain, the domain that looks like www.google.com etc. That was
supposed to be left at 0.0.0.0 or 127.0.0.1. 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.
> Critical crash of Futon after misconfigured bind_address
> --------------------------------------------------------
>
> Key: COUCHDB-1400
> URL: https://issues.apache.org/jira/browse/COUCHDB-1400
> 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
>
>
> Bug1: Unable to reflect bind_address in local.ini
> Bug2: Unable to revert changes doing clean install
> Bug3: Can only change bind_address in Futon
> I made a mistake to change the configuration table's httpd/bind_address
> parameter to my domain, the domain that looks like www.google.com etc. That
> was supposed to be left at 0.0.0.0 or 127.0.0.1. 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
