To know more about an error, download a
.txt file with server logs. Click the user icon in the upper-right corner to see the User Panel, then click Download Log:
Use the logs to investigate problems and manually run tools to debug the problem by entering the Docker* container. For more information, go to the Enter Docker Container section of the Work with Docker Container page.
Remote profiling issues:
This error appears due to the incorrect permissions that are set for the configuration folder on a host machine with Linux* or macOS*.
The indicator of the problem is the following output in the terminal:
To resolve the problem, follow the steps below:
NOTE: If the configuration folder already exists, delete it before proceeding.
-ASSETS_DIRargument in the script you used to install the application.
NOTE: If you use a non-default configuration directory, replace
NOTE: Creating the directory with the
-m 777mode makes the directory accessible to ALL users for reading, writing and executing.
This error appears due to model and dataset type incompatibility.
Also, check that you do not select a VOC Object-Detection dataset for a Classification model, or an ImageNet Classification dataset for an Object-Detection model.
If you cannot import models from the Open Model Zoo, you may need to specify your proxy settings when running a Docker container. For details, refer to Install from Docker Hub*.
The error shown below may appear due to incorrect user permissions set for an SSL key and/or SSL certificate.
Check the key and certificate permissions. They must have at least **4 mode, which means reading for
To resolve the problem, run the command below in your terminal and then restart the DL Workbench.
NOTE: The command makes the provided files accessible for reading to all users.
If the specified user has no sudo privileges on the remote machine, only a CPU device is available for inference. If you want to profile on GPU and MYRIAD devices, follow the steps described in the Configure Sudo Privileges without Password section of Set Up Target for Remote Profiling.
If the automatic setup of GPU drivers fails, install dependencies on the remote target machine manually as described in the Install Dependencies on Remote Target Manually section of Set Up Target for Remote Profiling.
Check the user name for the SSH connection to the remote machine.
This failure means you uploaded the key with the correct structure, yet the key does not match with the key you use for your machine. Make sure you upload the
id_rsa key generated when you set upthe target for remote profiling".
You should upload the `id_rsa` key, which contains a set of symbols surrounded by the lines shown below:
Make sure you have Python* 3.5, 3.6, 3.7, or 3.8 on your target machine. See Set Up Target for Remote Profiling for dependencies instructions and the full list of remote target requirements.
Make sure you have pip* 18 on your target machine. See Set Up Target for Remote Profiling for dependencies instructions and the full list of remote target requirements.
Make sure you have Ubuntu* 18.04 on your target machine. See Set Up Target for Remote Profiling for the full list of remote target requirements.
This failure may occur due to incorrectly set or missing proxy settings. Set the proxies as described in Register Remote Target in the DL Workbench. To update remote machine information, see Profile with Remote Machine