Unable to Connect to Docker#
Problem: Inability to connect to Docker could be due to several different causes.
Solution: Please check the following -
Make sure the user account running docker is part of the docker group. Test it by running the following Linux command:
id Output: uid=1000(ec2-user) gid=1000(ec2-user) groups=1000(ec2-user),4(adm),10(wheel),190(systemd-journal),**991(docker)**
Make sure that you have added the docker user to the docker group. See Adding OS user to docker group.
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.
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 (100.90.9.218)
Scale down Ranger, and Portal.
Connect to your Postgres database. For example, privacera_db.
Run the following command.
UPDATE DATABASECHANGELOGLOCK SET LOCKED=0, LOCKGRANTED=null, LOCKEDBY=null where ID=1;
Close the database connection.
Scale up Ranger.
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
./privacera_manager.sh update is running. Privacera Manager will stop running, provide a rollback, and/or a warning about leaving incomplete work.