Article ID: 119307, created on Dec 25, 2013, last review on Jan 18, 2016

  • Applies to:
  • Plesk Automation 11.1
  • Plesk Automation 11.5

Symptoms

Some actions are not listed in /var/log/poa.debug.log. How can I increase log verbosity?

Cause

Plesk Automation (PA) supports the same log levels as syslog supports, they are listed below in order of verbosity increasing:

  • ALERT
  • ERROR
  • WARNING
  • NOTICE
  • INFO
  • DEBUG
  • TRACE
  • TRACE_EXT

Log levels description is provided in the Linux manual pages for syslog. By default poa.debug.log level is set to DEBUG.

Resolution

  1. In PA 11.1 poa.debug.log verbosity can be changed with the following command:

    # /usr/local/pem/bin/pleskd_ctl -f /usr/local/pem/etc/pleskd.props setLogLevel <LOG LEVEL>
    

    e.g:

    # /usr/local/pem/bin/pleskd_ctl -f /usr/local/pem/etc/pleskd.props setLogLevel TRACE
    
  2. In PA 11.5 poa.debug.log verbosity can be changed with the list of the following actions:

    a. Open the /usr/local/pem/etc/pleskd.props file on the PA Management Node

    b. Set the 'loglevel' parameter to the desired value from the listed above:

    loglevel=TRACE
    

    c. Apply new configuration - restart pem service:

    # service pem restart
    

Search Words

log verbosity

unable to generate the web server configuration

poa.debug.log

change log level

c1ecc6010feff26cb42d1d14a7881dd6 e0aff7830fa22f92062ee4db78133079 33a70544d00d562bbc5b17762c4ed2b3 caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF