Article ID: 114592, created on Aug 16, 2012, last review on May 29, 2015

  • Applies to:
  • Odin Business Automation Standard 4.2
  • Odin Business Automation Standard 4.1

Symptoms

A container created by Odin Business Automation Standard (OBA-S) on a Virtuozzo Containers (VC) 4.7 node fails to start with the following error:

fork() failed: Cannot allocate memory Error: Unable to start the Container. 

This occurs if the "VSwap only resource management" memory management model is enabled in the hosting plan.

Cause

Such behavior was classified as the software issue PBAS-27978 and was fixed in OBAS 4.2.2 release.

Resolution

Upgrade OBAS to the latest version.

Hotfix for OBAS 4.1.6

  1. Download these RPM packages:

    hspc-infstr-manager-4.1.6-25.swsoft.i386.rpm
    hspc-vzagent-4.1.6-25.swsoft.i386.rpm

  2. Install the hotfix on the OBAS 4.1.6 node using the following commands:

    ~# rpm -Uvh hspc-infstr-manager-4.1.6-25.swsoft.i386.rpm  
    ~# rpm -Uvh hspc-vzagent-4.1.6-25.swsoft.i386.rpm  
    ~# service hspcd restart
    

Hotfix for OBAS 4.2.1

  1. Download these RPM packages:

    hspc-infstr-manager-4.2.1-07.swsoft.i386.rpm
    hspc-vzagent-4.2.1-07.swsoft.i386.rpm

  2. Install the hotfix on the OBAS 4.2.1 node using the following commands:

    ~# rpm -Uvh hspc-infstr-manager-4.2.1-07.swsoft.i386.rpm   
    ~# rpm -Uvh hspc-vzagent-4.2.1-07.swsoft.i386.rpm  
    ~# service hspcd restart
    

Search Words

fork() failed: Cannot allocate memory Error: Unable to start the Container

62a72d260afd42b853c9105003928212 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e 93123df14254afe4bfd02eb6096092cd

Email subscription for changes to this article
Save as PDF