On May 26, 12:45 pm, lasizoillo <[email protected]> wrote:
> 2009/5/26 Thomas G. Willis <[email protected]>:
> Maybe is not a couchdb issue and is a erlang (BEAM), freebsd or
> anything else issue.
>
> Maybe my problem is like
> this:http://www.erlang.org/pipermail/erlang-patches/2008-July/000258.html
>
> I don't know why erlang crash with core dumped when write over a
> corrupted register. The crash affects other connections for some
> seconds raising errors. You can read the corrupt register, but not
> modify or delete it. Compactations (read entire db and generates new
> one with lesser size) don't solve the problem, but you gets a less
> size corrupt db. With replication, you obtain a failure or a corrupt
> replicated db.
>
> The database have sensible information (I can't send it to developers
> team). I don't know how to recreate the error. I can't create an issue
> saying "somethings fails".
>
>
>
> > Also, you need the trunk version of python-couchdb in order for views
> > to work properly on the latest version of couch. In case anyone else
> > reading this is having those issues.
I see,
Erlang crashing with a core dump seems to be a very bad thing. One
thing you might want to try is building the latest erlang and then
building the latest couchdb. This is what I'm running (on jaunty) and
it's been running pretty rock solid for me.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
