Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

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


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


VMAN version 6.x or later


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: cannot open shared object file: no such file or directory
    The solution for this is to install to repair the missing shared object file using the following command:
    # yum install
    Press Y to proceed and perform step 3 or 4 again to check the status or start the service.



Last modified