Yep, that matches up with my experience. Adam On Oct 3, 2012, at 10:47 AM, Martin Hewitt wrote: > This one's further complicated by the fact that, after spitting out errors at start, CouchDB appears to operate normally with no further errors. Generating a view produces another error, but the view is generated correctly, and further view updates do not produce errors. > > Very curious behaviour. > > Martin > > > On Wednesday, 3 October 2012 at 15:44, Adam Kocoloski wrote: > >> This one in particular has always been a bit of a mystery to me. Sometimes it seems to be completely spurious. >> >> Adam >> >> On Oct 3, 2012, at 8:08 AM, Martin Hewitt wrote: >> >>> Hi Dave, >>> >>> Thanks for these links, no luck on my current install, but I may scrub down and start again, as I can't really map what's going on, so probably won't be able to work out what makes a difference! >>> >>> Martin >>> >>> >>> On Wednesday, 3 October 2012 at 13:01, Dave Cottlehuber wrote: >>> >>>> On 3 October 2012 13:35, Martin Hewitt wrote: >>>>> Hi all, >>>>> >>>>> I've recently compiled CouchDB from source, on an EC2 instance, and I'm seeing a lot of eacces errors of the form: >>>>> >>>>> [Wed, 03 Oct 2012 11:32:22 GMT] [error] [<0.19.0>] {error_report,<0.9.0>, >>>>> {<0.19.0>,std_error, >>>>> "File operation error: eacces. Target: ./mochiweb.beam (http://web.beam). Function: get_file. Process: code_server."}} >>>>> >>>>> >>>>> Now I know this is a permissions issue, but I can't work out what permissions I need to change. >>>>> >>>>> I've changed the owner on the data directories, ERLang directories any many more besides, but I'm still getting the error. >>>>> >>>>> If anyone could point me in the right direction, I'd be hugely grateful. >>>>> >>>>> Thanks, >>>>> >>>>> Martin >>>> >>>> Most of the info is in here: >>>> https://github.com/apache/couchdb/blob/master/INSTALL.Unix#L175-187 >>>> and some on the wiki >>>> http://wiki.apache.org/couchdb/Installing_on_Ubuntu or similar ones >>>> for other linux variants may help. >>>> >>>> su to the couch user, and then run couchdb interactively `couchdb -i` >>>> which sometimes spits out a moment of clarity. >>>> >>>> IIRC there was a recent-ish example on the user@ mailing list but I >>>> unfortunately don't recall the solution! >>>> >>>> A+ >>>> Dave >>>> >>> >>> >> >> >> > >