Article ID: 126242, created on Jul 18, 2015, last review on Jul 18, 2015

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

OBAS system is rather slow and most tasks execution fails with the standard maintenance page, ie. when trying to resolve Plesk domain conflicts when you click on a domain it takes a lot of time and results in OBAS showing the error page.

OBAS node is running on 64-bit OS and the MySQL instance has been moved to a separate node. CPU load is normal and also vmstat output does not show any particular load or memory issue.

# tail -f /var/log/hspcd/error_log

[Sun Nov  2 18:52:21 2014] [error] (12)Cannot allocate memory: fork: Unable to fork new process
[Sun Nov  2 18:52:31 2014] [error] (12)Cannot allocate memory: fork: Unable to fork new process

Cause

OBAS container memory is insufficient.

Resolution

Increase SWAP memory of the OBAS container by running the following command on the Virtuozzo node where the contianer is located:

# vzctl set CTID --save --ram 4G --swap 4G

where CTID is the OBAS container number.

Search Words

OBAS slow

maintenance page

Cannot allocate memory: fork: Unable to fork new process

624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF