Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Thu, 3 Apr 2014 11:55:15 +0000 (UTC)
From: "Shish (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12706403.1396526092217.57275.1396526115521@arcas>
In-Reply-To: <JIRA.12706403.1396526092217@arcas>
References: <JIRA.12706403.1396526092217@arcas>
Subject: [jira] [Created] (COUCHDB-2220) "/usr/bin/couchdb -b" doesn't close
 stdout / stderr
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Shish created COUCHDB-2220:
------------------------------

             Summary: "/usr/bin/couchdb -b" doesn't close stdout / stderr
                 Key: COUCHDB-2220
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2220
             Project: CouchDB
          Issue Type: Bug
      Security Level: public (Regular issues)
            Reporter: Shish


"/usr/bin/couchdb -b" launches a copy of itself in the background, but leaves stdout and stderr for the subprocess attached to the controlling terminal in the foreground

This makes salt hang when launching couchdb, because it tries to read the output of "/etc/init.d/couchdb restart" - despite the fact that that init script itself has returned, the children (ie, the daemon) are still holding the console file descriptors open

I *suspect* that this is also the cause of this issue --> https://issues.apache.org/jira/browse/COUCHDB-1669

If you have salt-minion 2014.1.0 installed, try stopping couchdb and then starting it up with:

salt-call cmd.run 'su couchdb -c "/usr/bin/couchdb -b -o /tmp/couchdb.stdout -e /tmp/couchdb.stderr"'

Originally reported as a bug in salt, but it seems that couchdb is the part with the non-standard behaviour https://github.com/saltstack/salt/issues/11228


--
This message was sent by Atlassian JIRA
(v6.2#6252)