Yes, eaccess is about permission issues. Worth to check them twice or better reset to those that should be (not sure what and where on OSX however). If this doesn't help, try to use strace to find what exact files/directories causes access error. -- ,,,^..^,,,
On Tue, Aug 11, 2015 at 6:11 AM, Tito Ciuro <[email protected]> wrote: > Hello, > > I’m seeing the following error in the couchdb log: > >> {"init terminating in >> do_boot",{{badmatch,{error,{bad_return,{{couch_app,start,[normal,["/SourceCache/XCSCouchDB/XCSCouchDB-2/build/etc/couchdb/default.ini","/SourceCache/XCSCouchDB/XCSCouchDB-2/build/etc/couchdb/local.ini"]]},{'EXIT',{{badmatch,{error,{shutdown,{failed_to_start_child,couch_secondary_services,{shutdown,{failed_to_start_child,auth_cache,{{{case_clause,{{badmatch,{error,eacces}},[{couch_file,init,1,[{file,"/SourceCache/XCSCouchDB/XCSCouchDB-2/dependencies/couchdb/src/couchdb/couch_file.erl"},{line,314}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,304}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,239}]}]}},[{couch_server,handle_info,2,[{file,"/SourceCache/XCSCouchDB/XCSCouchDB-2/dependencies/couchdb/src/couchdb/couch_server.erl"},{line,442}]},{gen_server,handle_msg,5,[{file,"gen_server.erl"},{line,604}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,239}]}]},{gen_server,call,[couch_server,{open,<<6 >> >> bytes>>,[{before_doc_update,#Fun<couch_users_db.before_doc_update.2>},{after_doc_read,#Fun<couch_users_db.after_doc_read.2>},sys_db,{user_ctx,{user_ctx,null,[<<6 >> >> bytes>>],undefined}},nologifmissing,sys_db]},infinity]}}}}}}}},[{couch_server_sup,start_server,1,[{file,"/SourceCache/XCSCouchDB/XCSCouchDB-2/dependencies/couchdb/src/couchdb/couch_server_sup.erl"},{line,98}]},{application_master,start_it_old,4,[{file,"application_master.erl"},{line,269}]}]}}}}}},[{couch,start,0,[{file,"/SourceCache/XCSCouchDB/XCSCouchDB-2/dependencies/couchdb/src/couchdb/couch.erl"},{line,18}]},{init,start_it,1,[]},{init,start_em,1,[]}]}} > > I see "error,eacces”, so I’d assume it’s due to a permission issue. But if > this is the case, it doesn’t make sense to me because the directory and files > have the correct permissions. It all matches other deployments which are > working just fine. I’m I overlooking something else? > > Thanks for the help, > > — Tito
