UIM CABI servers C drive filling up with mapdb-temp* files

book

Article ID: 129650

calendar_today

Updated On:

Products

DX Infrastructure Management NIMSOFT PROBES

Issue/Introduction

Post installation the baseline_engine throws errors and mapdb-temp* files are filling up the C:\ drive.

2019-03-18 12:48:48.660 [entsession] ERROR nimbus.NimServerSession - Exception in NimServerSessionThread.run. Closing session. 
2019-03-18 12:48:48.662 [entsession] ERROR nimbus.NimServerSession - (2) communication error, I/O error on nim session (S) com.nimsoft.nimbus.NimServerSession(Socket[addr=/10.162.xx.xx,port=48002,localport=53748]): Connection reset 
at com.nimsoft.nimbus.NimSessionBase.recv(NimSessionBase.java:944) 
at com.nimsoft.nimbus.NimServerSession.recv(NimServerSession.java:90) 
at com.nimsoft.nimbus.NimServerSession$NimServerSessionThread.handleMessage(NimServerSession.java:154) 
at com.nimsoft.nimbus.NimServerSession$NimServerSessionThread.run(NimServerSession.java:123) 
Caused by: java.net.SocketException: Connection reset 
at java.net.SocketInputStream.read(SocketInputStream.java:209) 
at java.net.SocketInputStream.read(SocketInputStream.java:141) 
at java.net.SocketInputStream.read(SocketInputStream.java:223) 
at com.nimsoft.nimbus.NimSessionBase.readNimbusHeader(NimSessionBase.java:1077) 
at com.nimsoft.nimbus.NimSessionBase.recv(NimSessionBase.java:883) 
... 3 more 

2019-03-18 12:48:59.077 [ Thread-5] ERROR impl.NimsoftApiImpl - NimSubscribe failure :(80) Session error, Unable to open a client session for 10.162.39.84:48002: Connection refused: connect 
2019-03-18 12:48:59.077 [ Thread-5] ERROR impl.NimsoftApiImpl - .........subscribe for queue failed .......... 
2019-03-18 12:48:59.078 [ Thread-5] ERROR engine.Engine - Uncaught Exception encountered: 
java.lang.NullPointerException 

at com.nimsoft.derivedmetrics.queuemessengerimpl.QueueReaderImpl.checkSubscription(QueueReaderImpl.java:300) ~[dme_core-2.5.6.jar:?] 
at com.nimsoft.derivedmetrics.queuemessengerimpl.QueueReaderImpl.run(QueueReaderImpl.java:321) ~[dme_core-2.5.6.jar:?] 
2019-03-18 12:48:59.099 [ Thread-5] ERROR engine.Engine - RuntimeException or Error encountered - initiating probe exit. 
2019-03-18 12:53:00.019 [ main] INFO engine.Engine - main() finding resouces 
2019-03-18 12:53:05.944 [ main] INFO analytics.MapDbHashSet - Not using memory mapped files for mapdb 
2019-03-18 12:53:06.381 [ main] INFO analytics.MapDbHashSet - Not using memory mapped files for mapdb 
2019-03-18 12:53:06.646 [ main] INFO always - upgrade76 previously preformed 
2019-03-18 12:53:06.662 [ main] INFO analytics.MapDbHashSet - Not using memory mapped files for mapdb

Cause

- issue post-installation, baseline_engine defect

Environment

- UIM v9.0.2
- baseline_engine v9.0.2

Resolution

First make sure the baseline_engine v9.02 probe package exists in your local archive, it should be present. 

Set loglevel to 3, and the minimum java heap for the probe to 512 from 64.

Then redeploy the probe-> Select the probe and rt-click to upgrade and just overwrite the existing baseline_engine probe. 

Check the baseline_engine log again. 

2019-03-18 15:57:57.967 [ main] INFO engine.Engine - initialization start engine = baseline_engine version = 9.02 build = 9.0.2-33 
2019-03-18 15:57:57.991 [ main] INFO nimbus.NimProbe - ****************[ Starting ]**************** 
2019-03-18 15:57:57.991 [ main] INFO nimbus.NimProbe - 9.02 
2019-03-18 15:57:57.991 [ main] INFO nimbus.NimProbe - CA Technologies 
2019-03-18 15:57:57.998 [ main] INFO nimbus.NimProbe - port=48012 
2019-03-18 15:57:58.071 [ main] INFO u76.Upgrade80 - upgrade80 previously preformed 
2019-03-18 15:57:58.072 [ main] INFO baseline.BaselineEngineImpl - Retention Period: 4 
2019-03-18 15:57:58.086 [ main] INFO calculator.DataGathererImpl - metIds are initialized 
2019-03-18 15:57:58.106 [ main] INFO nimbus.NimProbeBase - Login to NimBUS is OK 
2019-03-18 15:57:58.120 [ main] INFO baseline.BaselineConfigImpl - setLogStartUp() logLevel = 3 
2019-03-18 15:57:58.182 [ buildEx-1] INFO queuemessengerimpl.QueueReaderImpl - Queue baseline_engine.BASELINE_CONFIG is active 

Remove the mapdb-temp* files from C:\Windows\Temp.

The files should no longer be being written to the temp directory.

If the above steps do not resolve the errors:

Contact support and obtain the hotfix:  baseline_engine-9.0.2-HF2.zip 

- Deactivate the hub-robot watcher service
- Remove the hubs.sds file
- Start the robot
- Deploy the hotfix
- Check the baseline_engine log again to see if the error is alleviated.

The log should then look like this:

2019-03-19 15:11:39.484 [      main]  INFO  analytics.MapDbHashSet - Not using memory mapped files for mapdb 
2019-03-19 15:11:39.542 [      main]  INFO  engine.Engine - ******************************************** 
2019-03-19 15:11:39.542 [      main]  INFO  engine.Engine - initialization start engine = baseline_engine version = 9.02-HF2 build = 9.0.2-HF2-36 
2019-03-19 15:11:39.559 [      main]  INFO  nimbus.NimProbe - ****************[ Starting ]**************** 
2019-03-19 15:11:39.559 [      main]  INFO  nimbus.NimProbe - 9.02-HF2 
2019-03-19 15:11:40.566 [      main]  INFO  u76.Upgrade80 - upgrade80 previously preformed 
2019-03-19 15:11:40.566 [      main]  INFO  baseline.BaselineEngineImpl - Retention Period: 4 
2019-03-19 15:11:40.575 [      main]  INFO  calculator.DataGathererImpl - metIds are initialized 
2019-03-19 15:11:40.594 [      main]  INFO  baseline.BaselineConfigImpl - setLogStartUp() logLevel = 1 
2019-03-19 15:11:40.611 [- Thread-2]  INFO  queuemessengerimpl.DemartialPDSImpl - Metric runner max queue size set to : 151050