I’ve just started digging into the Deadline 8 beta and am looking forward to getting the proxy system up and running. In the past, I had my EC2 machines connected via OpenVPN to the local farm to give them repository access. But during an OS upgrade on the VPN server I ran into some setup issues and I’ve fallen back to operating the EC2 farm with its own repository.
Currently, I have the local farm up and running with the Deadline 8 beta, and I have a proxy server running on a local machine on port 8090. I’m testing a single EC2 slave configured for a proxy repository and am trying to get a simple commandscript job to complete.
To keep things simpler, I’m not using SSL at the moment.
When the EC2 slave starts up, it connects to the remote repository fine (which is encouraging!) and enters an idle state. But upon picking up a job, it throws a length error from the proxy server with error messages wrapped in HTML.
I’ve attached the slave log. It’s worth noting that the local farm is Windows based and the EC2 machines are Linux. Path mapping is setup based on region.
It seems like the main error is “filename unknown”, but it’s hard to tell if it’s just a path mapping issue, or something more internal to the proxy server.
deadlineslavelog.txt (68.4 KB)