Article ID: 116741, created on Aug 13, 2013, last review on Mar 13, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 6.0
  • Operations Automation 5.5
  • Business Automation 7.0
  • Business Automation 5.5
  • Business Automation 6.0

Symptoms

As Provider I want to investigate system logs of various Odin Service Automation servers/services to find the reason of a particular problem. In order to do this I need to know where logs are located.

Resolution

Operations Automation Management Node

For OA version < 6.0

The default location of the main OA system log is:

  • OA for Linux: /var/log/poa.debug.log
  • OA for Windows: C:\Program Files (x86)\SWsoft\PEM\var\log\poa.debug.log

OA system logs are being rotated with the following names:

  • OA for Linux: poa.debug.log-YYYYMMDD.gz
  • OA for Windows: poa.debug.log-YYYYMMDD.cab

For OA version 6.0

The default location of the main OA system log is:

  • OA for Linux: /var/log/poa.log

OA system logs are being rotated with the following names:

  • OA for Linux: poa.log-YYYYMMDD.gz

For OA version 7.0

The default location of the main OA system log is:

  • OA for Linux: /var/log/pa/core.log

APSC logs

Following apsc-related logs are located in the default OA log directory on MN:

  • apsc.http.log
  • saas.http.log

Business Automation Management Node

The default location of BA system logs is:

  • BA for Linux: /usr/local/bm/log/
  • BA for Windows: C:\Program Files\Parallels\BA\log

For BA version < 6.0 the folder above contains separate logs for every single BA container, like BM.log, www.log, OPENSRS.log and so on.

Starting from BA[PBA] 6.0 the main logs are generic.log, scheduler.log, WWW.log, _amt_service.log and XMLRPCD.log, no separate logs for the containers.

Starting from BA 7.0 the main logs are renamed and relocated as follows:

BA 6.0 BA 7.0
/usr/local/bm/log/generic_worker.log /var/log/pa/billing.log
usr/local/bm/log/WWW.log /var/log/pa/billing.www.log
/usr/local/bm/log/_amt_service.log /var/log/pa/billing._amt_.log
/usr/local/bm/log/scheduler.log /var/log/pa/billing.scheduler.log
/usr/local/bm/log/XMLRPCD.log /var/log/pa/billing.xmlrpcd.log

BA logs are being rotated with the following names:

  • BA for Linux: NAME.log-YYYYMMDD.bz2
  • BA for Windows: NAME.log_YYYY-MM-DD

Please refer to KB 1931 to acquire more information about of BA log rotation configuration.


Control Panel (User Interface, UI) server

The default location of the UI server system log is:

For OSA version 6.0

  • Linux-based UI server: /var/log/poa-ui.log
  • Windows-based UI server: C:\Program Files (x86)\SWsoft\PEM\var\log\poa-ui.log

Logs of Control Panel server are being rotated daily with names like poa-ui.YYYY-MM-DD.log.

For OSA version 7.0

  • Linux-based UI server: /var/log/pa/pui/pui.log

Online Store

The default location of the Online Store server system log is:

  • Linux-based Store server: /usr/local/bm/templatestore/logs/store.log
  • Windows-based Store server: C:\Program Files\Parallels\BA\templatestore\logs\store.log

BA Update/Hotfix installation

See this article for more information.


OSA-managed shared hosting server

The default location of OSA Agent log on managed shared hosting:

  • Linux-based host: /var/log/poa.log
  • Windows-based host: C:\Program Files (x86)\SWsoft\PEM\Logs\poa.debug.log

OSA Agent logs on Windows-based hosts are being rotated with the names poa.debug.log-YYYYMMDD.cab.

Search Words

Starting PBA pba-gates Container

log location

/usr/local/bm/conf

debug log

system log

logs location

debug logs location

c0f836394088a28cc30dd0e5fe8b600e caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 198398b282069eaf2d94a6af87dcb3ff b2c3b33425dfc50c7d41a2efaa7f84f3 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328 0871c0b47b3b86ae3b1af4c2942cd0ce 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 801221f8cd76fba7300d1e6817c8e08b 92711db0799e8aefe8e51f12dace0496 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF