Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 20676933C for ; Fri, 3 Feb 2012 21:47:22 +0000 (UTC) Received: (qmail 8287 invoked by uid 500); 3 Feb 2012 21:47:21 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 8191 invoked by uid 500); 3 Feb 2012 21:47:20 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 7862 invoked by uid 99); 3 Feb 2012 21:47:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2012 21:47:20 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2012 21:47:17 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id A566318C086 for ; Fri, 3 Feb 2012 21:46:55 +0000 (UTC) Date: Fri, 3 Feb 2012 21:46:55 +0000 (UTC) From: "Tim (Updated) (JIRA)" To: dev@couchdb.apache.org Message-ID: <1192202433.9197.1328305615678.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <285413429.8934.1328301593562.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (COUCHDB-1400) Critical crash of Futon after misconfigured bind_address MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ 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