incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kore Nordmann (JIRA)" <j...@apache.org>
Subject [jira] Created: (COUCHDB-133) Strange "random" error in view update
Date Wed, 01 Oct 2008 19:27:44 GMT
Strange "random" error in view update
-------------------------------------

                 Key: COUCHDB-133
                 URL: https://issues.apache.org/jira/browse/COUCHDB-133
             Project: CouchDB
          Issue Type: Bug
          Components: Database Core
    Affects Versions: 0.9
         Environment: Linux 2.6.26-gentoo-r1 #3 PREEMPT
            Reporter: Kore Nordmann


Never experiencing this when running an application normally, but when I run a test suite,
which of course executes lots of queries in a quite short time frame. The error I get back
from CouchDB (revision 700854) is:

> Error (500) in request: error ({{nocatch,{error,eacces}},[{couch_view,start_update_loop,4}]}).

This does not always seem to happen in the same test case, and after that error I can't connect
to CouchDB for a short tim espan anymore (less then a second), but it comes back most times.

Some times CouchDB stops responding completely until it is restarted after that error.

A request causing this for example looks like:

> GET /arbit_test/_view/users/user?key=null HTTP/1.1
> Host: localhost
> Connection: Keep-Alive

> HTTP/1.1 500 Internal Server Error 
> Server: CouchDB/0.9.0a694945-incubating (Erlang OTP/R12B)
> Date: Wed, 01 Oct 2008 18:27:33 GMT
> Content-Type: text/plain;charset=utf-8
> Content-Length: 90
> Cache-Control: must-revalidate
> 
> {"error":"error","reason":"{{nocatch,{error,eacces}},[{couch_view,start_update_loop,4}]}"}

The full HTTP log of a test run and the corresponding couch.log with log level=debug can be
found here:

http://k023.de/http.log
http://k023.de/couch.log

I hope this helps debugging this issue. If you need more information you may contact me on
IRC (timezone: GMT; nick: koredn) in the CouchDB channel.

If you want to run the test suite yourself, to reproduce the failures, you'd need PHP 5.3
(sic!) and the latest version of PHPUnit[1] installed. Then you can just do so, by executing:

> svn co svn://arbitracker.org/arbit/trunk arbit ; cd arbit
> ./runTests controller

Kind regards,
Kore

[1] http://www.phpunit.de/manual/3.3/en/installation.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message