Discovery Server issues

Document ID : KB000034005
Last Modified Date : 14/02/2018
Show Technical Document Details
Select the discovery_server probe.

Hold down the SHIFT key then rt-click to select Raw Configure.

Select startup->opt section.

See startup->options java min and max. Set them to at least 2048 and 4096 respectively and cold start the discovery_server.

<startup>
?? <opt>
????? java_mem_init = -Xms2048m
????? java_mem_max = -Xmx4096m
????? java_opts = -server -XX:ErrorFile=./hs_err_pid.log
?? </opt>
</startup>

User-added image

Also make sure the correlation settings are set to true, especially for vm_id and robot_device_id.

?? <vm_id>
????? enabled = true
?? </vm_id>
?? <robot_device_id>
????? enabled = true
?? </robot_device_id>

User-added image

Then click Ok.

Cold start the discovery_server probe:
(Deactivate, then Activate it

Check the log for any errors.

Note that having the memory too low can cause this error and other issues such as:

- discovery or node count inaccuracy in USM
- discovery _server slowness / performance issues

keywords: WARN com.nimsoft.discovery.server.probe.ProbeInitializer - Waiting initialize UDM. Retrying java.lang.IllegalArgumentException db.error/not-enough-memory datomic.objectCacheMax datomic.memoryIndexMax exceeds 75% JVM RAM node count off not accurate discover systems robots nodes inaccurate

?