[
https://issues.apache.org/jira/browse/COUCHDB-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Chesneau updated COUCHDB-1369:
-------------------------------------
Attachment: 0001-fix-COUCHDB-1369.patch
Attached patch should fix the issue which is due to the fact httpd is restarted
on any ssl change. The inverse issue.
This patch depending on the name of the service we start should register the
event depending on the service name.
> https config change
> -------------------
>
> Key: COUCHDB-1369
> URL: https://issues.apache.org/jira/browse/COUCHDB-1369
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Affects Versions: 1.1.1, 1.2, 1.3
> Reporter: Benoit Chesneau
> Priority: Blocker
> Attachments: 0001-fix-COUCHDB-1369.patch, https_config_change.patch
>
>
> Changing configuration of the ssl port make the server crashing.
> COnfiguration isn't saved and https isn't available anymore.
> Step to reproduce:
> 1. Enable ssl by uncommenting httpsd daemon line in local.ini and set
> key_file & cert_file in ssl section
> 2. start couchdb
> 3. Change port using the `_config` interface:
> curl -XPUT 'http://127.0.0.1:5984/_config/ssl/port' -d'"6987"'
> "6986"
> log:
> [error] [<0.95.0>] {error_report,<0.30.0>,
> {<0.95.0>,supervisor_report,
> [{supervisor,{local,couch_secondary_services}},
> {errorContext,child_terminated},
> {reason,normal},
> {offender,
> [{pid,<0.172.0>},
> {name,httpd},
> {mfargs,{couch_httpd,start_link,[]}},
> {restart_type,permanent},
> {shutdown,brutal_kill},
> {child_type,worker}]}]}}
> =SUPERVISOR REPORT==== 24-Dec-2011::11:54:36 ===
> Supervisor: {local,couch_secondary_services}
> Context: child_terminated
> Reason: normal
> Offender: [{pid,<0.172.0>},
> {name,httpd},
> {mfargs,{couch_httpd,start_link,[]}},
> {restart_type,permanent},
> {shutdown,brutal_kill},
> {child_type,worker}]
> The server restart but change isn't took in consideration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
