-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UnityTimeOutException: The Unity environment took too long to respond. #59
Comments
Hi @wookayin Are you running this in a headless environment? Or does your linux system have a display? |
Hi @awjuliani I also have the same problem. I did it and set option docker_training=True and False, but still have this problem. |
It happened in a head-less mode, but previously I was able to run the environments in head-less mode if I remember correctly, and shouldn't it be the case?. I will try having display servers running. |
Hi @wookayin and @GrachevArtem In order to run Obstacle Tower on a headless Linux machine you will either need to run xvfb on that machine (and you can use our |
Hi I have the same issue here, I'm trying to run it in docker and getting same exception both with xvfb and with virtualgl.
|
One potential reason for this may be that it takes longer than 30 seconds for the Unity environment to initialize and handshake with python. Our python api comes with a |
@awjuliani I increased timeout_wait and now able to run it with xvfb, thank you! However it doesn't run with virtualgl. Seems it tries to initialize audio driver which is obviously missing on the headless server.
|
Hi @twoleggedeye, Unfortunately we don't support virtualGL right now with Unity / Obstacle Tower. If you'd like to use a GPU rendering solution, we recommend running a virtual x-server. https://github.com/Unity-Technologies/obstacle-tower-env/blob/master/examples/gcp_training.md#set-up-xserver |
@awjuliani, |
I am using obstacle tower 1.2 binary and
mlagents-envs-0.6.2
, under a Linux environment.I get the following error:
I am correctly using the obstacletower 1.2 binary, and it was a head-less mode.
Related Issue?
I checked #44 #46 but they were about Windows or before 1.2 release. I had tried out v1.0 long time ago, and I remember there was no problem at that time.
Executing the binary from the console (with strace) -- nothing follows after some system calls.
What should I check for this issue?
The text was updated successfully, but these errors were encountered: