The Aria Automation Config(RAAS) installation fails with error while loading shared libraries: libz.so.1
search cancel

The Aria Automation Config(RAAS) installation fails with error while loading shared libraries: libz.so.1

book

Article ID: 322995

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

  • Performing the RAAS installation following Migrate Aria Config from LCM Based Deployment fails with below error

    /var/lib/raas/unpack/_MEIG6PmNi/zmq/backend/cython/error.cpython-39-x86_64-linux-gnu.so
    [43861] WARNING: file already exists but should not: /var/lib/raas/unpack/_MEIG6PmNi/zmq/backend/cython/message.cpython-39-x86_64-linux-gnu.so
    [43861] WARNING: file already exists but should not: /var/lib/raas/unpack/_MEIG6PmNi/zmq/backend/cython/socket.cpython-39-x86_64-linux-gnu.so
    [43861] WARNING: file already exists but should not: /var/lib/raas/unpack/_MEIG6PmNi/zmq/backend/cython/utils.cpython-39-x86_64-linux-gnu.so
    [43861] WARNING: file already exists but should not: /var/lib/raas/unpack/_MEIG6PmNi/zmq/devices/monitoredqueue.cpython-39-x86_64-linux-gnu.so
    /usr/bin/raas: error while loading shared libraries: libz.so.1: failed to map segment from shared object

  • Checking RAAS service status returns "Active: failed"

 systemctl status raas
× raas.service - The SaltStack Enterprise API Server
  Loaded: loaded (/usr/lib/systemd/system/raas.service; disabled; preset: disabled)
  Active: failed (Result: exit-code) since Fri <DATE-TIME> AEST; 
  Duration: 3.726s
  Process: 43329 ExecStart=/usr/bin/raas (code=exited, status=127)
  Main PID: 43329 (code=exited, status=127)
  CPU: 3.241s

raas[43331]: /usr/bin/raas: error while loading shared libraries: libz.so.1: failed to map segment from sha>
systemd[1]: raas.service: Main process exited, code=exited, status=127/n/a
systemd[1]: raas.service: Failed with result 'exit-code'.
systemd[1]: raas.service: Consumed 3.241s CPU time.

Environment

VMware Aria Automation Config 8.x

Cause

The issue occurs on Linux systems when the installation path's mount (such as /tmp or /var) has the noexec flag set.

Resolution

The solution requires mounting the /tmp or /var directories with execute permission specifically for the Raas installation process.

Follow the below steps to provide executable permission for /tmp or /var.

1. SSH to the server on which the RAAS installation is performed.
2. Using the below command to display the mount point properties

    mount
   
3. If the /tmp or /var filesystem is mounted with the "noexec" option, remount it with exec permission using the following command:
   
    sudo mount /tmp -o remount,exec
  sudo mount /var -o remount,exec 

    Also update the "/etc/fstab" file entry towards "/var" to have "exec" permission.

4. Restart the RAAS installation. Migrate Aria Config from LCM Based Deployment
5. Once the installation is completed you may change the mount option to "noexec".

  sudo mount -o remount,noexec /tmp
  sudo mount -o remount,noexec /var

    Also update the "/etc/fstab" file entry towards "/var" to have "noexec".