-
Notifications
You must be signed in to change notification settings - Fork 938
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to run "lxc cluster list" on cluster member Error: Failed to get the address of the cluster leader: context deadline exceeded #15035
Comments
Please provide output of |
Output of
|
Could be high load or network latency between cluster members. |
Try doing |
Or you could try stopping some of the workloads on dellserver7.internal.net and see if it improves. |
Load is about 0-5 on across all systems (multi-core+socket) I will look at the |
Correct. |
Could also try reloading LXD on dellserver7.internal.net too to ensure there's no issue with LXD generally. |
I ran log file rotated and new entries are:
|
@tomponline the reload seems to have the unintended consequence of "disconnecting" running VMs from LXD management. An attempt to start a VM where the
Is this expected or avoidable ? |
What does this command show:
|
here it is
|
Try doing |
I get
In the |
Looks like you still have a process running holding that mount open, take a look for virtfs-proxy-helper and virtiofsd. |
I am unable to run
lxc cluster list
on a cluster member. VMs continue to operate.On dellserver7.internal.net
on another node in the cluster
also on another node in the cluster:
log entries on dellserver7:
The text was updated successfully, but these errors were encountered: