Search Engine: Elastic

Article ID: 122088, created on Jun 19, 2014, last review on Jul 14, 2018

  • Applies to:
  • Business Automation 5.5
  • Business Automation 5.4


There is a script that connects to database, uses a query to fetch list of accounts or orders to be notified and sends notifications by calling PBA-E API.

After PBA-E was migrated to CentOS 6 script stopped working.


  1. During migration PBA-E application and PBA-E database are decoupled (i.e. if before migration they were running on same server - after migration database will be running on a separate server). If old IP address is used in script to connect to database - it will stop working.

  2. During migration backnet and/or frontnet IP addresses of PBA-E application server (and thus of API endpoint) might get changed. If script uses old IP address to send API requests - it will stop working.

  3. If on old PBA-E server there was customized xinetd configuration file to allow PBA-E accept API requests on public IP and this configuration was not moved to new PBA-E server, clients that were sending API requests to public IP address of PBA-E server will stop working.


Check database connection IP address in script and correct it if necessary. Check /var/lib/pgsql/data/pg_hba.conf on PBA-E database server and if needed add settings to allow external host to connect to database.

Move xinetd customization file to new PBA-E server and restart xinetd to allow PBA-E to accept API requests on public IP after migration.

Check and fix IP address of API endpoint used in script.

801221f8cd76fba7300d1e6817c8e08b caea8340e2d186a540518d08602aa065 198398b282069eaf2d94a6af87dcb3ff 92711db0799e8aefe8e51f12dace0496 210d017ddc3a076d22f0f865b1cf0730 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF