Article ID: 118139, created on Oct 23, 2013, last review on Nov 9, 2016

  • Applies to:
  • Odin Business Automation Standard

Symptoms

Virtuozzo containers are shown with "Offline" status in Virtuozzo Manager (Top > Service Director > Virtuozzo Manager > Containers). However, these containers are running on the hardware node where they reside.

Cause

  1. Odin Business Automation - Standard (OBAS) is outdated.

  2. An outdated Virtual Automation (VA) is installed on the hardware node. Verify the latest VA is installed.

    For Virtuozzo for Linux:

    [root@hw_node ~]# rpm -q pva-release
    pva-release-<OUTDATED_VERSION>
    

    For Virtuozzo for Windows:

    HW NODE: Start > Control Panel > Programs and Features 
    --->8---
    Parallels Virtuozzo Automation  <OUTDATED_VERSION>
    ---8<---
    
  3. Exceeded connection timeout - low VZ_HN_CONNECT_TIMEOUT. Try synchronizing the hardware node with OBAS:

    Top > Service Director > Virtuozzo Manager > Nodes > HW_NODE > Edit > Update (without changes)
    

    The following error shown after several minutes:

    Server is temporarily closed for maintenance
    

    Note the synchronization records in the DEBUG logs:

    /var/log/hspc/hspc.log
    --->8---
    [2013/11/06 02:10:54] [INFO] [29958] [HSPC::MT::VESrv::_find_vza_transport_obj] Get connection to VZA on Node # HW_ID, connect_type # 0
    ...
    [2013/11/06 02:10:54] [DEBUG] [29958] [HSPC::VZAgent::VZA46::HNGate::get_all_ve_info] get_all_ve_info()
    ---8<---
    
    /var/log/httpd/hspc_frontend_error_log
    ---8<---
    [Wed Nov 06 02:12:53 2013] [error] [client 91.204.25.4] (70007)The timeout specified has expired: proxy: error reading status line from remote server 127.0.0.1
    [Wed Nov 06 02:12:53 2013] [error] [client 91.204.25.4] proxy: Error reading from remote server returned by 
    --->8---
    

    Timestamps indicate that the timeout error occurred in 2 minutes (120 seconds) after starting collecting information with get_all_ve_info() - this is VZ_HN_CONNECT_TIMEOUT:

    /etc/hspc/hspc.conf
    --->8---
    VZ_HN_CONNECT_TIMEOUT = 120
    ---8<---
    
  4. vzcoll service is not running, please check it s status with the following command:

    #service vzcoll status
    

Resolution

  1. Upgrade OBAS to the latest available version.

  2. Upgrade VA to the latest version according to Virtual Automation builds, releases, and supported virtualization products.

  3. Increase the VZ_HN_CONNECT_TIMEOUT limit:

    /etc/hspc/hspc.conf
    --->8---
    VZ_HN_CONNECT_TIMEOUT = 12000
    ---8<---
    

    Remember to restart hspcd to apply the changes:

    ~# /etc/init.d/hspcd restart
    
  4. Start the vzcoll service with:

    #service vzcoll start
    

    Additional information

Virtuozzo for Windows server is marked as 'Offline' in OBAS

Search Words

container status offline

error 255 due creating container

status offline

container

containers shown offline

Constant subroutine HSPC::VZAgent::XML::OP_LIM redefined at /usr/lib/perl5/5.8.8/Exporter.pm line 65. at (eval 154766) line 1

Containers Offline

Out of Line

offline

Container has status "Destroyed"

node not available

ss

containers offline

Not available

VZ_HN_CONNECT_TIMEOUT

billing hosting

caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6

Email subscription for changes to this article
Save as PDF