I am running SItescope 11.20 on a Linux server, monitoring ~70 Solarisservers running Solaris 10 (x86).
In our setup, we use ssh to connect and run the monitors.
One of the problems we have with Sitescope, is that sometimes it fails to get data for basic monitors like the CPU monitor or the Memory monitor, resulting in a "no data" failure.
When I investigate the connection, there is never anything wrong.
A manual ssh session works perfectly from the Linuxserver that SiteScope is running on to the monitored server.
( I have tuned the ssh timeout to 180s as was recomended in a previous post).
When the problem occurs, I cannot make it go away by re-running the monitor (I am not sure if it actually runs the monitor again. It seems to finish very quickly). Sometimes I have been succesful after a restart of SiS, but this seems like overkill.
When I jave this problem with for instance the CPU monitor, other monitors are working fine.
One suspicion that I have is if ssh "Message Of The Day" (motd) could have an impact on some monitors?
We use a motd for legal reasons that is echoed to all (interactive) ssh connections and I am not sure
if the motd output is messing up the data parsing for some monitors.
Any suggestions on what could cause this behaviour or how to troubleshoot it?