Search Engine: Elastic

Article ID: 118639, created on Nov 14, 2013, last review on May 7, 2014

  • Applies to:
  • Odin Business Automation Standard 4.3


It takes very long to create a container from PBA-S, or fails with error "Server is temporarily closed for maintenance":

Top > Service Director > Virtuozzo Manager > Containers > New Container


The following records is shown in DEBUG PBA-S log (/var/log/hspc/hspc.log) when try creating new container (Top > Service Director > Virtuozzo Manager > Containers > New Container):

[2013/11/12 17:48:50] [DEBUG] [25604] [HSPC::OM::VESetupUpdate::reset_new_ve] TRACE [03]: . . -> HSPC::OM::VESetupUpdate->reset_new_ve ()
[2013/11/12 17:48:50] [DEBUG] [25604] [HSPC::MT::OM::get_allowed_hwnodes] TRACE [03]: . . -> HSPC::MT::OM->get_allowed_hwnodes (account_id=>1,is_operatable=>1)

The "Server is temporarily closed for maintenance" error appears in GUI in 120 seconds. The following error is shown in /var/log/httpd/hspc_frontend_error_log:

[Tue Nov 12 17:50:49 2013] [error] [client] proxy: error reading status line from remote server, referer: 
[Tue Nov 12 17:50:49 2013] [error] [client] proxy: Error reading from remote server returned by /hspc/pcc/02.02.16, referer:

This means that the timeout error appeared in 120 seconds after PBA-S started collecting information from registered Virtuozzo nodes (get_allowed_hwnodes).

The issue is caused by big amount of Virtuozzo nodes (several of them are outdated) and many Hosting Plans of type "Virtuozzo Container".


  1. Upgrade PBA-S to the latest available version.

  2. Verify limit VZ_HN_CONNECT_TIMEOUT in PBA-S configuration file /etc/hspc/hspc.conf according to KB article.

  3. Remove or upgrade outdated VZ nodes from PBA-S.

  4. Decrease number of active Hosting Plans of type "Virtuozzo Container" (remove unnecessary Hosting Plans).

  5. As a workaround it's recommended that you create new containers through nodes preferences (the operation is a time consuming process but it works):

    Top > Service Director > Virtuozzo Manager > Nodes > HW_NODE > Containers > New Container

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 807e9c1dc97aefd951b912a17e50c428 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF