No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FusionCompute V100R003C00/V100R003C10 VRM Process Failed to Connect to the Database

Publication Date:  2014-06-09 Views:  161 Downloads:  0

Issue Description

The database on the Virtualization Resource Management (VRM) node starts successfully. However, information indicating database connection failure is displayed in a VRM log, shown as follows:
Caused by: org.hibernate.exception.GenericJDBCException: Cannot open connection
at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(
at org.hibernate.exception.SQLStateConverter.convert(
at org.hibernate.exception.JDBCExceptionHelper.convert(
at org.hibernate.exception.JDBCExceptionHelper.convert(
at org.hibernate.jdbc.ConnectionManager.openConnection(
at org.hibernate.jdbc.ConnectionManager.getConnection(
at org.hibernate.jdbc.JDBCContext.connection(
at org.hibernate.transaction.JDBCTransaction.begin(
at org.hibernate.impl.SessionImpl.beginTransaction(
at org.hibernate.ejb.TransactionImpl.begin(

Notic:You can run the service postgresql status command to check whether the database is running properly.

Alarm Information


Handling Process

1. Use vi editor to add the loopback address in the /etc/hosts file. (Press Tab to separate the parameter and its value.)
2. Run the following commands to stop all processes on the VRM node:
    service notifyd stop
    service portal stop
    service vrmd stop
    service pmcd stop
    service cepd stop
    service analyzerd stop
    service fmcd stop

Root Cause

After checking the configuration file in /etc/hosts the VRM node, we found that the loopback address,, has been deleted.