Article ID: 115892, created on Apr 3, 2013, last review on May 8, 2014

  • Applies to:
  • Business Automation 5.4

Symptoms

A Provider wants to migrate their PBA installed on an outdated RHEL 4 server, to an RHEL 6 or CentOS 6 server. They follow the instructions in the PBA Migration Guide.

The pba_migrate script with the parameter _check _or _prepare _completes successfully. Being run with the parameter migrate, the script fails with the _PBA APP configuration failed _error message like in the example below:

+7m 13s [ DIE ] [main] PBA APP configuration failed
  [Call stack]:
 'Log::blog' at line 132
 'main::do_migrate' at line 310
 'main::main' at line 552

The Provider wants to troubleshoot the problem.

Resolution

Look at the /tmp/migrate_rh6.log file on the server where the pba_migrate script was run for possible error messages and detailed diagnostics.

The above-mentioned log file contains the specific commands that the migration script is trying to run, like in the example below:

[7m 13s] [DEBUG] [SSH::Connection] Success
[7m 13s] [INFO] [main] Check if `pba.db`(new) configs modification required on change of IP address at nodes
[7m 13s] [INFO] [main] Check if `pba.store`(new) configs modification required on change of IP address at nodes
[7m 13s] [INFO] [main] Configure Firewall
[7m 13s] [INFO] [Migration] Firewall configuration is not applicable for non-PVC destinations. Please, do it manually for `pba.app.new`.
[7m 13s] [INFO] [Migration] Firewall configuration is not applicable for non-PVC destinations. Please, do it manually for `pba.db.new`.
[7m 13s] [INFO] [Migration] Firewall configuration is not applicable for non-PVC destinations. Please, do it manually for `pba.store.new`.
[7m 13s] [INFO] [main] Run configuration scripts
[7m 13s] [INFO] [main] Configure DSN and remote DB access
[7m 13s] [DEBUG] [Migration] Get Location `pba.app.new` from repo
[7m 13s] [DEBUG] [SSH::Connection] [172.17.24.100] ssh_exec: perl -e 'use lib q|/usr/local/bm/tools|; use db; db::make_dsn();'
[7m 13s] [DEBUG] [SSH::Connection] OUT: [Mon Mar 11 10:22:15...skipped...; ERR: ; EXIT: 0
[7m 13s] [INFO] [main] Configure Apache and services startup at `pba.app.new`
[7m 13s] [DEBUG] [Migration] Get Location `pba.app.new` from repo
[7m 13s] [DEBUG] [SSH::Connection] [172.17.24.100] **ssh_exec: /usr/local/bm/tools/configure.pl --unattended &>/dev/null**
[7m 13s] [DEBUG] [SSH::Connection] OUT: ; ERR: ; EXIT: 115
[7m 13s] [DIE] [main] PBA APP configuration failed

In the log above, it may be seen that the pba_migrate script failed to run the following command on the target PBA application server (pba.app.new):

/usr/local/bm/tools/configure.pl --unattended &>/dev/null

Log in to the target PBA application server and check the log file of the configure.pl script: /usr/local/bm/tools/tools.log

Try to run the failed script manually:

cd /usr/local/bm/tools/ && ./configure.pl

Analyze the diagnostics that the script provides on the console to troubleshoot the problem.

Search Words

pba_migrate

migration failed

PBA APP configuration failed

92711db0799e8aefe8e51f12dace0496 caea8340e2d186a540518d08602aa065 198398b282069eaf2d94a6af87dcb3ff 210d017ddc3a076d22f0f865b1cf0730 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF