Search Engine: Elastic

Article ID: 117641, created on Oct 1, 2013, last review on Jul 14, 2018

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


Is it OK to enable SELinux on a PBA-E server or store server?


No, SELinux mode must be set to "permissive," as the "enforcing" mode causes various issues, such as update installation failure, problems with API call execution, store synchronization problems, PBA node registration in POA in PA 6.0 etc.

It is also mentioned in the deployment documentation:

To disable SELinux, you may follow the instructions from the article

List of possible errors from enabled SELinux:

  • PBA-E services are running, but the login page is not displayed, www.log does not show any records, and there are permission errors in the Apache error log.

  • API method execution fails with this error:

    "System Error. Object is not available inside a server"
  • The "" script fails:

    [DATE] Execute: '/etc/init.d/postgresql initdb'
    Initializing database: chown: invalid user: `postgres:postgres'
    [DATE] [Call stack]:
    [DATE]     'helper::msystemex' at line 574
    [DATE]     'helper::msystem' at /usr/local/bm/tools-db/ line 585
    [DATE]     'main::postgres_operate' at /usr/local/bm/tools-db/ line 96
    [DATE] PWD: /usr/local/bm/tools-db
    Command '/etc/init.d/postgresql initdb' exited with error code 256 at line 576.
  • Store synchronization fails:

    "Synchronization failed with error: Couldn't open counter file. "
  • The store is not displayed; an error mentioned above is displayed instead, even though the "templatestore" folder owner and permissions are correct.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 801221f8cd76fba7300d1e6817c8e08b 92711db0799e8aefe8e51f12dace0496 210d017ddc3a076d22f0f865b1cf0730 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF