Known Issues and Workarounds in Cloudera Navigator Encrypt

Using screen utility with Cloudera Navigator Encrypt does not work

Running Cloudera Navigator Encrypt commands within the Linux screen utility does not work correctly.

Workaround: None.

Warning messages appear during Navigator Encrypt installation on SLES

The following warning messages appear during Navigator Encrypt installation on SLES:

warning: user ec2-user does not exist - using root
warning: user ec2-user does not exist - using root
warning: user ec2-user does not exist - using root

Workaround: None. These messages can be safely ignored.

The navencrypt exec command does not work

Using navencrypt exec to run a single command without having a matching ACL rule does not work.

Workaround: Add a temporary ACL rule to allow the command you want to use.

Sophos antivirus is not compatible with Cloudera Navigator Encrypt

Kernel panics have been observed on machines running both Sophos antivirus and Cloudera Navigator Encrypt.

Workaround: None. Do not use Sophos antivirus in conjunction with Cloudera Navigator Encrypt.

Cloudera Navigator Encrypt crashes in Docker container

Cloudera Navigator Encrypt crashes when run in a Docker container.

Workaround: None. Do not use Cloudera Navigator Encrypt with Docker.