To see what happening: $ couchdb -n -a /tmp/couch.ini -c /tmp/couch.ini
-- ,,,^..^,,, On Sun, Jul 14, 2013 at 1:39 PM, Jan Lehnardt <[email protected]> wrote: > > On Jul 14, 2013, at 11:30 , Jan Lehnardt <[email protected]> wrote: > >> >> On Jul 14, 2013, at 11:23 , Jan Lehnardt <[email protected]> wrote: >> >>> >>> On Jul 14, 2013, at 11:13 , Jan Lehnardt <[email protected]> wrote: >>> >>>> Heya, >>>> >>>> I’m running into an odd issue: >>>> >>>> couchdb -n starts just fine >>>> couchdb -n -a couch.ini (where couch.ini is an empty file) fails: >>>> >>>> Apache CouchDB 1.3.0 (LogLevel=info) is starting. >>>> {"init terminating in >>>> do_boot",{{badmatch,{error,{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,[{file,"couch_server_sup.erl"},{line,98}]},{application_master,start_it_old,4,[{file,"application_master.erl"},{line,274}]}]}}}}}},[{couch,start,0,[{file,"couch.erl"},{line,18}]},{init,start_it,1,[]},{init,start_em,1,[]}]}} >>>> >>>> Why would that be? :) >>> >>> It is because CouchDB expects at least two ini files. Thanks all :) >> >> Hm, no, that’s not it. >> >> Stay tuned for more live debugging. (no seriously, any help would be greatly >> appreciated :) > > it seems like couchdb -n still keeps the system default ini files and couchdb > -n /tmp/couchdb.ini uses only this empty one and CouchDB can’t start without > any ini files (which it should, but doesn’t) > > So, both the description of -n (that it resets *all* ini files, including the > system defaults) is incorrect as well as CouchDB not starting without > default.ini (at least) should be a bug > > Jan > -- > > >> >> >>> >>> >>>> >>>> (note that the ini files you see in the trace are hardcoded on build-time >>>> and are not actually used here.) >>>> >>>> Best >>>> Jan >>>> -- >>>> >>> >> >
