We've got two nodes of an 13 node cluster that are displaying the
following error:
[error] [emulator] [--------] Error in process <0.6945.1> on node
'****.nodeping.com' with exit value:
{{rexi_EXIT,{badarg,[{erlang,binary_to_term,1},{couch_file,pread_term,2},{c ouch_btree,get_node,2},{couch_btree,lookup,3},{couch_btree,lookup_kpnode,5} ,{couch_btree,lookup,2},{fabric_rpc,get_missing_revs,3},{rexi_server...
Anybody got any ideas what the error means and how to fix it?
We've already restarted the nodes multiple times. They're able to
reach all the nodes in the cluster.
That's most likely from a file that's corrupt. If you can narrow it to
the file you can either try truncating it a bit at a time (while
bigcouch isn't running) to see if you can reach before the error or
you can just blow it away and let internal replication fix it up.
We see this very rarely and the cases where we do see it are generally
tied to something like a machine that ran out of disk space or
operator error (ie, truncating the file while the node is online).
Anything like that happen recently?
On Thu, Jul 12, 2012 at 3:07 PM, Shawn Parrish <sparr...@nodeping.com> wrote:
> We've got two nodes of an 13 node cluster that are displaying the
> following error:
> [error] [emulator] [--------] Error in process <0.6945.1> on node
> '****.nodeping.com' with exit value:
> {{rexi_EXIT,{badarg,[{erlang,binary_to_term,1},{couch_file,pread_term,2},{c ouch_btree,get_node,2},{couch_btree,lookup,3},{couch_btree,lookup_kpnode,5} ,{couch_btree,lookup,2},{fabric_rpc,get_missing_revs,3},{rexi_server...
> Anybody got any ideas what the error means and how to fix it?
> We've already restarted the nodes multiple times. They're able to
> reach all the nodes in the cluster.