TLS2.0 Key (username)=(admin) already exists issue

[Lin__Joey]

Dear EIS Team,

The error log attached appears after running ./setup_TLS_docker.sh 

Please provide your expertise. Thanks in advance,

Best regards,

Joey

[JesusE_Intel]

Hi Joey,

Thanks for reaching out, the DETAIL: Key (username)=(admin) already exists is alerting that the user name exists, likely the command was previously executed.

However, the issue indicates there is already a docker container with the device /opt/intel/openvino.

ERROR: Configuration for volume openvino specifies "device" driver_opt None, but a volume with the same name uses a different "device" driver_opt (/opt/intel/openvino). If you wish to use the new configuration, please remove the existing volume "training-and-learning-suite_openvino" first:

If possible, please try to clean the docker containers and re-run the setup_TLS_docker.sh script. Please note this will completely remove the docker contains and they will be re-downloaded.

cd <TLS_repo>/thirdparty

sudo ./cleanup_docker.sh

sudo ./cleanup.sh

Regards,

Jesus

[Lin__Joey]

I tried it with no luck with error log attached. Does that mean the keys stores somewhere else in the system? The error appeared after I failed to restart TLS docker.  It baffles me for the correct procedure to restart the TLS server.  Do you have any other suggestion?

Thanks a lot,

Joey

[WengWai_C_Intel · Accepted solution]

Hi @Lin__Joey

For the key already exists message, basically it will not cause any issue and from your logfile we can see the 5 cvat related containers (cvat,  nginx, cvat_cvat_ui, redis and postgres) already up running. In order to have a clean rebuild, below are some suggestions for you to re-run the setup:

1) Go to path <TLS_repo>/webservices/components/cvat directory, run the command below:

     sudo docker-compose down

2) Go to path <TLS_repo>/ directory, run the command below:

    sudo docker-compose down

3) Run the command below to remove the directories:

    sudo rm -r /opt/intel/tls

4) Go to path <TLS_repo>/thirdparty directory, run command below:

    sudo ./cleanup_docker.sh

5) Finally, in the same directory, run the setup script again without sudo.

     ./setup_TLS_docker.sh

Let me know if you can rebuild the system and running. 

Thanks!

[JesusE_Intel]

If you need any additional information, please submit a new question as this thread will no longer be monitored.