library initiallization faild - unable to allocate file descriptor table - out of memory
search cancel

library initiallization faild - unable to allocate file descriptor table - out of memory

book

Article ID: 450193

calendar_today

Updated On:

Products

Easytrieve Report Generator

Issue/Introduction

When installing Easytrieve on Linux, received the following message.
Installed it on several systems, but only one received this message.

 Message : library initiallization faild - unable to allocate file descriptor table - out of memory

Environment

Release : R11.6

OS : Linux

Resolution

Possible Fix for this Problem:
Test Lowering ulimit -n Before Running the Installer
In the terminal session where the installer is executed, manually constrain the open files limit to a reasonable number (e.g., 65536 or 10240) before launching the setup script:

Bash
# Set file limit temporarily
ulimit -n 65536

# Run the Easytrieve installer again

./easytrieve_installer.sh

Additional Information

The following are recommendations for investigating the cause.

1. Inspect the Process Limits directly
Check the exact limits assigned to the process running the installer via /proc:

Bash

cat /proc/<INSTALLER_PID>/limits | grep "Max open files"

Compare this value between one of the working servers and the failing server.


2. Check Hard Limits (ulimit -Hn)
Compare both soft and hard limits across all servers:

Bash

ulimit -Sn  # Soft limit
ulimit -Hn  # Hard limit


3. Check Kernel & System Configuration Files
Verify if system-wide file descriptor configurations differ:

Kernel Parameters: sysctl fs.file-max fs.nr_open

PAM / Security limits: Check /etc/security/limits.conf and files in /etc/security/limits.d/

Systemd limits: Check /etc/systemd/system.conf (e.g., DefaultLimitNOFILE)

Please check what ulimit -Hn (hard limit) returns on the failing server versus one of the working servers, and clarify how the installer is being executed (e.g., directly as root, via sudo, or through an automated script).