[
https://issues.apache.org/jira/browse/COUCHDB-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563993#comment-13563993
]
Pierre Voisin commented on COUCHDB-1655:
----------------------------------------
Note: /_users/_design/_auth does exist and seem to be valid when I evaluate it.
Anyway, I made no change to any database befire trying to add that user so
everything should be original to the installation.
> CentOS + CouchDB 1.2.1 - Adding documents to _users fails with a "OS Process
> Error" error
> -----------------------------------------------------------------------------------------
>
> Key: COUCHDB-1655
> URL: https://issues.apache.org/jira/browse/COUCHDB-1655
> Project: CouchDB
> Issue Type: Bug
> Reporter: Pierre Voisin
> Attachments: trace.txt
>
>
> I've installed CouchDB 1.2.1 on my CentOS 6.2, initially following this guide
> [http://www.thegeekstuff.com/2012/06/install-couch-db/] but then relying on
> packages bundled with CentOS (except for CouchDB itself that I want to be
> 1.2.1) and it seemed to be working nicely until I tried to create a user.
> Basically, I'm getting a "OS Process Error" exception with that trace that
> I'm attaching to the issue right after:
> [Mon, 28 Jan 2013 02:06:03 GMT] [error] [<0.331.0>] OS Process Error
> <0.359.0> :: {os_process_error,
> {exit_status,134}}
> [Mon, 28 Jan 2013 02:06:03 GMT] [error] [<0.331.0>] ** Generic server
> couch_query_servers terminating
> ** Last message in was {get_proc,{doc,<<"_design/_auth">>,
> ...yadayadayada...
> {<<"_design/_auth">>,
>
> <<"1-a8cfb993654bcc635f126724d39eb930">>}},
> infinity]}}
> [Mon, 28 Jan 2013 02:06:03 GMT] [info] [<0.304.0>] 70.30.198.177 - - PUT
> /_users/org.couchdb.user:pvoisin 500
> I'm a bit scared about reading such a trace and I'm absolutely not at ease
> enough to decrypt that message.
> The thing is I can add users successfully with the CentOS couchdb package
> (which is a 1.0.3).
--
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
