Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Virtualization Manager (VMAN) > Failed to log in to the VMAN Administrator Console https://vmanserver:5480

Failed to log in to the VMAN Administrator Console https://vmanserver:5480

Table of contents

Updated December 5, 2016

Overview

The VMAN Administrator Console is inaccessible through the login screen regardless of account privilege.

Environment

VMAN version 6.x or later

Detail

Note: Double check if the two responsible services (daemons) are running.

  1. Access the VMAN appliance through SSH.
  2. Enter sudo su to switch to root level user.
  3. Enter the following command to check the status of the two involved services:
    # /etc/init.d/vami-lighttp status
    # /etc/init.d/vami-sfcbd status
  4. If either or both are resulting in none running state, perform one or both of the following commands:
    # /etc/init.d/vami-lighttp start
    # /etc/init.d/vami-sfcbd start
  5. If in case the services cannot start accordingly, analyze which part of the error is missing or required and perform a YUM command to install or repair them. 
    Example error for a vami-sfcdb that cannot run:
    /opt/vmwaresbin/vami-sfcbd: error while loading shared libraries: libssl.so.6: cannot open shared object file: no such file or directory
    The solution for this is to install libssl.so.6 to repair the missing shared object file using the following command:
    # yum install libssl.so.6
    Press Y to proceed and perform step 3 or 4 again to check the status or start the service.

 

 

Last modified
02:08, 27 Mar 2017

Tags

Classifications

Public