How to fix XOSTOR

fred974

@ronan-a Could you please help me please?

brodiecyber

@fred974 it looks like the logs say it cant find the controller can you confirm if it is running on any of your hosts.

im no expert but its a start

fred974

@brodiecyber Thank you for your help. I ran the command but got this message

[16:28 uk ~]# xe host-call-plugin host-uuid=5a1e10ec-4f1a-469d-d5h7-adb8535741ca plugin=linstor-manager fn=has-ControllerRunning
Error code: UNKNOWN_XENAPI_PLUGIN_FUNCTION
Error parameters: has-ControllerRunning

fred974

@brodiecyber I found the correct cmd..

[16:45 uk ~]# xe host-call-plugin host-uuid=5a1e10ec-4f1a-469d-d5h7-adb8535741ca plugin=linstor-manager fn=hasControllerRunning
False

linstor resource list

[16:49 uk ~]# linstor resource list
Error: Unable to connect to linstor://localhost:3370: [Errno 99] Cannot assign requested address

brodiecyber

@fred974

So we know its not running to that host as the command is targeting a single hosts uuid.

have you run it on all your XCP-ng servers to confirm if the controller is running on any of them. perhaps check to make sure the lunstor controller is available on any host

fred974

@brodiecyber yes, it says 'False' on all 4x hosts. The controller isn't running on any hosts

brodiecyber

@fred974

ok so thats our problem the lunstor controller is not running on any node so XOSTOR has no way to initialize. Im going to do some reading and see what comes up

brodiecyber

@fred974

Maybe also post in the XOSTOR thread
A controller failure should be on the radar for possible failure scenarios.
https://xcp-ng.org/forum/topic/5361/xostor-hyperconvergence-preview

brodiecyber

@fred974

also see if this script is available on the last host that has the controller which we can assume is the host that failed the first time. Maybe it has some data on why the controller isn't initializing

controller 2.PNG

fred974

@brodiecyber I can see it exist in /opt/xensource/bin/linstor-kv-tool but no idea on how to use it