Issues Encountered While Installing the PRA Engine

If users encounter issues during PRA installation, check to make sure your Linux distribution is supported:

  • Amazon Linux 2, Amazon Linux 2023+
  • Debian 8.x+
  • Ubuntu 18.x+
  • Redhat 7.x + (Will be deprecated by the end of 2024. Only Redhat 8+ will be supported going forward)

We also recommend that users have:

  • At least 1 GB of physical RAM
  • At least 500 MB storage

Warnings That Can Occur During Installation

  1. Unsupported operating system

    • Warning msg: "This Linux distribution or version is NOT currently supported!"

  2. Unsupported operating system "Version"

    • Warning msg: "Unsupported system version OS 6.3, required 7"

  3. Not enough physical memory

    • Warning msg: "This system has less than 1Gb, of available memory! Performance may be degraded."

  4. Not enough physical storage

    • Warning msg: "Not enough space on disk 250mgb, required 1 GB"

  5. Non-unique engine name

    • Warning msg: "The engine name "" is already in use for this site. Please enter a unique engine name."

Errors That Can Occur During Installation:

  1. User does not have root/privileged/administrator access

    • Error msg: "Super user privileges are required to install PRA ."
    • Solution: User must have root access to run the installer

  2. A previously installed version of the PRA engine has been detected

    • Error msg: "A previously installed version of PRA has been detected."
    • Solution: User must un-install the currently installed PRA engine

  3. Installation script has expired

    • Error msg: "This installation script has expired."
    • Solution: User must return to the web UI and generate a new installer script

  4. Unable to finalize installation

    • Error msg: "Unable to finalize installation with PRA registration service"

    • Solution:

      1. Check that only one user is installing using the engine name they entered. (if 2 users try to install on different servers at the same time and enter the same engine name the registration will be rejected)

  5. The engine host cannot be uniquely identified

    • Error msg: Unable to retrieve this device's unique identifier.

    • Troubleshooting:

      • Run the following command: 
      sudo cat /sys/devices/virtual/dmi/id/product_uuid
      • Check if the following error appears: No such file or directory

    • Solution:

      • This issue can occur if installing the engine in a container, which is unsupported.
      • This issue can also occur if the server configuration does not include this file, which is needed to uniquely identify a PRA engine. Please install the PRA engine on a host that is configured to ensure that this file exists.

  6. Failure while running the installer on Ubuntu hosts

    • Error msg: "chmod: cannot access '/tmp/installer': No such file or directory
    • Solution This error may appear if curl was installed with snap instead of curl. Please uninstall the curl package using sudo snap remove curl and reinstall it with sudo apt install curl.

  7. Server registration error

    • Error msg: This server is currently registered with another site.

    • Solution:

      1. Have the user check that this server has been deleted from the web UI. (If this server has had a previous PRA installation that was manually deleted and the Web UI record was NOT deleted, this error will occur).
      2. Check that this server has not been previously registered with a different tenant.

  8. The engine cannot be identified and registered in the Delinea Platform

    • Error msg: Registration error

    • Solution:

      1. This happens when the product_uuid of the Linux system was changed.

        • Check if the product_uuid was changed after restart:

          Copy 
          cat /sys/devices/virtual/dmi/id/product_uuid

        • Reinstall the engine

Uninstallation of the PRA Engine is Not Working From the Web UI.

  1. SSH into the server hosting the PRA engine
  2. Run the following CLI command as a privileged user:
- sudo /opt/delinea/updater -del

If the command above did not work as expected, please try the following commands:

  • systemctl stop clientmgr

  • rm -f /etc/systemd/system/clientmgr.service

  • rm -rf /etc/clientmgr

  • rm -f /usr/local/bin/clientmgr

  • rm -f /usr/local/bin/tunnelcl

  • rm -f /usr/local/bin/updater

  • rm -rf /opt/delinea

  • systemctl daemon-reload

Please use with caution. This is a hard reset

  1. To uninstall PRA  engines from the Web UI, see Uninstall PRA Engines.