it's possible to set up "moxi bucket" on ssl proxy port (was: Failure in XDCR- System Test during Scenario:: failover_one_and_rebalance_out_at_dest)

Test Scenario

Cluster Description

Source Cluster: 8 nodes

Target Cluster: 8 nodes

3 buckets - 2 non-sasl buckets and 1 saslbucket
1. standardbucket (bi-directional) <---the bucket under discussion
2. standardbucket1 (uni-directional)
3. saslbucket (no xdcr)

Scenarios which passed:: rebalance_out_one_at_source, rebalance_in_one_source, failover_one_and_rebalance_out, failover_one_and_add_back, rebalance_out_one_at_destination, rebalance_in_one_destination

Scenario Where the Test Fails:: failover_one_and_rebalance_out_at_dest

Scenario Description from the .js file

"8" :
{
"name" : "failover_one_and_rebalance_out_dest",
"desc" : "failover_one_and_rebalance_out_at_dest",
"workload" : ["b:standardbucket,s:3,u:22,g:70,d:3,e:2,m:5,ttl:3000,ccq:std1ph5keys,ops:3000",
"b:standardbucket1,s:3,u:22,g:70,d:3,e:2,m:5,ttl:3000,ccq:std2ph5keys,ops:3000",
"b:saslbucket,pwd:password,s:3,u:22,g:70,d:3,e:2,m:5,ttl:3000,ccq:saslph5keys,ops:3000"],
"cluster" :

},

The node was removed but rebalance did not proceed. Seeing Erlang Crashes

Most Recent Log from UI Snap-shot::

ort server xdcr_proxy on node 'babysitter_of_ns_1@127.0.0.1' exited with status 1. Restarting. Messages: {"Kernel pid terminated",application_controller,"{application_start_failure,ns_ssl_proxy,{shutdown,

}}) ns_log000 ns_1@172.23.105.55 12:38:29 - Tue Jan 21, 2014

Uploaded Logs

Source Cluster
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.44-1212014-1117-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.45-1212014-1120-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.47-1212014-1122-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.48-1212014-1124-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.49-1212014-1126-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.50-1212014-1128-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.51-1212014-1131-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.52-1212014-1134-diag.zip

Target Cluster
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.54-1212014-1136-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.55-1212014-1140-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.57-1212014-1144-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.58-1212014-1149-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.60-1212014-1153-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.61-1212014-1157-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.62-1212014-121-diag.zip
https://s3.amazonaws.com/bugdb/jira/MB-9975/172.23.105.63-1212014-124-diag.zip

Action items for QE
---------------------------
Re-run this particular scenario in an isolated way