Hi all,
Specifically for one of the nodes in the cluster the /storage/content call as such (https://domain.tld:8006/api2/json/nodes/node-1/storage/local/content is not working. In the pveproxy log it returns a "596" error, which seems to indicate a "resource unavailable" error . Other API calls for this node are working fine, including the various /storage/ calls. When executing
This also works fine, albeit with somewhat of a delay, with the "time" command prefix:
For the other node, with similar spec, the pvesh /storage/content call comes back in 13 seconds. There are definitely more VM's active on node-1 but looking at read/write behaviour it's not immediatly obvious why the difference should be so large.
My guess is that because the content call on node-1 goes over 30 seconds it may hit some type of time-out when going through the pveproxy / API. Can anyone confirm that this is the case? Is there also a way to change such a timeout setting?
We are running 7.4.-16.
Specifically for one of the nodes in the cluster the /storage/content call as such (https://domain.tld:8006/api2/json/nodes/node-1/storage/local/content is not working. In the pveproxy log it returns a "596" error, which seems to indicate a "resource unavailable" error . Other API calls for this node are working fine, including the various /storage/ calls. When executing
Code:
pvesh get /nodes/node-1/storage/local/content
Code:
real 0m35.039s
user 0m17.313s
sys 0m18.277s
For the other node, with similar spec, the pvesh /storage/content call comes back in 13 seconds. There are definitely more VM's active on node-1 but looking at read/write behaviour it's not immediatly obvious why the difference should be so large.
My guess is that because the content call on node-1 goes over 30 seconds it may hit some type of time-out when going through the pveproxy / API. Can anyone confirm that this is the case? Is there also a way to change such a timeout setting?
We are running 7.4.-16.