From the information you provide there are two scenarios I see:
1. You may have started CouchDB with different permissions than its
files have (e.g., you start CouchDB with regular user permissions while
the log file, for example, have root permissions).
2. SpiderMonkey too new and incompatible with CouchDB.
How to check if the scenarios:
1. Start CouchDB as with root privileges.
2. Downgrade your SpiderMonkey version.
I cannot guarantee that these are the only possibilities. It may be a
good idea to check if Erlang is working properly on your OS.
Nevertheless, I hope my suggestions will help you.
CGS
On 12/15/2011 03:41 PM, Peta Bogdan wrote:
also, I don't use the javascript engine, in fact I don't use views at all,
Instead the documents are indexed through an elasticsearch instance which
happens to be on the same machine
All queries are conducted tru elasticsearch, while the database is busy
with only inserts and updates.
I used to build views using erlang language, but as the database grows the
time taken to regenerate the views increases, so I dropped this method of
querying the database.
As a side note icu version is icu4c-4.8, installed from ports.
also forgot to mention that OS is OpenBSD5.0/amd64 if it makes a difference
.
On Thu, Dec 15, 2011 at 4:01 PM, Peta Bogdan<[email protected]> wrote:
Hello,
1. OS: OpenBSD5.0 GENERIC.MP
2. SpiderMonkey: Version: 1.9.2.16, installed from ports
3. CouchDB installed from sources
4. The server crashed just before this last insert
On Thu, Dec 15, 2011 at 3:45 PM, CGS<[email protected]> wrote:
Hi,
It would be helpful if you could specify the followings:
1. your OS;
2. SpiderMonkey version;
3. how you installed CouchDB/1.1.1;
4. if the message in couch.stderr was stamped before or after you sent
the insertion command.
CGS
On 12/15/2011 02:16 PM, Peta Bogdan wrote:
Hello,
Today I had a strange experience with my CouchDB/1.1.1 (Erlang
OTP/R14B04) .
After I inserted a normal size document (ten fields) into database, this
crashed unexpectedly, and nothing appears in logs (log_level = debug) ,
only in coucdb.stderr the following line:
heart_beat_kill_pid = 10014
heart_beat_timeout = 11
heart: Thu Dec 15 14:08:19 2011: heart-beat time-out.
Killed
heart: Thu Dec 15 14:08:23 2011: Executed
"/usr/local/couchdb/1.1.1/bin/**couchdb -k". Terminating.
I don't know what cause heart-beat mechanism to activate and why it timed
out?
Any help very much appreciated.
Thank you,
Bogdan
