incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Tisdall <>
Subject Re: couchdb returning empty response
Date Thu, 16 Aug 2012 20:08:57 GMT
Okay, I double checked every file under /usr/local/lib/couchdb and
every one has read access to all.  None of the .beam files need
execute permission, right?

Besides, the server starts up and runs fine with no eaccess errors
until several thousand queries are made.  Also, after it crashes and
gives those errors, it automatically restarts it continues running
with no problem.  I'm thinking it's something deeper in the kernel
that temporarily stops access to those files and then goes back to
normal...   I'm running everything on a virtualized server on
 However, I've also had the couchdb server restart without those
eaccess errors.

Will running couchdb in interactive mode give me any more logging
information that what goes into couch.log?

On Thu, Aug 16, 2012 at 3:44 PM, Dave Cottlehuber <> wrote:
> On 16 August 2012 17:16, Tim Tisdall <> wrote:
>> I tried running my code again and got a bunch of these entries in my logs:
>> [Thu, 16 Aug 2012 14:53:03 GMT] [error] [<0.20.0>] {error_report,<0.9.0>,
>>                                  {<0.20.0>,std_error,
>>                                   "File operation error: eacces.
>> Target: ./mochiweb_response.beam. Function: get_file. Process:
>> code_server."}}
>> here's the file listing for the file (as you can see it's readable by all):
>> -rw-r--r-- 1 root staff 1420 Aug  7 21:11
>> /usr/local/lib/couchdb/erlang/lib/mochiweb-1.4.1/ebin/mochiweb_response.beam
> As you noticed, this is file permissions related. So check all of
> those, esp permissions on the couchdb .beam files.
> If you're logged in as that user, does pushd
> /usr/local/lib/couchdb/erlang/lib/mochiweb-1.4.1/ebin && cat
> mochiweb_response.beam > /dev/null work?
> I usually do an
>     $ sudo -u couchdb couchdb -i
> to start couchdb in interactive mode before switching to daemon usage.
> Maybe a recursive chmod / chown on/usr/local/lib/couchdb is in order?
> If you let me know what arch/platform this is on, I'll check tomorrow
> on a fresh install if that doesn't fix it, using your notes provided.
> A+
> Dave

View raw message