We are seeing several SAM monitors go unknown, then after anywhere from a few minutes to an hour come back up.
Anyone else seeing this behavior?
The issue was with the 3rd party set of DLL's SAM uses to SSH to linux nodes
WOD > https://www.weonlydo.com/SSH/ssh-activex-component.asp
> WeOnlyDo.Client.SSH.dll
> WeOnlyDo.Client.SSH.FIPS.dll
The issue was identified and fixed in SAM 2020.2
JIRA 00431006
SAM 2020.2 Release Notes: https://documentation.solarwinds.com/en/Success_Center/SAM/Content/Release_Notes/SAM_2020-2_release_notes.htm
rcbarr wrote:We are seeing several SAM monitors go unknown, then after anywhere from a few minutes to an hour come back up.Anyone else seeing this behavior?
rcbarr wrote:
Hi Rick, is your polling occurring successfully? What error messages are you seeing?
I see no issue with polling completion, dbsync's, or collection. I will follow up on the errors we see once I have them. Have turned on debug on different component monitors waiting to catch one that goes unknown.
We are pretty sure it is a bug. Development is evaluating it now. We provided everything, diagnostics from hosted pollers, debug logs on components IDs, eventlogs from pollers, wireshark traces, etc. Awaiting feedback.
