Details
Description
i see these crashes after resetting the data path to /data which had data files from build with a different file format ( or let's say the file could be corrupted )
i am not sure what we can do in this case - keep the server running but show that the status is yellow for that node ?
"Incorrect disk header version"}}}
[error_logger:error,2012-11-14T16:09:17.527,ns_1@127.0.0.1:error_logger<0.5.0>:ale_error_logger_handler:log_msg:76]** Generic server couch_server terminating
** Last message in was {'EXIT',<0.10116.0>,
{bad_return_value,
{database_disk_version_error,
"Incorrect disk header version"}}}
** When Server state == {server,"/data",
{re_pattern,0,0,
<<69,82,67,80,91,0,0,0,16,0,0,0,1,0,0,0,0,0,0,
0,0,0,0,0,48,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,93,0,39,25,77,0,0,0,0,32,
224,255,3,254,255,255,135,254,255,255,7,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,69,26,84,0,39,0>>},
0,"Thu, 15 Nov 2012 00:09:17 GMT"}
** Reason for termination ==
i am not sure what we can do in this case - keep the server running but show that the status is yellow for that node ?
"Incorrect disk header version"}}}
[error_logger:error,2012-11-14T16:09:17.527,ns_1@127.0.0.1:error_logger<0.5.0>:ale_error_logger_handler:log_msg:76]** Generic server couch_server terminating
** Last message in was {'EXIT',<0.10116.0>,
{bad_return_value,
{database_disk_version_error,
"Incorrect disk header version"}}}
** When Server state == {server,"/data",
{re_pattern,0,0,
<<69,82,67,80,91,0,0,0,16,0,0,0,1,0,0,0,0,0,0,
0,0,0,0,0,48,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,93,0,39,25,77,0,0,0,0,32,
224,255,3,254,255,255,135,254,255,255,7,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,69,26,84,0,39,0>>},
0,"Thu, 15 Nov 2012 00:09:17 GMT"}
** Reason for termination ==