Search Engine: Elastic

Article ID: 121401, created on Apr 30, 2014, last review on May 9, 2014

  • Applies to:
  • Plesk Automation 11.5


During the installation of PPA Billing node the task 'Prepare node 'billing.domain.tld' to PA agent installation' failed with the following error:

Command 'TERM=xterm-256color perl --level=1 --ip="" --communication-ip=""' execution failed with following error:
'The following error occurred on attempt to install PBA: Failed execute configuration script 'tools-db/': Command '/etc/init.d/postgresql start' exited with error code 256 at line 588.

For details please refer to log file 'ppa_billing_install.log'.
Once the root of the problem will be solved you may reschedule task execution.'
Check logs in '/root/c/POA_Deploy' at host '' for more details about the reasons of failure.

In the '/var/lib/pgsql/pgstartup.log' file you could find the following error:

FATAL:  could not create shared memory segment: Cannot allocate memory
DETAIL:  Failed system call was shmget(key=5432001, size=630439936, 03600).
HINT:  This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory or swap space, or exceeded your kernel's SHMALL parameter.  You can either reduce the request size or reconfigure the kernel with larger SHMALL.  To reduce the request size (currently 630439936 bytes), reduce PostgreSQL's shared_buffers parameter (currently 65536) and/or its max_connections parameter (currently 504).
    The PostgreSQL documentation contains more information about shared memory configuration.


By some reasons PostgreSQL was not gracefully stopped so some shared memory was still allocated for PostgreSQL


Find shared memory blocks marked as used by 'postgresql' user by using ipcs utility, then free up these memory blocks. You may use the following script to speedup the process:

ipcs | grep postgres | awk '{print $1}' | while read i; do ipcrm -S $i; done

Afterwards try to start and stop postgresql daemon.

service postgresql start
service postgresql stop

If that was successful then restart the failed task in PPA.

33a70544d00d562bbc5b17762c4ed2b3 e0aff7830fa22f92062ee4db78133079 caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF