Upload Catalog Item Using API is producing Timed Out Error

Products

• VMware Cloud Director

Issue/Introduction

Timed Out Error when uploading Catalog Item using API

See the following in the logs:

/opt/vmware/vcloud-director/logs/vcloud-container-debug.log.

2024-05-02 18:58:43,610 | DEBUG    | auto-pool-Monitor Service-28-thread-17 | ReceivingSocketImpl            | Resource file not fully transferred yet (0/460,989,511,769) for transfer session ########-####-####-####-######### |
2024-05-02 18:58:44,610 | DEBUG    | auto-pool-Monitor Service-28-thread-17 | ReceivingSocketImpl            | Resource file not fully transferred yet (0/460,989,511,769) for transfer session ########-####-####-####-######### |
2024-05-02 18:58:45,610 | DEBUG    | auto-pool-Monitor Service-28-thread-17 | ReceivingSocketImpl            | Resource file not fully transferred yet (0/460,989,511,769) for transfer session ########-####-####-####-######### |
2024-05-02 18:58:46,610 | DEBUG    | auto-pool-Monitor Service-28-thread-17 | ReceivingSocketImpl            | Resource file not fully transferred yet (0/460,989,511,769) for transfer session ########-####-####-####-######### |

Task fails with the Timed Out error after 30 minutes.

Cause

The transfer timeout is set too low for the amount of data being transferred.

Resolution

Essentially, during the file transfer, VCD reports that the transfer did not complete within the timeout limit defined here:

/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n transfer.session.timeToRemoveSeconds -l

We suggest increasing the value beyond the default 1800 seconds (30 minutes). The following command sets the timeout to 5400 seconds (90 minutes):

/opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n transfer.session.timeToRemoveSeconds -v 5400