Oh, you'll also get eaccess errors if couch can't write the DB files or log files, as well, as mentioned on that page I linked to.
On Wed, May 26, 2010 at 11:35 AM, Paul Bonser <[email protected]> wrote: > On Wed, May 26, 2010 at 5:15 AM, cdr53x <[email protected]> wrote: > *snip* >> [Wed, 26 May 2010 10:08:16 GMT] [error] [<0.2647.0>] Uncaught error in HTTP >> request: {exit, >> {{{badmatch,{error,eacces}}, >> [{couch_config_writer,save_to_file,2}, >> {couch_config,handle_call,3}, >> {gen_server,handle_msg,5}, >> {proc_lib,init_p_do_apply,3}]}, >> {gen_server,call, >> [couch_config, >> {set,"couch_httpd_auth","secret", >> "21e33bf7c1bc1354fd1e06579dc549d1", >> true}]}}} > > That {error, eaccess} error generally means that the user you're > running couchdb as doesn't have write access to your config files, and > it looks like from the call there that it's trying to write back the > hashed version of your admin password. > >> >> >> I realy don't know the severity of the errors. The 0.10 version installed >> from debian package seem to pass all the tests. >> >> Any ideas on how to solve this ? > > The couchdb you installed from source is probably looking at > /usr/local/etc/couchdb for config files, whereas the one set up by the > packaged version probably went into /etc/couchdb, so you'll need to > update the permissions of all the couchdb directories, specifically > /usr/local/etc/couchdb and /usr/local/var/lib/couchdb > > See > http://wiki.apache.org/couchdb/Error_messages#Incorrect_Permissions_or_Missing_Directories > > > >> >> Regards, >> >> >> > > > > -- > Paul Bonser > http://probablyprogramming.com > -- Paul Bonser http://probablyprogramming.com
