We are seeing an issue with an snmpcollector probe on a remote/secondary hub - where if we click on the device profile, we get the following error:
And, the device details/components do not populate. We also see the following log in the ppm.log:
[attach_socket, ppm] Got NOT OK response, called /<folder path>/snmpcollector.get_ctd_configuration( crdta=���-,���_G7��]tF��� Jգ3a���B:���@x����@j���7����B���(�в���� �ct5�Y
And log in the snmpcollector.log includes:
[PollConfig2, snmpcollector] PollConfig : exception during update of device <> : java.lang.ArrayIndexOutOfBoundsException: 3
[PollConfig2, snmpcollector] java.lang.ArrayIndexOutOfBoundsException: 3
at com.nimsoft.nimbus.NimBase64.decode(NimBase64.java:104)
at com.nimsoft.nimbus.NimSecurity.decrypt(NimSecurity.java:243)
at com.nimsoft.nimbus.NimSecurity.decryptUTF8(NimSecurity.java:208)
at com.nimsoft.probes.network.snmpcollector.model.probe.SnmpCredentials.decrypt(SnmpCredentials.java:84)
at com.nimsoft.probes.network.snmpcollector.model.probe.SnmpV2cCredentials.getCommunityString(SnmpV2cCredentials.java:32)
at com.nimsoft.probes.network.snmpcollector.common.PolledCollectionConverter.getSNMPProfile(PolledCollectionConverter.java:128)
at com.nimsoft.probes.network.snmpcollector.common.CommonPollerUtil.getPollerDeviceID(CommonPollerUtil.java:102)
at com.nimsoft.probes.network.snmpcollector.common.CommonPollerUtil.registerPolledCollections(CommonPollerUtil.java:81)
at com.nimsoft.probes.network.snmpcollector.model.probe.PollConfigurationResolver.updatePolledCollections(PollConfigurationResolver.java:297)
at com.nimsoft.probes.network.snmpcollector.model.probe.PollConfigurationResolver$Worker.run(PollConfigurationResolver.java:360)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Release : 20.3
hub 9.31
robot 9.32
snmpcollector 4.03
We had to delete the probe on the remote hub, and then then completely deleted the snmpcollector directory on the hub and then redeployed the latest version of the snmpcollector probe. After that new profiles could be managed again.