You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/04/21 07:32:18 UTC
[jira] [Commented] (COUCHDB-2220) "/usr/bin/couchdb -b" doesn't
close stdout / stderr
[ https://issues.apache.org/jira/browse/COUCHDB-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975412#comment-13975412 ]
ASF subversion and git services commented on COUCHDB-2220:
----------------------------------------------------------
Commit e348d4f2da082cee52d11efc6fbc94f1d8a047c9 in couchdb's branch refs/heads/master from [~wohali]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=e348d4f ]
When backgrounding couchdb, close stdout/stderr
COUCHDB-2220
COUCHDB-1669
> "/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
> Assignee: Joan Touzet
> Fix For: 1.7.0
>
>
> "/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)