On Wed, Mar 30, 2011 at 7:10 AM, Robert Newson <[email protected]> wrote: > yes, they are significant errors. couchdb is unable to load some of > its modules, it's surprising it appears to work. > > B. > > On 30 March 2011 00:46, Wayne Conrad <[email protected]> wrote: >> When I start couchdb, I see dozens of eacces errors in the log: >> >> [Tue, 29 Mar 2011 23:25:47 GMT] [error] [<0.20.0>] {error_report,<0.9.0>, >> {<0.20.0>,std_error, >> "File operation error: eacces. Target: >> ./couch_secondary_sup.beam. Function: get_file. Process: code_server >> ."}} >> [Tue, 29 Mar 2011 23:25:47 GMT] [error] [<0.20.0>] {error_report,<0.9.0>, >> {<0.20.0>,std_error, >> "File operation error: eacces. Target: >> ./couch_db_update_notifier_sup.beam. Function: get_file. Process: co >> de_server."}} >> ... >> >> couchdb does start and appears to work, though. Checking permissions on one >> of the files, I see: >> >> -rw-r--r-- 1 couchdb couchdb 1260 Mar 23 13:57 >> ./lib/couchdb/erlang/lib/couch-1.2.0ac052866-git/ebin/couch_secondary_sup.beam >> >> I'm running the trunk of the git tree, couch-1.2.0ac052855-git. >> >> Are these errors significant? >> >
I've seen these errors before but they always turn out to be a red herring when looking for something else. So far as I can tell they're not really an issue, but I don't have a definitive answer on why they occur.
