DX Infrastructure Manager

Expand all | Collapse all

[Thread-7, snmpcollector] DiscoveryController unable to query for devices in PENDING and FAILED states: Connections could not be acquired from the underlying database!

Jump to Best Answer
  • 1.  [Thread-7, snmpcollector] DiscoveryController unable to query for devices in PENDING and FAILED states: Connections could not be acquired from the underlying database!

    Posted 07-30-2018 12:33 PM
      |   view attached

    Hi all.

     

    I have been problems with SNMPC, in 2 occasitons the SNMPC db are corrupted.

     

    Now, the procedure it's restore the SnmpCollector.mv, but my question is that this problem is reccurrent in 2 weeks only. This behavior is not normal.

     

    I was checking the logs SNMPC and I can see this ------>

     

    Starting problem ---->

     

    Jul 29 03:01:46:420 [DiscoveryController2, snmpcollector] retry after sql exception General error: "java.lang.IllegalStateException: File corrupted in chunk 8721572, expected page length 4..768, got -775151292 [1.4.194/6]"; SQL statement:
    SELECT A0.CONFIGITEMID,A0.DEFAULTINDEXLABEL,A0.DEFAULTLABEL,A0.DEVICEID,A0.METRICFAMILYID,B0.ATTRIBUTION_ID_OID,B0.ID,B0.INTERVALVALUE,A0.SEQUENCEID,A0.SNMPINDEX,C0.ID,C0.SPEEDINOVERRIDE,C0.SPEEDOUTOVERRIDE,A0.VENDORCERTIFICATIONNAME FROM COMPONENT A0 LEFT OUTER JOIN POLLINGINTERVAL B0 ON A0.POLLINGINTERVAL_ID_OID = B0.ID LEFT OUTER JOIN SPEEDOVERRIDE C0 ON A0.SPEEDOVERRIDE_ID_OID = C0.ID WHERE A0.ID = ? [50000-194]
    Jul 29 03:01:46:439 [DiscoveryController2, snmpcollector] retry after sql exception General error: "java.lang.IllegalStateException: Reading from retry:D:/Program Files (x86)/Nimsoft/probes/network/snmpcollector/SnmpCollector.mv.db failed; file length 58308400 read length 768 at 139328001 [1.4.194/1]"; SQL statement:
    SELECT A0.CONFIGITEMID,A0.DEFAULTINDEXLABEL,A0.DEFAULTLABEL,A0.DEVICEID,A0.METRICFAMILYID,B0.ATTRIBUTION_ID_OID,B0.ID,B0.INTERVALVALUE,A0.SEQUENCEID,A0.SNMPINDEX,C0.ID,C0.SPEEDINOVERRIDE,C0.SPEEDOUTOVERRIDE,A0.VENDORCERTIFICATIONNAME FROM COMPONENT A0 LEFT OUTER JOIN POLLINGINTERVAL B0 ON A0.POLLINGINTERVAL_ID_OID = B0.ID LEFT OUTER JOIN SPEEDOVERRIDE C0 ON A0.SPEEDOVERRIDE_ID_OID = C0.ID WHERE A0.ID = ? [50000-194]

     

    Continue...

     

    Jul 29 04:01:56:133 [Thread-7, snmpcollector] DiscoveryController unable to query for devices in PENDING and FAILED states: The database has been closed [90098-194]
    Jul 29 04:11:57:174 [Thread-7, snmpcollector] DiscoveryController unable to query for devices in PENDING and FAILED states: The database has been closed [90098-194]
    Jul 29 04:21:58:213 [Thread-7, snmpcollector] DiscoveryController unable to query for devices in PENDING and FAILED states: The database has been closed [90098-194]
    Jul 29 04:31:59:241 [Thread-7, snmpcollector] DiscoveryController unable to query for devices in PENDING and FAILED states: The database has been closed [90098-194]
    Jul 29 04:42:29:420 [Thread-7, snmpcollector] DiscoveryController unable to query for devices in PENDING and FAILED states: Connections could not be acquired from the underlying database!
    Jul 29 04:52:59:570 [Thread-7, snmpcollector] DiscoveryController unable to query for devices in PENDING and FAILED states: Connections could not be acquired from the underlying database!

     

    If you need, can check the logs file attached.

     

    Why happen this?

     

    Maybe? I don't know...

    1- Two user open snmpcollector in the same time?

    2- The virtual machine where the host running (hubs: s.owindows+snmpc) consume too resource caused that SNMPC corrupted the DB? but the report of health not indicated high consume.

     

    Anyone know why happen this? my SNMPC only have "Device Inventory: 63667 components on 194 devices -- 49203 metrics enabled" the memoy is -Xms2048m -Xmx10240m, other keys enabled *DISCOVER_ALL_METRIC_FAMILIES = true, *DB_SERVER_MODE = true

     

    Best Regards.

     

    M.E

    Attachment(s)

    zip
    Logs-SNMPC.txt.zip   11K 1 version


  • 2.  Re: [Thread-7, snmpcollector] DiscoveryController unable to query for devices in PENDING and FAILED states: Connections could not be acquired from the underlying database!
    Best Answer

    Broadcom Employee
    Posted 07-30-2018 06:14 PM

    Try latest snmpcollector hotfix from the URL below.

    CA Unified Infrastructure Management Hotfix Index - CA Technologies 



  • 3.  Re: [Thread-7, snmpcollector] DiscoveryController unable to query for devices in PENDING and FAILED states: Connections could not be acquired from the underlying database!

    Posted 07-31-2018 10:40 AM

    Hi David, I didn't know of this hotfix. I will apply and evaluate the behavior.



  • 4.  Re: [Thread-7, snmpcollector] DiscoveryController unable to query for devices in PENDING and FAILED states: Connections could not be acquired from the underlying database!

    Posted 07-31-2018 02:09 PM

    Miller!

     

    After apply the new snmpcollector fix, please increase the probe memory at the cfg file.

     

    Kind Regards,

     

    Alex Yasuda
    Sr. Support Engineer



  • 5.  Re: [Thread-7, snmpcollector] DiscoveryController unable to query for devices in PENDING and FAILED states: Connections could not be acquired from the underlying database!

    Posted 07-31-2018 02:14 PM

    Yes, I already applied the hotfix. The memory are in Xms2048m -Xmx10240m.

    I am in evaluation of the behavior.

     

    thanks