title: Cassandra OpsCenter Repair Service Stops
body: <p>After starting the repair service, it shows a percentage illustrating the current repair process going. When the whole cluster is repaired, it goes OFF again.</p>
  
  <p>I thought it was repairing the whole cluster smoothly, forever, starting again and again, but it appears to "finish"... which is not my expectation</p>
  
  <p>Did I miss something?</p>
  
  <ul>
  <li>OpsCenter 5.2.0</li>
  <li>DSE 4.6.7</li>
  </ul>
  
  <p>Edit:</p>
  
  <p>Logs:</p>
  
  <pre><code>2015-09-02 08:33:34+0000 [XX]  INFO: Detected a topology change. The Repair Service will stop now and check the cluster topology every 5 minutes. If the cluster is stable, the Repair Service will start again.
  2015-09-02 08:33:34+0000 [XX]  INFO: Stopping Repair Service
  2015-09-02 08:48:34+0000 []  INFO: Unhandled error in Deferred:
  2015-09-02 08:48:34+0000 [] Unhandled Error
      Traceback (most recent call last):
        File "/usr/share/opscenter/lib/py-debian/2.7/amd64/twisted/internet/defer.py", line 361, in callback
          self._startRunCallbacks(result)
        File "/usr/share/opscenter/lib/py-debian/2.7/amd64/twisted/internet/defer.py", line 455, in _startRunCallbacks
          self._runCallbacks()
        File "/usr/share/opscenter/lib/py-debian/2.7/amd64/twisted/internet/defer.py", line 542, in _runCallbacks
          current.result = callback(current.result, *args, **kw)
        File "/usr/share/opscenter/lib/py-debian/2.7/amd64/twisted/internet/defer.py", line 1076, in gotResult
          _inlineCallbacks(r, g, deferred)
      --- &lt;exception caught here&gt; ---
        File "/usr/share/opscenter/lib/py-debian/2.7/amd64/twisted/internet/defer.py", line 1020, in _inlineCallbacks
          result = g.send(result)
        File "/usr/lib/python2.7/dist-packages/opscenterd/cluster/Repair.py", line 909, in startRepairService
  
      opscenterd.cluster.Repair.RepairServiceAlreadyRunning: The Repair Service is already running.
  </code></pre>
  
  <p>It seems that OpsCenter is failing at starting again the repair service after a topology change (Adding a node)</p>