Hmm could the module causing the crash if the device isn't accessible?
@TeddyAstie any opinion?
Hmm could the module causing the crash if the device isn't accessible?
@TeddyAstie any opinion?
First, let's collect the exact commands you are using to hide it from the Dom0, in case there's a typo
Hello and welcome here!
That's weird than just hiding the device from the Dom0 is causing an issue Do you have any logs during the crash we can check?
If the message is displayed, there is a reason. Please do a timdatectl status
on your XOA
That you have NTP correctly configured/enabled everywhere
That's because you are using DMC (dynamic memory control). Try on a VM with static == dynamic.
If you want to test, you can switch to the relevant branch, which is fix_replication
It's indeed pretty long. I would maybe use a local SR as suspend SR to check if it's very different, that could help to pinpoint the issue.
Let's try to grep 127.0.0.1
in the XAPI DB file then
I would print the result of the command xe host-param-list uuid=<problematic host UUID>
to see where this localhost IP is set somlewhere.
Then, there is one machine thinking its management IP is 127.0.0.1
@cgasser said in Nos stats problem (but not the know one I guess):
connect ECONNREFUSED 127.0.0.1:443
That's the issue. XO needs to have access to all hosts management IPs, not just the master. I assume you made a tunnel or something specific to make XO connecting to the master. It's not related to 8.2 or 8.3, it's an architecture thing on pools since XCP exists
Hi,
How much RAM your VM had?
Food for thoughts for the @Team-Storage and @Team-XAPI-Network
@Andrew And it doesn't with the commit just before?
Hi,
Do you have any error message? What's happening? Anything visible or not?