Search Engine: Elastic

Article ID: 116435, created on Jul 12, 2013, last review on May 9, 2014

  • Applies to:
  • Operations Automation 5.5


Certain provisioning tasks executing jobs on POA-managed Linux nodes start taking too long to complete. On the system where these tasks execute jobs, POA Agent log file (/var/log/poa.log) is rather large (several gigabytes or more) and is growing quickly.

The problem may affect usual Linux Shared Hosting services provisioning or APS tasks which involve executing operations on Linux servers, like installation, re-configuration or upgrade of APS application.


One of possible causes can be that POA Agent log level on affected Linux shared hosting server is set to the TRACE value. This causes it to fully log all requests coming from POA. On busy systems with limited I/O capacity this can result in server performance degradation.


First, check the current log level value for POA Agent on the shared hosting server that has performance issues (its IP address and/or hostname may be found in the task properties in POA Task Manager):

~# grep loglevel /usr/local/pem/etc/pleskd.props

If log level is set to 'TRACE', you can change it to one of the less verbose options. Possible values are, in decreasing order of verbosity:


If you have POA 5.2 or later, you can use the following command to change the log level of POA Agent:

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

For instance:

~# /usr/local/pem/bin/pleskd_ctl -f /usr/local/pem/etc/pleskd.props setLogLevel INFO

DEBUG [setLogLevel] ===> ENTRY
DEBUG [AA::PEM_Current::context] ===> ENTRY
DEBUG [AA::PEM_Current::context] <=== EXIT [0.000019]
DEBUG [setLogLevel] <=== EXIT [0.082263]

Make sure that the change has been applied:

~# grep loglevel /usr/local/pem/etc/pleskd.props

Change is effective immediately and does not require POA agent restart.

If you have POA 5.1 or earlier, log level of POA Agent can be changed by directly editing the loglevel parameter value in the /usr/local/pem/etc/pleskd.props file on a Linux shared hosting server followed by POA Agent restart.

Follow the steps below to change POA Agent log level.

  1. Backup the original file /usr/local/pem/etc/pleskd.props.

  2. Change the loglevel parameter in the file to the desired value from the list above, e.g. to DEBUG.

  3. Restart the POA Agent:

    ~# /etc/init.d/pem restart
    Stopping pleskd:                                           [  OK  ]
    Starting pleskd:                                           [  OK  ]

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF