check_ssh is wrongly claiming ssh tests are failing (user == root) about mysql-master-ha HOT 5 OPEN

I get the same problem, but for all hosts throughout my cluster. I'm using a 
non-root user. The manual checks from any host to any host succeed, but MHA 
checks fail:

--------------------------------------------------------------
Mon Aug 27 18:30:22 2012 - [debug]  Connecting via SSH from 
[email protected](10.248.86.135:22) to 
[email protected](10.248.109.158:22)..
Permission denied (publickey).
Mon Aug 27 18:30:23 2012 - [error][/usr/share/perl5/MHA/SSHCheck.pm, ln107] SSH 
connection from [email protected](10.248.86.135:22) to 
[email protected](10.248.109.158:22) failed!
Mon Aug 27 18:30:24 2012 - [error][/usr/share/perl5/MHA/SSHCheck.pm, ln63] 
Mon Aug 27 18:30:22 2012 - [debug]  Connecting via SSH from 
[email protected](10.248.109.158:22) to 
[email protected](10.248.86.135:22)..
Permission denied (publickey).
Mon Aug 27 18:30:24 2012 - [error][/usr/share/perl5/MHA/SSHCheck.pm, ln107] SSH 
connection from [email protected](10.248.109.158:22) to 
[email protected](10.248.86.135:22) failed!
Mon Aug 27 18:30:25 2012 - [error][/usr/share/perl5/MHA/SSHCheck.pm, ln63] 
--------------------------------------------------------------

And, for example:

--------------------------------------------------------------
ubuntu@ip-10-248-109-158:~$ ssh [email protected]
Welcome to Ubuntu 12.04 LTS (GNU/Linux 3.2.0-25-virtual x86_64)
...(other successful login text snipped)...
--------------------------------------------------------------

I'm perplexed. I'll be digging in as well, and if I solve it, I'll post back 
here.

Timeless...,

I think it is safe to suppose that mha is not ready for open source users .. 
The author probably would prefer that you approach his commercial company and 
purchase support to help with this.

I moved on, and suggest you do too .. percona extradb cluster (with galera) is 
a very neat solution and is still opensource but with commercial support .. 
google for it, and move onto that .. It offers you master-slave if that is what 
you want, but it provides a better solution through clusters of n-nodes ... 

Good luck .. 

Does the error repeat every time? Or do you sometimes succeed and sometimes get 
errors? If you succeed sometimes, would you please try increasing MaxStartups 
parameter in all sshd_config, restart sshd and try again?

This seems to be exactly the same issue as I posted about here: 
http://code.google.com/p/mysql-master-ha/issues/detail?id=13#c9 - I needed to 
have my SSH key named "id_dsa" and then it worked.

Hello,

I had the same error. 

The solution is :
each server should have their pub key in their authorized_keys.