Skip to content

Troubleshooting Guide

Unable to Connect to Docker#

Problem: Inability to connect to Docker could be due to several different causes.

Solution: Please check the following -

  1. Make sure the user account running docker is part of the docker group. Test it by running the following Linux command:

    Output: uid=1000(ec2-user) gid=1000(ec2-user) groups=1000(ec2-user),4(adm),10(wheel),190(systemd-journal),**991(docker)**
  2. Make sure that you have added the docker user to the docker group. See Adding OS user to docker group.

  3. If steps 1 and 2 don’t solve the issue, exit the shell and log back in.

Wget command Not Found#

Problem: If you get the error such as -bash: wget: command not found then check whether wget is installed.

wget -V

Solution: Install wget using the command below.

sudo yum install wget

After successful installation, check and verify the version of wget using wget -V command.

Unable to Start the Portal Service#

Problem: Unable to start the Portal server, and it cannot start the Tomcat server. Due to this, the following log is generated:

liquibase.exception.LockException: Could not acquire change log lock. Currently locked by portal-f957f5997-jnb7v ( 


  1. Scale down Ranger, and Portal.

  2. Connect to your Postgres database. For example, privacera_db.

  3. Run the following command.

  4. Close the database connection.

  5. Scale up Ranger.

  6. Scale up Portal.

Terminate On-Going Operations#

Problem: When Privacera Manager runs, many active operations gets hang or run for extremely long times (e.g. bad connectivity to dockerhub, or enabling SSL) and user wants to cancel a run in case of termination of all active operations.

Solution: Press CTRL+C or similar interrupt key sequence while ./ update is running. Privacera Manager will stop running, provide a rollback, and/or a warning about leaving incomplete work.

Last update: July 23, 2021