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
{{ message }}
This repository has been archived by the owner on Jan 14, 2020. It is now read-only.
[Tue Oct 29 12:14:23 2013] [error] [client 10.13.255.108] I could not get a lock for '/nfs/tuvfls02/nic/nic/tuvnic/lml/lab.conf': [Timed out waiting for blocking lock] at /usr/lib/lml/pxelinux.pl line 86
[Tue Oct 29 12:22:14 2013] [error] [client 10.13.255.132] I could not get a lock for '/nfs/tuvfls02/nic/nic/tuvnic/lml/lab.conf': [Timed out waiting for blocking lock] at /usr/lib/lml/pxelinux.pl line 86
[Tue Oct 29 12:22:20 2013] [error] [client 10.100.115.151] I could not get a lock for '/nfs/tuvfls02/nic/nic/tuvnic/lml/lab.conf': [Timed out waiting for blocking lock] at /usr/lib/lml/api/vm_overview.pl line 22, referer: http://tuvnic01.dev.is24.loc/lml/
[Tue Oct 29 12:22:37 2013] [error] [client 10.13.255.148] I could not get a lock for '/nfs/tuvfls02/nic/nic/tuvnic/lml/lab.conf': [Timed out waiting for blocking lock] at /usr/lib/lml/pxelinux.pl line 86
[Tue Oct 29 12:22:37 2013] [error] [client 10.13.255.189] I could not get a lock for '/nfs/tuvfls02/nic/nic/tuvnic/lml/lab.conf': [Timed out waiting for blocking lock] at /usr/lib/lml/pxelinux.pl line 86
[Tue Oct 29 12:22:56 2013] [error] [client 10.13.255.122] I could not get a lock for '/nfs/tuvfls02/nic/nic/tuvnic/lml/lab.conf': [Timed out waiting for blocking lock] at /usr/lib/lml/pxelinux.pl line 86
Possible Solutions
Split lab.conf into many small files so that booting a VM will only touch a few of them.
Use a persistent connection to vSphere. This will reduce script execution time by at least 3 seconds and also reduce the load on the vSphere server.
Separate VM boot from network, datastore, host and folder updates.
Probably we should do all 3 of these.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When too many VMs boot at the same time then the locking for the lab.conf runs into a timeout. Example log output proving the point:
And
Possible Solutions
Probably we should do all 3 of these.
The text was updated successfully, but these errors were encountered: