Problem starting lxc conteiner while another is created.

[Alex Porto dos Santos]

I have a scenario with many lxc created on one host. There is no shortage of resources for them (cpu, memory, disk).
But when I add one lxc and in parallel I am trying to start another I am experiencing some flaws.
When I look at the logs I can't understand what could be happening.
I noticed that constantly when I create an lxc, proxmox stops updating the information (but the service is still running).
Containers are linked and created by API in an automated manner.
proxmox version 5.3-8

 

[Chris]

I have a scenario with many lxc created on one host. There is no shortage of resources for them (cpu, memory, disk).
But when I add one lxc and in parallel I am trying to start another I am experiencing some flaws.
When I look at the logs I can't understand what could be happening.
I noticed that constantly when I create an lxc, proxmox stops updating the information (but the service is still running).
Containers are linked and created by API in an automated manner.
proxmox version 5.3-8

View attachment 13352

View attachment 13349


View attachment 13351

Hi,
this sounds like the CT times out while trying to acquire a lock. On creation PVE needs some locks to get exclusive access in order to guarantee consistency.
You could start the container in foreground mode with debug symbols in order to learn more.
Run lxc-start -n ID -F -l DEBUG -o /tmp/lxc-ID.log with the container ID of the one you want to start and check the generated debug output in the tmp file.

 

[Alex Porto dos Santos]

Hi,
this sounds like the CT times out while trying to acquire a lock. On creation PVE needs some locks to get exclusive access in order to guarantee consistency.
You could start the container in foreground mode with debug symbols in order to learn more.
Run lxc-start -n ID -F -l DEBUG -o /tmp/lxc-ID.log with the container ID of the one you want to start and check the generated debug output in the tmp file.

302/5000

I'll try.
Can you tell me when the block happens? How many simultaneous tasks can proxmox solve? Do the locks apply to all operations?
For the creation of containers simultaneously already noticed that I can only two at the same time, more than that, I have problems with lock.

 

[Chris]

302/5000

I'll try.
Can you tell me when the block happens? How many simultaneous tasks can proxmox solve? Do the locks apply to all operations?
For the creation of containers simultaneously already noticed that I can only two at the same time, more than that, I have problems with lock.

This is hard to tell since in principle most locks are e.g. VM/CT config specific and should not interfere with one another. Also this is not neccessarily the root cause, just a guess as the error states that there was a timeout. Please try to run the container with the debug flags to see where the timeout is coming from.