You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Nestor Urquiza (JIRA)" <ji...@apache.org> on 2012/12/12 21:53:22 UTC
[jira] [Commented] (COUCHDB-1627) couchdb fails to start when run
remotely (from an interactive shell)
[ https://issues.apache.org/jira/browse/COUCHDB-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530317#comment-13530317 ]
Nestor Urquiza commented on COUCHDB-1627:
-----------------------------------------
For more information about the whole previous discussion on the subject look at http://mail-archives.apache.org/mod_mbox/incubator-couchdb-user/201212.mbox/browser
> couchdb fails to start when run remotely (from an interactive shell)
> ---------------------------------------------------------------------
>
> Key: COUCHDB-1627
> URL: https://issues.apache.org/jira/browse/COUCHDB-1627
> Project: CouchDB
> Issue Type: Bug
> Reporter: Nestor Urquiza
>
> 1. Be sure couchdb is not running in a remote machine
> 2. Issue the below command to the remote machine:
> $ ssh -t remoteserver sudo /etc/init.d/couchdb start
> 3. You will see how the daemon is not started
> Now update the script as shown below (using nohup) and repeat 1-2 from above to confirm the daemon is indeed started:
> run_command () {
> command="$1"
> if test -n "$COUCHDB_OPTIONS"; then
> command="$command $COUCHDB_OPTIONS"
> fi
> if test -n "$COUCHDB_USER"; then
> if nohup su $COUCHDB_USER -c "$command"; then
> return $SCRIPT_OK
> else
> return $SCRIPT_ERROR
> fi
> else
> if $command; then
> return $SCRIPT_OK
> else
> return $SCRIPT_ERROR
> fi
> fi
> }
> I am not recommending to use nohup but to come up with a solution that allows to remotely start couchdb the same way it is started from a logged in session.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira