Search Engine: Elastic

Article ID: 128513, created on Mar 6, 2016, last review on Mar 6, 2016

  • Applies to:
  • Operations Automation 5.5


Consider the following scenario:

  • OA version is 5.5;
  • you have modified the following set of resource limits for subscription hosted on web server with legacy Apache hosting:

    Web disk space usage hard limit 
    Web disk space usage soft limit 
    Web inodes usage hard limit 
    Web inodes usage hard limit 

But new quotas were not applied to the webspace and the task "Set quota for apache user XXXXXX domain service with id XXXX webspace id XXXX" was not generated.


Such behavior is considered to be a software issue with ID POA-85855. The issue affects only webspaces running on legacy Apache hosting. Webspaces running on NG hosting are not affected.


The only workaround in this case is to manually adjust quota limit on the web server after resource limit was changed in POA.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF