I think the problem partly has to do with our Python3.8 installation. We did the installation via Anaconda. Cloudera recommended will use yum to install the rh-python38 on our RHEL/OL7 as I mentioned in the previous message. Documentation is here: Installing Python 3.8 standard package on RHEL 7 | CDP Private Cloud. The installation resolved most of the Web Server issue.  The Web Server issue for Impala not only has to do with Python installation but the Web Server username and password. Below is the following action performed to resolve the Impala Web Server issue after enabling the hadoop_secure_web_ui. WORK PERFORMED: Removed the below configurations from CM UI : Impala > Configuration > Catalog Server > Web Server Username   Impala > Configuration > Catalog Server > Server Web Server User Password Impala > Configuration > Impala Daemon > Web Server Username  Impala > Configuration >Impala Daemon > Web Server User Password Impala > Configuration >Statestore > Web Server Username Impala > Configuration >Statestore > Web Server User Password   Enabled "Enable Kerberos Authentication for HTTP Web-Consoles" under CM UI > Impala > Configurations   Restarted Impala Service. Also, regarding the Impala, this Cloudera documentation was quite helpful: Configuring Impala Web UI | CDP Public Cloud The issue is resolved now by following the instructions in the above documentation. ... View more

The TLS/SSL are configured correctly. Also, the krb5.conf is the same for pre-prod which is working fine. I think the problem partly has to do with our Python3.8 installation. We did the installation via Anaconda. Cloudera recommended will use yum to install the rh-python38 on our RHEL/OL7. Documentation is here: Installing Python 3.8 standard package on RHEL 7 | CDP Private Cloud Also, regarding the Impala, this Cloudera documentation was quite helpful: Configuring Impala Web UI | CDP Public Cloud The issue is resolved now by following the instructions in the above documentation.     ... View more

It seems like this issue is a special case due to how we have set up our environment. I have received a script from Cloudera support team. Our hue service is currently running fine. However, the script is only temporary. Once we upgraded, we have to use the original script. Below is the major change they've made in the hue.sh script. export PYTHONPATH=/opt/cloudera/parcels/CDH/lib/hue/build/env/lib64/python2.7/site-packages echo "print env 3st" env; ... View more