couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Woelfel (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (COUCHDB-1669) Unable to start CouchDB in background through a psuedo-tty
Date Tue, 05 Feb 2013 23:15:13 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Woelfel updated COUCHDB-1669:
------------------------------------

    Description: 
CouchDB crashes when started as a background process in a psuedo-tty.

Steps to reproduce:

On a machine that you can ssh into localhost do:

ssh -tt localhost "/path/to/couchdb -b"

When the connection closes, CouchDB will be killed.

A few things I've discovered while debugging

When I do

ssh -tt localhost "~/build-couchdb/build/bin/couchdb -b && sleep 10 && curl
localhost:5984"

The output from the command is:

Apache CouchDB has started, time to relax.
{"couchdb":"Welcome","version":"1.2.1"}
Connection to localhost closed.

The contents or couchdb's stdout file is 

Apache CouchDB 1.2.1 (LogLevel=info) is starting.
Apache CouchDB has started. Time to relax.
[info] [<0.32.0>] Apache CouchDB has started on http://127.0.0.1:5984/
[info] [<0.131.0>] 127.0.0.1 - - GET / 200

The contents of couchdb's stderr is

heart_beat_kill_pid = 32631
heart_beat_timeout = 11
heart: Mon Feb  4 07:31:57 2013: Erlang has closed.
heart: Mon Feb  4 07:31:58 2013: Executed "/home/ubuntu/build-couchdb/build/bin/couchdb -k"
-> 0. Terminating.

This happens no matter how I start CouchDB: as a service, with the init script, with nohup,
or with the command above. I built CouchDB using the build instructions for Ubuntu 12.04 from
the wiki and using the build-couchdb project on Github.

The really odd thing is that this only happens when I start couchdb with `ssh -tt`. If I ssh
into localhost and start couchdb in the background, it will continue running after I exit
the ssh session.

  was:
CouchDB crashes when started as a background process in a psuedo_tty.

Steps to reproduce:

On a machine that you can ssh into localhost do:

ssh -tt localhost "/path/to/couchdb -b"

When the connection closes, CouchDB will be killed.

A few things I've discovered while debugging

When I do

ssh -tt localhost "~/build-couchdb/build/bin/couchdb -b && sleep 10 && curl
localhost:5984"

The output from the command is:

Apache CouchDB has started, time to relax.
{"couchdb":"Welcome","version":"1.2.1"}
Connection to localhost closed.

The contents or couchdb's stdout file is 

Apache CouchDB 1.2.1 (LogLevel=info) is starting.
Apache CouchDB has started. Time to relax.
[info] [<0.32.0>] Apache CouchDB has started on http://127.0.0.1:5984/
[info] [<0.131.0>] 127.0.0.1 - - GET / 200

The contents of couchdb's stderr is

heart_beat_kill_pid = 32631
heart_beat_timeout = 11
heart: Mon Feb  4 07:31:57 2013: Erlang has closed.
heart: Mon Feb  4 07:31:58 2013: Executed "/home/ubuntu/build-couchdb/build/bin/couchdb -k"
-> 0. Terminating.

This happens no matter how I start CouchDB: as a service, with the init script, with nohup,
or with the command above. I built CouchDB using the build instructions for Ubuntu 12.04 from
the wiki and using the build-couchdb project on Github.

The really odd thing is that this only happens when I start couchdb with `ssh -tt`. If I ssh
into localhost and start couchdb in the background, it will continue running after I exit
the ssh session.

    
> Unable to start CouchDB in background through a psuedo-tty 
> -----------------------------------------------------------
>
>                 Key: COUCHDB-1669
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1669
>             Project: CouchDB
>          Issue Type: Bug
>            Reporter: Daniel Woelfel
>
> CouchDB crashes when started as a background process in a psuedo-tty.
> Steps to reproduce:
> On a machine that you can ssh into localhost do:
> ssh -tt localhost "/path/to/couchdb -b"
> When the connection closes, CouchDB will be killed.
> A few things I've discovered while debugging
> When I do
> ssh -tt localhost "~/build-couchdb/build/bin/couchdb -b && sleep 10 &&
curl localhost:5984"
> The output from the command is:
> Apache CouchDB has started, time to relax.
> {"couchdb":"Welcome","version":"1.2.1"}
> Connection to localhost closed.
> The contents or couchdb's stdout file is 
> Apache CouchDB 1.2.1 (LogLevel=info) is starting.
> Apache CouchDB has started. Time to relax.
> [info] [<0.32.0>] Apache CouchDB has started on http://127.0.0.1:5984/
> [info] [<0.131.0>] 127.0.0.1 - - GET / 200
> The contents of couchdb's stderr is
> heart_beat_kill_pid = 32631
> heart_beat_timeout = 11
> heart: Mon Feb  4 07:31:57 2013: Erlang has closed.
> heart: Mon Feb  4 07:31:58 2013: Executed "/home/ubuntu/build-couchdb/build/bin/couchdb
-k" -> 0. Terminating.
> This happens no matter how I start CouchDB: as a service, with the init script, with
nohup, or with the command above. I built CouchDB using the build instructions for Ubuntu
12.04 from the wiki and using the build-couchdb project on Github.
> The really odd thing is that this only happens when I start couchdb with `ssh -tt`. If
I ssh into localhost and start couchdb in the background, it will continue running after I
exit the ssh 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

Mime
View raw message