couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Lehnardt (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-2488) Respawn no longer works
Date Thu, 04 Dec 2014 12:29:12 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234171#comment-14234171
] 

Jan Lehnardt commented on COUCHDB-2488:
---------------------------------------

Curious! I am fairly sure we didn’t change anything there.

In addition, I think the 1.6.1 behaviour is correct, as you shouldn’t get restarts when
you normally shut down the CouchDB instance.

A better test would be to kill the beam[.smp] process and waiting for a respawn.

What are your respective Erlang versions?

(also, hi & waves from Kotti :)

> Respawn no longer works
> -----------------------
>
>                 Key: COUCHDB-2488
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2488
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: Kristine Jetzke
>
> I noticed that CouchDB does not get restarted anymore if it was killed. Were there any
changes between 1.5 and 1.6?
> Using 1.5.1:
> {code}
> tine$ couchdb -r 5 -b
> Apache CouchDB has started, time to relax.
> tine$ couchdb -k
> Apache CouchDB crashed, restarting in 5 seconds.
> Apache CouchDB has been killed.
> tine$ curl localhost:5984
> {"couchdb":"Welcome","uuid":"9ed01bc924270ea8c58fb659db662eb7","version":"1.5.1","vendor":{"version":"1.6.1-1","name":"Homebrew"}}
> {code}
> Using 1.6.1:
> {code}
> tine$ couchdb -r 5 -b
> Apache CouchDB has started, time to relax.
> tine$ couchdb -k
> Apache CouchDB has been killed.
> tine$ curl localhost:5984
> curl: (7) Failed to connect to localhost port 5984: Connection refused
> {code}
> I'm on Mac OS X Yosemite. I used homebrew to install CouchDB and {{brew switch couchdb
1.5.1}} and {{brew switch couchdb 1.6.1_1}} to test the different versions. However, I initially
noticed the problem on a system with only 1.6.1 installed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message