Deadline Asset server not uploading VDBs to S3 to render using an EC2

Hi,

We are currently facing an issue with Deadline, when using Portal Link and the Asset Server that comes with it, we are rendering multiple jobs on EC2 but those that have vdbs are not working, we are getting this error

2024-12-17 06:48:29: 0: STDOUT: 00:00:02 194MB WARNING | [volume] IoError: could not open file /mnt/Data/Yprojects382c1f5b518e9b00988cd8fdd65602ce/rhw/101/vfa/0940/lgt_main/default/work/houdini/cloud_sim_0/cloud_sim_0.1098.vdb (No such device)

The paths are swap at least that is what we read above, so we are thinking that the issue is that VDBs are not being uploaded.

Thank you for any advice that can be provided.

Our local system runs on Windows with Deadline 10.2.0.10

I would first check the AWSPortalLink and AWSPortalAssetServer logs (ProgramData\Thinkbox..) to see if they are getting picked up and uploaded (the slow part).

Not familiar with Houdini cloud rendering, but if you haven’t already, I would try something simple (with at least a texture file) just to make sure the basics are ok. I remember back in the day we would export rsproxies from Houdini and import those into Maya for cloud rendering. We had to be wary of how external files (images and openvdb) were referenced in those rsproxy files or else they weren’t uploaded by AWS Portal.

Another Asset Server issue was it ran with elevated privileges that did not have the network drive mounted. Using UNC paths as Asset Server Root Dirs and for all file paths in scenes, but you can also mount the network drive as admin.

Haven’t required cloud rendering for years though, so it’s probably a lot more seamless these days for people to spend big bucks on EC2.