Installing standard Python 3.9 binary on RHEL 9 at a standard or custom location
Cloudera Manager agents and Hue require Python 3.9 on RHEL 9. You must install Python 3.9.14 or higher on all cluster hosts before installing Cloudera Manager and adding services to your cluster. Follow the instructions in this topic to manually download, install, and build standard Python 3.9 binaries from source on RHEL 9 to install Python at a standard or custom location.
You must manually download, install, and build Python 3.9 from source to install Python at a custom location. You must also replace [***CUSTOM-INSTALL-PATH***] in the instructions with the custom path.
yum install gcc openssl-devel bzip2-devel libffi-devel zlib-devel -y
- SSH into the host system as a root user.
Change directory to /opt:
Download Python 3.9 as follows:
curl -O https://www.python.org/ftp/python/3.9.14/Python-3.9.14.tgz
Decompress the package as follows:
tar -zxvf Python-3.9.14.tgz
Change directory to where you decompressed the Python 3.9 package:
Install Python 3.9 as follows:
./configure --enable-sharedCustom location:
./configure --enable-shared --prefix=[***CUSTOM-INSTALL-PATH***]If you are installing Python 3.9 in any non-standard location, then you must specify the path using the
--prefixoption. You must also create a symbolic link pointing to /usr/bin or to /usr/local/bin by running the following command:
ln -s [***SOURCE***] [***DESTINATION***]For example:
ln -s [***CUSTOM-INSTALL-PATH***]/python3.9 /usr/bin/python3.9The
--enabled-sharedoption is used to build a shared library instead of a static library.
Build Python 3.9 as follows:
If you see an error such as
makecommand to compile the files:
Run the following command to put the compiled files in the default
location, or in the custom location that you specified using the
altinstallprevents you from overwriting the system Python, if any.
Copy the shared compiled library files (libpython3.9.so) to the
cp --no-clobber ./libpython3.9.so* /lib64/The
--no-clobberoption is used to prevent overwriting files.
Change the permissions of the libpython3.9.so files as follows:
chmod 755 /lib64/libpython3.9.so*
error while loading shared libraries: libpython3.9.so.1.0: cannot open shared object file: No such file or directory, then run the following command:
- Run the
Change the permission of the Python 3.9 installation directory to
755so that Hue and its related services can leverage the binary and the site packages, as follows:
chmod -R 755 /usr/local/lib/python3.9
- Enable Cloudera Manager to use Python 3.9 installed in a custom location
If you have installed Python 3.9 at a custom location, then you must either create a symbolic link using the alternatives command or by adding an environment variable to the Cloudera Manager Agent in the systemd service definition files with the full path to the Python 3.9 custom-built binary.
To use the alternatives command, get help by running the command alternatives --help. You should create symbolic links from either /usr/bin/python3.9 or /usr/local/bin/python3.9 to [***CUSTOM-INSTALL-PATH***]/bin/python3.9 where you installed the Python 3.9 package.To add an environment variable to the Cloudera Manager Agent in the systemd service definition files perform the following steps:
- SSH into the host system on which you installed Python 3.9 as a root user.
- Open the /usr/lib/systemd/system/cloudera-scm-supervisord.service file for editing.
- Add the following line in the
under the [Service]
- Open the /usr/lib/systemd/system/cloudera-scm-agent.service file for editing.
- Add the following line in the
cloudera-scm-agent.service file under
- Enable Hue to use Python 3.9 installed in a custom location
- If you have installed Python 3.9 in a custom location and you did not
configure alternatives, then you must prepend the custom path to the custom
bin directory in
separated by colon (:) as follows:
- Install the psycopg2-binary package
- Install the
psycopg2-binarypackage after installing Python 3.9 for using PostgreSQL as a backend database for Hue.