Description of problem:
When the ssh pem file is not present geo-rep start returns success and proper success message. But since the pem file is not present it logs error in the log files. It would be great to indicate the user via CLI output whenever pem file setup is not present along the log messages in the log file.

Version-Release number of selected component (if applicable):
glusterfs-3.4.0.39rhs-1.el6rhs.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Don't create the ssh pem setup and run geo-rep create.

Actual results:
geo-rep create and even start succeeds, but since actually the pem file is not  present it log Error message in the log file and goes to faulty state.



Expected results:
geo-rep create should throw error to stderr saying that the ssh pem file is not present.

Additional info:

The log files log following error. Ideally it should also indicate the user through the warning/error message as a CLI output.

[2013-11-05 17:46:31.898323] W [syncdutils(/rhs/bricks/brick0):198:log_raise_exception] <top>: !!!!!!!!!!!!!
[2013-11-05 17:46:31.898716] E [resource(/rhs/bricks/brick0):204:errlog] Popen: command "ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/secret.pem -oControlMaster=auto -S /tmp/gsyncd-aux-ssh-sUpWP0/gsycnd-ssh-%r@%h:%p root@falcon /nonexistent/gsyncd --session-owner 3e02c9ad-d29b-453f-908e-b6a3b2b156d4 -N --listen --timeout 120 gluster://localhost:slave" returned with 127, saying:
[2013-11-05 17:46:31.898997] E [resource(/rhs/bricks/brick0):207:logerr] Popen: ssh> Warning: Identity file /var/lib/glusterd/geo-replication/secret.pem not accessible: No such file or directory.
[2013-11-05 17:46:31.899321] E [resource(/rhs/bricks/brick0):207:logerr] Popen: ssh> bash: /nonexistent/gsyncd: No such file or directory
[2013-11-05 17:46:31.899852] I [syncdutils(/rhs/bricks/brick0):159:finalize] <top>: exiting.