Stuck in maintenance mode after joining pool.
-
I have a 2 host pool setup. They have a standard network and a storage network. No VLAN tagging, the ports on the switch are just separated for storage and they go to a bonded interface on a Synology.
I am trying to add a 3rd host to the pool and have successfully gone through the add process but it will not come out of maintenance mode.
I made sure to update all servers to latest before adding the 3rd host to the pool. The new host can ping all servers on the main network and the storage network. However, its intermittently telling me from the console that the Pool master is unreachable. I have checked the conf file and its pointing to the correct IP for master. I can also ping it directly. Also, this error comes and goes in the console.
When I try to look at the host in Xen Orchestra it just says "An error has occurred".
It does think the host is in the pool though. Sometimes...
I tried to eject it and it timed out saying it couldn't communicate with the server. So then I tried to forget it and it says that the host is still live so it couldn't remove it.
When I look at the NICs in the console I get this message.
I tried to repair the shared storage and got the error, "Internal Error: Helpers.No_domain_zero."
Which from what I looked up was a domain memory error. I have 1.8GB dom memory but I went ahead and manually upgraded that to 4GB but still got same error.
When I go to display NICs on xsconsole this is what it says.This server was working just fine in a different pool the week prior. I have since wiped it clean and started fresh. Here is a link to all pictures from the thread in case they are not showing up for anyone: https://imgur.com/a/EtLgNfX
I don't know what to try next.
-
@DwightHat said in Stuck in maintenance mode after joining pool.:
When I try to look at the host in Xen Orchestra it just says "An error has occurred".
Check to browser's Dev Tools console when this happens. It will likely contain some additional details.
You likely need to check the logs to find out why you are encountering this issue. Many times the "stuck in maintenance mode" issue is related to an unmountable storage repository.
