USM error related to maintenance_mode probe

Document ID : KB000057231
Last Modified Date : 14/02/2018
Show Technical Document Details

Symptoms


An unknown error has occurred.
Refreshing your browser may resolve the issue.

Details:
com.firehunter.ump.exceptions.DataFactoryException : Received status (4) on response (for sendRcv) for cmd = 'nametoip' name = 'maintenance_mode'

Stack Trace:
(4) not found, Received status (4) on response (for sendRcv) for cmd = 'nametoip' name = 'maintenance_mode'
at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:603)
at com.nimsoft.nimbus.NimSessionBase.getHostAndPortForName(NimSessionBase.java:423)
at com.nimsoft.nimbus.NimNamedClientSession.<init>(NimNamedClientSession.java:29)
at com.nimsoft.nimbus.NimObjectSender.connectNamed(NimObjectSender.java:77)
at com.nimsoft.nimbus.NimRequest.sendImpersonate(NimRequest.java:242)
at com.nimsoft.nimbus.pool.NimRequestPool.sendImpersonate(NimRequestPool.java:81)
at com.nimsoft.nimbus.pool.NimRequestPool.send(NimRequestPool.java:66)
at com.nimsoft.nimbus.pool.NimRequestPoolInstance.send(NimRequestPoolInstance.java:180)
at com.nimsoft.nimbus.pool.NimRequestPoolInstance.send(NimRequestPoolInstance.java:150)
at com.firehunter.umpportlet.PDSUtils.send(PDSUtils.java:21)







Solution


The maintenance_mode probe address information was missing the ump_common section in wasp probe .
This information was added back in the ump_common section in the wasp probe and the wasp probe restarted