Article ID: 122063, created on Jun 18, 2014, last review on Oct 10, 2014

  • Applies to:
  • Business Automation 5.4

Symptoms

Attempts to migration PBA-E servers to CentOS 6 fails with error:

+7m 5s [INFO ] [Migration] Restoring database from dump... +8m 48s [ DIE ] [Migration] Unable to restore database on destination node

In Postgresql log file (/var/lib/pgsql/data/pg_log/postgresql-XXX.log) the following error shown:

LOG: server process (PID 859) was terminated by signal 7: Bus error LOG: terminating any other active server processes WARNING: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

Cause

Insufficient amount of shared memory exists in the container (as limited by its configuration) or on the hardware node (1/2 of the total RAM).

For more details please refer to the article #121470

Resolution

One of the following actions should be performed to fix shared memory issue:

  1. Decrease the size of shared buffers, defined in postgresql configuration(/var/lib/pgsql/data/postgresql.conf).

  2. Increase the amount of RAM, defined for the container (assuming there's available amount of shared memory on the node).
  3. Increase the amount of RAM on the hardware node.

After that migration procedure should be restarted:

  1. Remove /migration folder on container where migration script is executed.
  2. Stop and destroy new PBA-E, PBA-E database and PBA-E store containers (pba.app.new, pba.db.new and pba.store.new) that were created by migration script.
  3. Run migration script again: pba_migrate check pba_migrate prepare pba_migrate migrate

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 210d017ddc3a076d22f0f865b1cf0730 92711db0799e8aefe8e51f12dace0496 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF