You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* added faq to the aws doc
* added the link
* added some faq and updated the temp ami id
* resolved the comments, updated one of the faq along with the scriptable object update
* added one other cause raise in issues
* fixed line change
### The <Executable_Name>_Data folder hasn't been copied cover
240
+
241
+
If you've built your Linux executable, but forget to copy over the corresponding <Executable_Name>_Data folder, you will see error message like the following:
242
+
243
+
```console
244
+
Set current directory to /home/ubuntu/ml-agents/ml-agents
245
+
Found path: /home/ubuntu/ml-agents/ml-agents/3dball_linux.x86_64
246
+
no boot config - using default values
247
+
248
+
(Filename: Line: 403)
249
+
250
+
There is no data folder
251
+
```
252
+
253
+
### Unity Environment not responding
254
+
255
+
If you didn't setup X Server or hasn't launched it properly, or you didn't made your environment with external brain, or your environment somehow crashes, or you haven't `chmod +x` your Unity Environment, all of these will cause connection between Unity and Python to fail. Then you will see something like this:
256
+
257
+
```console
258
+
Logging to /home/ubuntu/.config/unity3d/<Some_Path>/Player.log
259
+
Traceback (most recent call last):
260
+
File "<stdin>", line 1, in <module>
261
+
File "/home/ubuntu/ml-agents/ml-agents/mlagents/envs/environment.py", line 63, in __init__
File "/home/ubuntu/ml-agents/ml-agents/mlagents/envs/rpc_communicator.py", line 60, in initialize
266
+
mlagents.envs.exception.UnityTimeOutException: The Unity environment took too long to respond. Make sure that :
267
+
The environment does not need user interaction to launch
268
+
The Academy and the External Brain(s) are attached to objects in the Scene
269
+
The environment and the Python interface have compatible versions.
270
+
```
271
+
272
+
It would be also really helpful to check your /home/ubuntu/.config/unity3d/<Some_Path>/Player.log to see what happens with your Unity environment.
273
+
274
+
### Could not launch X Server
275
+
276
+
When you execute:
277
+
278
+
```console
279
+
sudo /usr/bin/X :0 &
280
+
```
281
+
282
+
You might see something like:
283
+
284
+
```console
285
+
X.Org X Server 1.18.4
286
+
...
287
+
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 11 21:10:38 2018
288
+
(==) Using config file: "/etc/X11/xorg.conf"
289
+
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
290
+
(EE)
291
+
Fatal server error:
292
+
(EE) no screens found(EE)
293
+
(EE)
294
+
Please consult the The X.Org Foundation support
295
+
at http://wiki.x.org
296
+
for help.
297
+
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
298
+
(EE)
299
+
(EE) Server terminated with error (1). Closing log file.
300
+
```
301
+
302
+
And when you execute:
303
+
304
+
```console
305
+
nvidia-smi
306
+
```
307
+
308
+
You might see something like:
309
+
310
+
```console
311
+
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
312
+
```
313
+
This means the NVIDIA's driver needs to be updated. Refer to [this section](Training-on-Amazon-Web-Service.md#update-and-setup-nvidia-driver) for more information.
0 commit comments