Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6348311
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T21:23:40+00:00 2026-05-24T21:23:40+00:00

I have couchdb 1.1.0 installed, and it is running fine, when starting using the

  • 0

I have couchdb 1.1.0 installed, and it is running fine, when starting using the normal config files. That is, starting as:

couchdb

will allow me to do the usual:

curl -X GET http://127.0.0.1:5984/
{"couchdb":"Welcome","version":"1.1.0"}

Now, I need to start couchdb with an alternate config directory. For that, I fire couchdb with the following command:

couchdb -n -a test.ini

The start up is successful, and couchdb is listening to http://127.0.0.1:5984

However, as soon as I do a GET operation, couchdb crashes:

[error] [<0.196.0>] {error_report,<0.31.0>,
                     {<0.196.0>,crash_report,
                      [[{initial_call,
                         {mochiweb_acceptor,init,
                          ['Argument__1','Argument__2','Argument__3']}},
                        {pid,<0.196.0>},
                        {registered_name,[]},
                        {error_info,
                         {exit,
                          {noproc,
                           {gen_server,call,
                            [couch_httpd_vhost,
                             {match_vhost,
                              {mochiweb_request,#Port<0.2102>,'GET',"/",
                               {1,1},
                               {3,
                                {"user-agent",
                                 {'User-Agent',
                                  "curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15"},
                                 {"host",
                                  {'Host',"127.0.0.1:5984"},
                                  {"accept",{'Accept',"*/*"},nil,nil},
                                  nil},
                                 nil}}}}]}},
                          [{gen_server,call,2},
                           {couch_httpd_vhost,match_vhost,1},
                           {couch_httpd,handle_request,5},
                           {mochiweb_http,headers,5},
                           {proc_lib,init_p_do_apply,3}]}},
                        {ancestors,
                         [couch_httpd,couch_secondary_services,
                          couch_server_sup,<0.32.0>]},
                        {messages,[]},
                        {links,[<0.103.0>,#Port<0.2102>]},
                        {dictionary,[]},
                        {trap_exit,false},
                        {status,running},
                        {heap_size,610},
                        {stack_size,24},
                        {reductions,672}],
                       []]}}
=CRASH REPORT==== 19-Aug-2011::17:03:44 ===
  crasher:
    initial call: mochiweb_acceptor:init/3
    pid: <0.196.0>
    registered_name: []
    exception exit: {noproc,
                     {gen_server,call,
                      [couch_httpd_vhost,
                       {match_vhost,
                        {mochiweb_request,#Port<0.2102>,'GET',"/",
                         {1,1},
                         {3,
                          {"user-agent",
                           {'User-Agent',
                            "curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15"},
                           {"host",
                            {'Host',"127.0.0.1:5984"},
                            {"accept",{'Accept',"*/*"},nil,nil},
                            nil},
                           nil}}}}]}}
      in function  gen_server:call/2
      in call from couch_httpd_vhost:match_vhost/1
      in call from couch_httpd:handle_request/5
      in call from mochiweb_http:headers/5
    ancestors: [couch_httpd,couch_secondary_services,couch_server_sup,
                  <0.32.0>]
    messages: []
    links: [<0.103.0>,#Port<0.2102>]
    dictionary: []
    trap_exit: false
    status: running
    heap_size: 610
    stack_size: 24
    reductions: 672
  neighbours:

Any idea what could be going on?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-24T21:23:41+00:00Added an answer on May 24, 2026 at 9:23 pm

    Well, I think I found the problem, so I will answer my own question, for reference.

    My configuration file (test.ini) was lacking (compared to the stock default.ini) the following options in the [daemon] section:

    replication_manager={couch_replication_manager, start_link, []}
    vhosts={couch_httpd_vhost, start_link, []}
    os_daemons={couch_os_daemons, start_link, []}
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I've installed CouchDB on my vagrant 0.9.0 box that is running CentOS 6.2 .
I have a normal Rails project (without Active Record) using CouchDB (couchrest_model) as a
I have a production server running an app that uses CouchDB as its main
I have a CouchDB server that is running behind a front end proxy which
CouchDB, version 0.10.0, using native erlang views. I have a simple document of the
My company is using CouchDB, and I'm going to have to interact with it
Using CouchDB , I currently have a document which represents an idea, you can
Given that I have some number of documents in my CouchDB database, I would
Using CouchDB to create a hosted app for clients. I have a dev database
I am running nginx 0.6.32 as a proxy front-end for couchdb. I have my

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.