Description of problem: If the geo-rep session is stopped, it logs 
new state : faulty  in geo-rep log file. 

sample logs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[2013-07-15 18:52:02.167277] E [syncdutils(/bricks/brick3):189:log_raise_exception] <top>: connection to peer is broken
[2013-07-15 18:52:02.168705] I [syncdutils(/bricks/brick3):158:finalize] <top>: exiting.
[2013-07-15 18:52:02.181000] I [monitor(monitor):81:set_state] Monitor: new state: faulty

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

geo-rep stop should log something meaning full like stopped or something like that. 

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


How reproducible: Consistently 


Steps to Reproduce:
1.Create and start a geo-rep relationship between master and slave volume.
2.Now stop the geo-rep session.
3.Check the geo-rep log-file. 

Actual results:  geo-rep stop logs new state: faulty in geo-rep log file. 


Expected results: when the session is stopped, it should log something like stopped the session.


Additional info: