Search Engine: Elastic

Article ID: 8335, created on Mar 30, 2010, last review on Jul 14, 2018

  • Applies to:
  • Odin Business Automation Standard


OBAS logs do not have any useful information for troubleshooting issues. How can I increase the verbosity of OBAS logs?


The Provider may manage the log verbosity level in OBAS PCC at

Top > Configuration Director > Logging and Errors > Log Settings

To change the log verbosity level, go to this screen, click the Edit button, select the needed level (DEBUG, INFO, WARN, ERROR, or FATAL), and click Update.

It is not necessary to restart any part of OBAS services for the changes to take effect.

The recommended log level is DEBUG; only this level allows you to properly investigate problems that occurred in the past.

It also is recommended to enable all available options on the Log Settings screen, namely the following:

    Enable SQL Log in Problem Reports
    Enable Debug Log in Problem Reports
    Enable Extended Problem Reports

Please note that with the DEBUG level, OBAS will write a great deal of data to the main log file, /var/log/hspc/hspc.log, so you must ensure that log rotation is configured properly on the OBAS server to prevent disk space from being filled with logs.

OBAS does not provide any custom log rotation tools; the usual Linux system package, logrotate, is used. You simply need to make sure OBAS log files are present in the logrotate configuration with the needed parameters (number of rotated logs to keep, compression parameters, etc.). It is recommended to keep logs for the last 10-14 days so problems that occurred in the past can be investigated.

Refer to the KnowledgeBase article OBAS logrotation for more details.

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF