We have finaly decided to upgrade to 64bits NMS system-enviroment. We ccome from 6.20
We use 3 seperate servers for the main taks. nms, database and ump. NMS and databse is running ok, so it looks, but ump server will not start he wasp probe. It comes withe several error messages:
jul 31 13:07:07:252 WARN [pool-1-thread-1, com.nimsoft.nimbus.probe.service.wasp.udm.UDM] Unable to initialize data update from dashboard_engine.
jul 31 13:07:07:252 WARN [pool-1-thread-1, com.nimsoft.nimbus.probe.service.wasp.udm.UDM] (7) temporarily out of resources, Received status (7) on response (for sendRcv) for cmd = 'InitializeDataUpdate'
jul 31 13:06:03:094 ERROR [Callback_initializeDataUpdate-410, Utilities:89] Error occurred during probe status verification: Probe Name = /eRemote/CentralHub/ump-webserver/wasp Error: (4) not found, Received status (4) on response (for sendRcv) for cmd = 'nametoip' name = '/eRemote/CentralHub/ump-webserver/wasp'
All system have a minimal resource 2 cores and 8gbyte of memory. Java is set toL min1024, max4048, that should be enough I think.
As I look in the probe list on our NMS server there is no varaiable_server running. As I understand it is deprectiated. Why is the dashboard_engine on the UMP server aksing for a varaiable_server.
Does anyone have a tip or clue for me why Wasp does not start?