Search Engine: Elastic

Article ID: 129238, created on Aug 10, 2016, last review on Jan 1, 2018

  • Applies to:
  • Operations Automation


After installation of OA Update 8, OACI VE console is not working for all virtual environments on a specific Virtuozzo host.

The console shows the message:

Session Closed. Please click on Reset Console


With Update 8, VE console was switched from Java applet to HTML5 based console utilizing HTTP web sockets with Branding host proxying connections to Virtuozzo node. After the update installation, a configuration script is called to created the required proxy rules. Due to various reasons, the configuration may not become available afterwards.


The check-list below will help to validate the VE console configuration:

  1. Each host that contains a brand should have the following configuration files in place:

    # cat /etc/httpd/conf.d/oaci.conf
    SSLProxyEngine On
    ProxyVia Off
    ProxyRequests Off
    Order allow,deny
    Allow from all
    Header set X-Forwarded-Proto https ProxyPass "/oaciws/22" "ws://" ProxyPass "/oaciws/23" "ws://"

    The bottom lines are formed with the help of backnet IP addresses of the Virtuozzo hardware nodes.

    The configuration file should be included into the Apache configuration tree:

    # grep oaci.conf /etc/httpd/conf/httpd.conf
    Include conf.d/oaci.conf
  2. Each Virtuozzo host should have Apache configuration file /etc/httpd/conf.d/oaci.conf, describing OACI virtual host that should be located at /var/www/oaci. The virtual host includes a single .htaccess file to forward the incoming requests to web sockets.

    # cat /var/www/oaci/html/.htaccess
    RewriteEngine on
    RewriteRule ^websocket/([^/]+) ws://$1/websockify [P]
    RewriteRule ^oaciws/([^/]+)/([^/]+) ws://$2/websockify [P]
  3. All Branding and Virtuozzo hosts should have mod_proxy_wstunnel RPM package installed, with additional Apache configuration file to load the module:

    # cat /etc/httpd/conf.d/proxy_wstunnel.conf
    LoadModule proxy_wstunnel_module modules/

    Note: RedHat7/CentOS7 have mod_proxy_wstunnel shipped with httpd by default. RPM package mod_proxy_wstunnel is not required on servers with RedHat7/CentOS7.

  4. The request to access VE console arrives at the Branding host, which is proxied to the web sockets running on Virtuozzo hosts. Connectivity between Branding and Virtuozzo on port 80 is required to make this work.

Log files to check for possible errors:

  1. Apache service should be running on all Virtuozzo and Branding nodes:

    # service httpd status

In order to re-run the OACI console configuration scripts:

  • on the Management Node:

    1. Find the location of script
      • For 7.0: it is included into the main distributive package at oa-7.0-9781/upgrade/post/
      • For 6.0.8: the script arrives with updates at /usr/local/pem/var/updates/poa-6.0-3517_update08/upgrade/post/
    2. Run the script: # python
  • on each Virtuozzo node:

    # prlsrvctl set --vnc-public-key "" --vnc-private-key ""
    # python /usr/lib64/httpd/modules/mod_rewrite_ws/

    where is the backnet IP address of the Virtuozzo node

To find the spot, when configuration scripts should have been applied:

  • on a Virtuozzo host:

    # zgrep /var/log/poa.log*
  • on MN 7.0:

    # grep update-branding-nodes-with-websockets /var/log/pa/update*
  • on MN 6.0:

    # grep update-branding-nodes-with-websockets /usr/local/pem/var/log/pa_updates_installer/*

Scripts execution on Virtuozzo nodes happens in scope of paci_hn_psbm PPM installation:

oss=> select task_id,name,finished from tm_logs where name like '%paci_hn_psbm%';
 task_id |                         name             |        finished
  339913 | Install paci_hn_psbm to | 2016-08-09 11:42:58+03
  339914 | Install paci_hn_psbm to | 2016-08-09 11:56:32+03

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF