couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Gonzalez (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1253) Resetting config chain not working properly
Date Fri, 19 Aug 2011 11:14:27 GMT


Daniel Gonzalez commented on COUCHDB-1253:

Hi Noah,

I am continuing to report here, since this is a related issue.

This is getting more strange by the minute. I have now trouble running couchdb, even as couchdb
user, whenever I specify an alternate config file:

couchdb@prime:/$ couchdb -n -a /tmp/tmp7oXBs2.paisley.test/test.ini &> /tmp/couchdb.log

Couchdb starts (I am now using default port 5984) but it is crashing as soon as I access
I attach now the couchdb.log, where the crash report can be seen.

The problem does not occur if I use the default configuration files in /usr/local/etc/couchdb,
starting simply with "couchdb".

Just for clarification: the reason I want to start couchdb with an alternate configuration
is that I am doing unit testing of a twisted couchdb client (paisley) which fires up a private
couchdb. That is also the reason why couchdb must run under the normal user, which is doing
the unit testing.

I must say that this unit testing was running fine before, with couchdb being started by the
testing user, and the unit tests running fine. Since in one of my unit tests (view creation)
I was getting "function_clause" errors, and I know those are related to conflicting versions
of couchdb / erlang, I have performed a clean install of the latest versions of erlang / couchdb,
making sure that any system packages are removed before (I am on Ubuntu, so that means removing
package couchdb-bin).

After the reinstall, it is not anymore possible to start couchdb with alternate config files.
Maybe it is a simple error related to permissions (I think I have carefully followed the install
instructions, but who knows). Unfortunately I am unable to understand the crash report.

Even if this is a self-inflicted problem, I would expect that couchdb would not crash that
easily, and that a specific reason of why it has problems fulfilling the request would be
issued, with couchdb happily continuing to run. That would at least reduce the number of bug
reports! :)

Thanks again,

> Resetting config chain not working properly
> -------------------------------------------
>                 Key: COUCHDB-1253
>                 URL:
>             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, 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:


View raw message