Article ID: 124648, created on Feb 27, 2015, last review on Oct 22, 2015

  • Applies to:
  • Business Automation 6.0

Symptoms

After upgrade to PBA 6.0.x the list of containers missing some container that used to exist in PBA 5.x. For example:

[root@hostname ~]# /etc/init.d/pba status
Checking Stellart Service Manager:                         [RUNNING]
Checking Stellart Log Server:                              [RUNNING]
Checking Application Transaction Manager:                  [RUNNING]
Checking PBA REST CSM API Server:                          [RUNNING]
Checking Stellart Generic Worker Process:                  [RUNNING]
Checking PBA REST PCP API Server:                          [RUNNING]
Checking PBA REST UPSELL API Server:                       [RUNNING]
Checking Stellart WWW Server:                              [RUNNING]
Checking Stellart XML RPC Server:                          [RUNNING]
Checking PBA Tasks Execution Scheduler:                    [RUNNING]
Checking Parallels Business Automation:                    [RUNNING]

there is no DOMAINGATE container.

Attempt to start the "missing" container fails:

[root@hostname ~]# /etc/init.d/pba start DOMAINGATE
Starting PBA pba-core Container:                           [FAILED]
Starting PBA DOMAINGATE Container dependencies:            [FAILED]

Cause

In PBA 6.0.x there are no separate processes, no separate services for most of the containers, they work inside generic_worker process. It does not affect the functionality - if there were some APIs in this container, they are to be called in the same way as in PBA 5.x. If due to whatever reason you need to perform a restart, you will have to restart generic_worker or the whole pba.

Search Words

ingram container

gate container not starting

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328

Email subscription for changes to this article
Save as PDF