incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Myung <dmy...@dimagi.com>
Subject eaccess errors on running server
Date Fri, 04 Jan 2013 23:42:55 GMT
Hi All,


I'm running 1.2.0 on RHEL6, and am running into some strange behavior.

The server can run for stretches no problem, but occasionally when I'm
doing some major indexing operations, the indexing operation hangs.
The only way to get it back to a working state is to restart couch
entirely.

The errors in my _log file are filled with messages of eaccess on
various .beam files in my install. As soon as the first message
appears, view indexing operations stop.

https://gist.github.com/4458530

[Fri, 04 Jan 2013 23:13:31 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."}}

[Fri, 04 Jan 2013 23:13:31 GMT] [error] [<0.20.0>] {error_report,<0.9.0>,

                                 {<0.20.0>,std_error,

                                  "File operation error: eacces.
Target: ./couch_view_group.beam. Function: get_file. Process:
code_server."}}

[Fri, 04 Jan 2013 23:13:31 GMT] [error] [<0.20.0>] {error_report,<0.9.0>,

                                 {<0.20.0>,std_error,

                                  "File operation error: eacces.
Target: ./couch_view_updater.beam. Function: get_file. Process:
code_server."}}

[Fri, 04 Jan 2013 23:13:31 GMT] [error] [<0.20.0>] {error_report,<0.9.0>,

                                 {<0.20.0>,std_error,

                                  "File operation error: eacces.
Target: ./couch_ejson_compare.beam. Function: get_file. Process:
code_server."}}

[Fri, 04 Jan 2013 23:13:31 GMT] [error] [<0.20.0>] {error_report,<0.9.0>,


>From suggestions from the mailing list archives, I've double checked
and chown'ed all files couch touches - the install dir, the data and
design directories.

The strange thing is that the server can run for days no problem,
reindex incremental new data, pull replicate data in, etc, but the
past hour, I've have to reboot the server 3-4 times when reindexing
new and altered design documents from scratch.

I've double checked permissions on running files involved, but haven't
seen anything that catches my eye.

Anyone else run into this issue and have suggestions on how else to
troubleshoot this?


Thanks,


Dan

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message