http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/MB-7479 Couchbase Server Installed 2 Servers with latest version, created initial server and added some basic docs, index like post_picture_1 and so on, docs are in jason format. <br/> As long its only single server all works fine. When i add 2nd Server and finish rebalance i see the docs are distributed among both servers. When i go <br/> to buckets it shows activity indicator and comes back with &quot;There are currently no documents in this bucket.&quot; if i search for the doc by index it either <br/> returns nothing or sometimes reports it lost communication to server. When going back to the server the gui was run on in the os, i can verify status <br/> that couchbase no longer runs and i need to start manually again. <br/> So i am not certain if the 2 issues are related to each other why there is no data in the document screen in gui once i use cluster. All works normal <br/> with single server. I also was able to create same issues with 3 server cluster &nbsp;running version 2.0.0 enterprise edition (build-1976) on 2 Servers Ubuntu 11.10 MB-7479

No data returned when using 2 or more nodes via gui as well as server crash

Bug Major Closed Fixed Public Xiaoqin Ma makeawish Wed, 2 Jan 2013 14:43:03 -0600 Fri, 5 Apr 2013 02:35:02 -0500 Wed, 27 Feb 2013 17:11:31 -0600 2.0 2.0.2 couchbase-bucket 0 4 Can you attach the server logs so I can take a look? They can generated by running /opt/coucbase/bin/collectinfo. You can also get them by clicking on the logs tab in the web console and then clicking the link that says &quot;generate diagnostic report&quot;. Uploaded diag file <br/> If you need anything else, let me know Shows both servers and 5 docs Data Bucket shows also 5 docs in default Screen shows searching for docs for about 10 to 15 sec Returns no Docs in bucket even so there are docs in the bucket How much memory does each server contain? Can you also run top on one of the machines and paste the output here? From looking at the logs it appears that one of the processes in the server is being kill by the OS. This information will help me to understand if this is the case. Right now they ron with 512 MB, but i thought it was the mem issue and moved the VM&#39;s to GB and it behaved still same way. The single server (non cluster ) behaves just fine with 512 MB or 8 GB For the bug distributions in the engine team. @makawish, what is the size of your document? Do you have log files? Thanks! Xiaoqin,<br/> <br/> The logs for this issue are already attached. I looked through the logs and memcached looks like it is continually killed by the OS for some reason. See the message below where sigkill (137) is reported. I don&#39;t think there is anything we can do about this since a non-Couchbase process is killing us.<br/> <br/> =========================CRASH REPORT=========================<br/> &nbsp;&nbsp;crasher:<br/> &nbsp;&nbsp;&nbsp;&nbsp;initial call: ns_port_server:init/1<br/> &nbsp;&nbsp;&nbsp;&nbsp;pid: &lt;0.881.0&gt;<br/> &nbsp;&nbsp;&nbsp;&nbsp;registered_name: ns_port_memcached<br/> &nbsp;&nbsp;&nbsp;&nbsp;exception exit: {abnormal,137}<br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;in function gen_server:terminate/6<br/> &nbsp;&nbsp;&nbsp;&nbsp;ancestors: [&lt;0.879.0&gt;,ns_port_sup,ns_server_sup,ns_server_cluster_sup,<br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;0.58.0&gt;]<br/> &nbsp;&nbsp;&nbsp;&nbsp;messages: [{&#39;EXIT&#39;,#Port&lt;0.7456&gt;,normal}]<br/> &nbsp;&nbsp;&nbsp;&nbsp;links: [&lt;0.879.0&gt;]<br/> &nbsp;&nbsp;&nbsp;&nbsp;dictionary: []<br/> &nbsp;&nbsp;&nbsp;&nbsp;trap_exit: true<br/> &nbsp;&nbsp;&nbsp;&nbsp;status: running<br/> &nbsp;&nbsp;&nbsp;&nbsp;heap_size: 75025<br/> &nbsp;&nbsp;&nbsp;&nbsp;stack_size: 24<br/> &nbsp;&nbsp;&nbsp;&nbsp;reductions: 1342314<br/> &nbsp;&nbsp;neighbours:<br/> <br/> [error_logger:error,2012-12-20T0:58:59.107,<a href='mailto:ns_1@10.181.2.115'>ns_1@10.181.2.115</a>:error_logger&lt;0.5.0&gt;:ale_error_logger_handler:log_msg:76]** Generic server &lt;0.879.0&gt; terminating <br/> ** Last message in was {die,{abnormal,137}}<br/> ** When Server state == {state,memcached,5000,<br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{1355,962940,896183},<br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;undefined,infinity}<br/> ** Reason for termination == <br/> ** {abnormal,137}<br/> I&#39;m closing this issue since the logs show that the memcached process appears to be killed by the os. sigkill Date of First Response Wed, 2 Jan 2013 17:08:03 -0600 Rank 2848 Time In Status