mongodb_monitor clusters not returning any information
search cancel

mongodb_monitor clusters not returning any information

book

Article ID: 391299

calendar_today

Updated On: 03-19-2025

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

We have installed and configured the mongodb_monitor on multiple machines successfully.

We have 2 sets of clusters that will not return any information/data.

They do not use SSL and the permissions have been setup and the ID is able to reach them.

cluster nodes showing as UNKNOWN: <port>

Environment

  • DX UIM 23.4
  • mongodb_monitor v3.01
  • java 2.22

Cause

  • Unsupported mongodb database authentication mode

 

Resolution

  • mongodb authentication mechanism SCRAM-SHA-256 is NOT currently supported. Currently as of the 3.01 GA release, only SCRAM-SHA-1 is supported as well as the other options displayed below which are mentioned in the mongodb release notes.

MongoDB Release Notes

Additional Information

Mar 17 09:29:20:104 [Data Collector - MONGO, mongodb_monitor] Running [serverStatus] command on [admin] database.
Mar 17 09:29:20:110 [Data Collector - MONGO, mongodb_monitor] serverStatus for server listening on port 27506 failed. Is it shutdown?
Mar 17 09:29:20:112 [Data Collector - MONGO, mongodb_monitor] MONGO EXEC DEFAULT: mongo
Mar 17 09:29:20:113 [Data Collector - MONGO, mongodb_monitor] MongoDBProcessMgr execAndReadOneLine failed to execute command: [mongo, -version]
Mar 17 09:29:20:113 [Data Collector - MONGO, mongodb_monitor] java.io.IOException: Cannot run program "mongo": error=2, No such file or directory
    at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
    at com.nimsoft.custom.probe.MongoDBMonitor.MongoDBProcessMgr.execAndReadOneLine(MongoDBProcessMgr.java:104)
    at com.nimsoft.custom.probe.MongoDBMonitor.MongoDBProcessMgr.getProductVersion(MongoDBProcessMgr.java:71)
    at com.nimsoft.custom.probe.MongoDBMonitor.MongoDBControllerHelper.loadServerVersion(MongoDBControllerHelper.java:1150)
    at com.nimsoft.custom.probe.MongoDBMonitor.MongoDBControllerHelper.loadAll(MongoDBControllerHelper.java:676)
    at com.nimsoft.custom.probe.MongoDBMonitor.MongoDBControllerHelper.update(MongoDBControllerHelper.java:258)
    at com.nimsoft.custom.probe.MongoDBMonitor.MongoDBControllerHelper.getMongodbRuntimePropertyJSONObject(MongoDBControllerHelper.java:1179)
    at com.nimsoft.custom.probe.MongoDBMonitor.MongoDBController.handleCheck(MongoDBController.java:312)
    at com.nimsoft.custom.probe.common.MonitorProbe.Controller.handleCheck(Controller.java:259)
    at com.nimsoft.custom.probe.MongoDBMonitor.MongoDBMonitorInventory.collectMongoDBInventory(MongoDBMonitorInventory.java:74)
    at com.nimsoft.custom.probe.MongoDBMonitor.MongoDBMonitorProbe.getUpdatedInventory(MongoDBMonitorProbe.java:235)
    at com.nimsoft.probe.framework.genprobe.GenInventory.update(GenInventory.java:117)
    at com.nimsoft.probe.framework.genprobe.GenSession.updateInventory(GenSession.java:145)
    at com.nimsoft.probe.common.ctd.CtdSession.doInventoryUpdate(CtdSession.java:258)
    at com.nimsoft.probe.framework.genprobe.GenProbeDataCollector.executeSessionUpdateInventory(GenProbeDataCollector.java:59)
    at com.nimsoft.probe.common.ctd.ProbeDataCollector.execute(ProbeDataCollector.java:218)
    at com.nimsoft.probe.framework.genprobe.GenProbeDataCollector.execute(GenProbeDataCollector.java:36)
    at com.nimsoft.vm.collector.DataCollector.run(DataCollector.java:151)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:750)
Caused by: java.io.IOException: error=2, No such file or directory
    at java.lang.UNIXProcess.forkAndExec(Native Method)
    at java.lang.UNIXProcess.<init>(UNIXProcess.java:247)
    at java.lang.ProcessImpl.start(ProcessImpl.java:134)
    at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
    ... 24 more
 
Mar 17 09:29:20:113 [Data Collector - MONGO, mongodb_monitor] Mongo version line: null
Mar 17 09:29:20:113 [Data Collector - MONGO, mongodb_monitor] Mongo version detected: null
Mar 17 09:29:20:113 [Data Collector - MONGO, mongodb_monitor] Sending NimAlarm: {"severity":2,"subsystem":"mongodb_monitor","source":"<hostname.example>.com","message":"MongoDB instance [UNKNOWN:27506] is not running on this node."}