couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Narepalepu, Vimal Abhishek" <>
Subject CouchDB 1.6.1 os_process_error,{exit_status,127}
Date Mon, 18 Sep 2017 20:15:10 GMT
Hi ,

I'm new to CouchDB and  have recently installed CouchDB 1.6.1 and CouchDB-lucene 1.1.0 on
CentOS 6.9. Configured the local.ini and the couchdb-lucene .ini accordingly based on the
general installation instructions.
Checked the service of couchdb status as running. Placed  the .couch, design files in /usr/local/var/lib/couchdb
by exporting the files from another server (couch 1.3.0)
Made sure all the relevant file appropriate permissions are set to 'couchdb' for the user
and group

Now running a curl call (as below for example) gives the connection failed error:

Curl -X GET http://username:password@hostname:5984/_fti/local/dbname/_design/lucene/all_fields?q=

Error: {"error":"error","reason":"{conn_failed,{error,econnrefused}}"}

Below are the messages from the log file:



OS Process died with status: 127
** Generic server <0.17431.2721> terminating
** Last message in was {#Port<0.59970138>,{exit_status,127}}
** When Server state == {os_proc,"/usr/local/bin/couchjs /usr/local/share/couchdb/server/main.js",
** Reason for termination ==
** {exit_status,127}


Also have noticed that the couchjs shortcut (pointing to the same at /usr/local/lib/couchdb/bin/)
 at /usr/local/bin contains encrypted characters. Is there a possibility that this file is
Appreciate any help regarding this error . Please let me know if I missed something or any
further details are needed to understand the issue. Looking forward. Thank you for your time


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message