Technical Support

Need help?

 

What are the installation requirements of Endpoint Protection on Linux systems?

Information applies to:

Products
Panda Adaptive Defense 360
Panda Endpoint Protection
Panda Endpoint Protection Plus

Attention!

The instructions indicated in this article apply to the traditional management platform. If your query refers to a product based on Aether Platform, please access the article on the Installation requirements of products based on Aether Platform for Linux platforms, or else, check the Knowledge Base, where you will find answers to frequently asked questions.

If you still haven't switched to Aether, please contact your sales representative or reseller and request the platform migration.

Supported distributions

Endpoint Protection supports the following operating systems:

  • Red Hat Enterprise (64-bit), version 6.0 or later
  • Debian Squeeze (32-bit and 64-bit)
  • Ubuntu (32-bit and 64-bit), version 12 or later
  • OpenSuse (32-bit and 64-bit), version 12 or later
  • Suse Enterprise Server (64-bit), version 11 SP2 or later
  • CentOS 6.x and later

Preinstallation requirements

The system must meet the following requirements for the product to work correctly:

  • The ?lsb_release? utility must be installed (on RedHat and Debian).

    This utility is used to determine the Linux distribution the installer is running on.
    • On Debian, download and install the following package:

      lsb-release_3.2-23.2squeeze1_all.deb
    • On RedHat, download and install the following package:

      redhat-lsb.i686
  • PavSL protection dependencies (all distributions).
    The PavSL protection requires the installation of the following libraries to work properly:
    • libsoup-2.4.so.1 (HTTP client/server library for GNOME)
    • libgthread-2.0
    • libmcrypt.so.4 (MCrypt - encryption functions)
    • libz.so.1 (zlib compression and decompression library)

      Make sure the /opt/PCOPAgent/PCOPScheduler/pavsl-bin/ directory contains all the ?PavSL? dependencies:

      # ldd libPskcomms.so

      On SUSE/OpenSUSE x64, use the following workaroundif there are any issues:
        • Install ligsoup-2_4-1-32bit (if it is not already installed). For example:

          # zypper install libsoup-2_4-1-32bit
        • Install libgthread-2_0-0-32bit (if it is not already installed). For example:

          # zypper install libgthread-2_0-0-32bit
        • Uninstall libmcrypt and mcrypt:

          # zypper rm libmcrypt
          # zypper rm mcrypt
        • Install ?libmcrypt-2.5.8-109.1.2.i586.rpm?. Download and install it, if it is not already installed.

On Ubuntu x64, run the following commands to install the required dependencies for the service to to work properly:

sudo dpkg --add-architecture i386
sudo apt-get update

sudo apt-get install libglib2.0-0:i386
sudo apt-get install libsoup2.4-1:i386
sudo apt-get install libmcrypt4:i386
sudo apt-get install libgssapi-krb5-2:i386

  • AT/CRON must be properly installed and enabled (in all distributions):

    Make sure the AT and CRON services are properly installed and enabled in the system services.

    Workaround for the ?ATD? service (on SUSE and openSUSE)

    Follow the steps below if the "ATD" service doesn?t start automatically on openSUSE:
    1. Edit the file /etc/sysconfig/atd

      ATD_BATCH_INTERVAL = "60"
      ATD_LOADAVG = "0.8"
    2. Edit the file /lib/systemd/system/atd.service as follows:

      # cat /lib/systemd/system/atd.service

      [Unit]
      Description=Execution Queue Daemon
      After=syslog.target

      [Service]
      Type=forking
      EnvironmentFile=-/etc/sysconfig/atd
      ExecStart=/usr/sbin/atd -b ${ATD_BATCH_INTERVAL} -l ${ATD_LOADAVG}

      [Install]
      WantedBy=multi-user.target
    3. Reload the daemon, start it, and check the service status:

      # chkconfig --add atd
      # systemctl --system daemon-reload
      # systemctl enable atd.service
      # systemctl start atd.service
      # systemctl status atd.service

      atd.service - Execution Queue Daemon
      Loaded: loaded (/lib/systemd/system/atd.service; disabled)
      Active: active (running) since Fri, 05 Oct 2012 12:14:52 -0500; 1s ago
      Process: 20851 ExecStart=/usr/sbin/atd -b ${ATD_BATCH_INTERVAL} -l ${ATD_LOADAVG} (code=exited, status=0/SUCCESS)
      Main PID: 20852 (atd)
      CGroup: name=systemd:/system/atd.service
      |_ 20852 /usr/sbin/atd -b 60 -l 0.8
    4. Reboot the computer so that it takes it into account from then on:

      # reboot
    5. After the computer finishes booting, check the service status:

      # systemctl status atd.service
  • To run the proxy server configuration script, the whiptail command must be available. On SUSE, this command is included in the newt package. Run the following command to install it:

    # zipper install newt

Related articles

Help nº- 20191015 50071 EN
ALWAYS ONLINE TO HELP YOU TWITTER FORUM
ALWAYS ONLINE TO HELP YOU TWITTER FORUM