Search Engine: Elastic

Article ID: 125064, created on Mar 31, 2015, last review on Mar 31, 2015

  • Applies to:
  • Odin Business Automation Standard 4.5


Application installation to a Container fails with the "Virtuozzo Container is locked by mutex" error.


The issue is caused by timeouts. If a task fails by timeout, it restarts itself but the Container is still locked by installation process.


To resolve the issue, please increase the LONG_TIMEOUT value in /etc/hspc/hspc.conf from default 1800 to a greater value, say, 3600 (in seconds).

With the timeout increased, the task will wait for installation to complete.

It is required to restart the hspcd service for the changes to come into force:

#service hspcd restart

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 624ca542e40215e6f1d39170d8e7ec75 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF