BigCouch lockups and beam segfaults

[Howard Hart]

We're using a standard three BigCouch server configuration running Erlang R15B03 and BigCouch 0.4.2 on 64-bit Linux and wondered if anyone else has encountered the following problems:

- random BigCouch server lockups during peak load times, where the server randomly stops responding to queries as well as stops logging entirely, requiring a full restart to fix. No apparent memory or CPU spikes prior to and all the processees are still running.

- at least one beam segfault per below, unfortunately with no corresponding core dump:

beam.smp[30382]: segfault at 8 ip 00000000004b7464 sp 00007f80906f0ab0 error 4 in beam.smp[400000+218000]

[Dave Cottlehuber]

Hi Howard

Segfaults in in Erlang are reasonably rare, so I'd suggest you specify exactly what version of linux you're running, where you installed erlang from, what startup parameters you're using, whther its real h/w or virtualised, and report this on erlang-questions mailing list.

Finally, if you can, move to R14B01 or R14B04 for your application. That's tried, true, and tested.  There's nothing in the newer releases that we want, and arguably some things we don't. None of those things don't cause segfaults, but some *might* be related to the hangs. 

A+

Dave

--
You received this message because you are subscribed to the Google Groups "BigCouch Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigcouch-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Howard Hart]

HI Dave,

   Thanks for the response and yeah, we're hearing R14 from multiple sources.


   Wrt the Linux we're running, it's Scientific Linux 6.1 on bare metal HP DL360s with 64GB of RAM and the following startup settings:

    beam.smp -K true -A 25 -Bd -- -root /usr -progname bigcouch -- -home /srv -- -boot /usr/releases/0.4.2/bigcouch -name bigcouch@hostname -setcookie ******** -sasl errlog_type error -noshell -noinput -noshell -noinput -couch_ini /usr/etc/default.ini /etc/kazoo/bigcouch/local.ini

   -env ERL_MAX_PORTS 65000, system file handle limits set to 1000000, max_dbs_open = 500  and q=3/r=2/w=2/n=3

   We bumped the ports, max_dbs_open, and file handles way up after hitting the wall on those a few times, so no longer an issue.

-Howard

You received this message because you are subscribed to a topic in the Google Groups "BigCouch Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bigcouch-user/C4DfAwBwA-g/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bigcouch-use...@googlegroups.com.

[vinay saini]

Hi Howard,

I have also got the same issue with one of my two clustered bigcouch. I am using those bigcouch for the kazoo.Since I am new to it, I don't understand how did you resolved this problem.

Can you please explain what are the changes need to be done and on which files.

Thanks,

Vinay Saini

[Howard Hart]

We actually never did resolve it. The problem just went away after a client-side upgrade.

Probably a pointer reference to nowhere that was cured by just changing the memory mapping slightly.