VNX M&R | ViPR SRM | Watch4Net: alerting-backend Default service will not start; apg-alerting-backend-default.out file contains "FATAL ERROR in native method" message

Products

• VMware

Issue/Introduction

Symptoms:


The Watch4Net Alerting Backend service will not start after a fresh installation.

The following error is seen in the Watch4Net apg-alerting-backend-default.out file (<BASEDIR>/APG/Backends/Alerting-Backend/Default/apg-alerting-backend-default.out):

Exception in thread "main" java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImp1.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at sun.lang.reflect.Method.invoke(Method.java:597)
 at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:325)
 at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:338)
Caused by: java.net.UnknownHostException: apg-2.smrtsupport.local: apg-2.srmtsupport.local
 at java.net.InetAddress.getLocalHost(InetAddress.java:1354)
 at com.watch4net.utils.jmx.JMXAgent.premain(Unknown Source)
 ... 6 more
FATAL ERROR in native method: processing of -javaagent failed

Environment

VMware Smart Assurance - Watch4Net/M&R

Cause

The /etc/hosts file contained incorrect information about the host. The loopback address entry must be correct and the primary IP address of the host must match with the expected hostname in Watch4Net.

Resolution

Edit the /etc/hosts file to ensure the hostnames are correct for both the loopback and the primary IP addresses.