Hi,
Since upgrading to 3.8.13, the replication service no longer starts. When I try to start it, the button turns green for a few seconds and then back to “Off”.
/opt/rockstor/var/log/supervisord_replication_stderr.log has this error repeated many times:
Process ReplicaScheduler-1:
Traceback (most recent call last):
File “/usr/lib64/python2.7/multiprocessing/process.py”, line 258, in _bootstrap
self.run()
File “/opt/rockstor/src/rockstor/smart_manager/replication/listener_broker.py”, line 185, in run
frontend.bind(‘tcp://%s:%d’ % (self.listener_interface, self.listener_port))
File “zmq/backend/cython/socket.pyx”, line 487, in zmq.backend.cython.socket.Socket.bind (zmq/backend/cython/socket.c:5156)
File “zmq/backend/cython/checkrc.pxd”, line 25, in zmq.backend.cython.checkrc._check_rc (zmq/backend/cython/socket.c:7535)
raise ZMQError(errno)
ZMQError: No such device
And /opt/rockstor/var/log/supervisord.log:
2016-05-07 09:33:40,477 INFO spawned: ‘replication’ with pid 1302
2016-05-07 09:33:41,343 INFO exited: replication (exit status 0; not expected)
2016-05-07 09:33:42,351 INFO spawned: ‘replication’ with pid 1315
2016-05-07 09:33:42,944 INFO exited: replication (exit status 0; not expected)
2016-05-07 09:33:44,949 INFO spawned: ‘replication’ with pid 1327
2016-05-07 09:33:45,525 INFO exited: replication (exit status 0; not expected)
2016-05-07 09:33:49,069 INFO spawned: ‘replication’ with pid 1357
2016-05-07 09:33:49,664 INFO exited: replication (exit status 0; not expected)
2016-05-07 09:33:50,665 INFO gave up: replication entered FATAL state, too many start retries too quickly
Any ideas? I suspect Rockstor cannot bind to whatever “tcp://%s:%d’” is. I have removed all send tasks and other appliances to no avail. Many thanks.