[
https://issues.apache.org/jira/browse/COUCHDB-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087629#comment-13087629
]
Noah Slater commented on COUCHDB-1253:
--------------------------------------
The original permissions on that directory were correct, so I would leave them
that way. If you specify your own config chain, the script should not try to
read from the default location. The output you attached looks okay. If you
cannot reproduce the bug, I will close the ticket. There's nothing like a
problem that fixes itself when you threaten to debug it.
> Resetting config chain not working properly
> -------------------------------------------
>
> Key: COUCHDB-1253
> URL: https://issues.apache.org/jira/browse/COUCHDB-1253
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Affects Versions: 1.1
> Environment: Linux 2.6.32-33-generic #70-Ubuntu SMP Thu Jul 7
> 21:09:46 UTC 2011 i686 GNU/Linux
> Ubuntu 10.04.3 LTS
> Reporter: Daniel Gonzalez
> Priority: Minor
> Attachments: couchdb.log
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Resetting the config chain seems to be working:
> couchdb -n -a /tmp/tmpuPqqSF.paisley.test/test.ini -c
> /tmp/tmpuPqqSF.paisley.test/test.ini
> But it does actually not work:
> couchdb -n -a /tmp/tmpuPqqSF.paisley.test/test.ini
> ...
> =INFO REPORT==== 18-Aug-2011::15:21:32 ===
> application: couch
> exited: {bad_return,{{couch_app,start,
> [normal,
> ["/usr/local/etc/couchdb/default.ini",
> "/usr/local/etc/couchdb/local.ini"]]},
> {'EXIT',{{badmatch,{error,shutdown}},
> [{couch_server_sup,start_server,1},
> {application_master,start_it_old,4}]}}}}
> type: temporary
> ...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
