You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A storage router's state becomes FAILURE in red color after it was rebooted, but everything still looks working well.
(1) ovs.storagerouter.ping
In sys log, the task ovs.storagerouter.ping never shows up on node1 since last reboot, but it is not absent on the other two nodes (master) every minute.
All 3 nodes including itself can't make connection to 192.168.0.33.
(3) Celery
Checked celery:
celery inspect ping -b amqp://ovs:[email protected]// --timeout=5
-> celery@node1: OK
pong
-> celery@node3: OK
pong
-> celery@node2: OK
pong
Any idea about how to fix it? The failure state has happened before and there's no way to cure it all the time. I've read the issue #558 and #565, but not sure if they have the same cause.
Best regards,
Yongsheng
The text was updated successfully, but these errors were encountered:
Hello,
A storage router's state becomes
FAILURE
in red color after it was rebooted, but everything still looks working well.(1) ovs.storagerouter.ping
In sys log, the task
ovs.storagerouter.ping
never shows up on node1 since last reboot, but it is not absent on the other two nodes (master) every minute.(2) RabbitMQ
RabbitMQ reports error once a minute in [email protected]
All 3 nodes including itself can't make connection to 192.168.0.33.
(3) Celery
Checked celery:
Any idea about how to fix it? The failure state has happened before and there's no way to cure it all the time. I've read the issue #558 and #565, but not sure if they have the same cause.
Best regards,
Yongsheng
The text was updated successfully, but these errors were encountered: