Hello

Is anyone using SSH sensors like "Disk Free" on vCSA 6.5? Looks like none of the ssh sensors are working...

I guess the problem is OS related as PRTG does not know VMware's Photon OS?

Sensor results:

{{{Result of Sensor 35840 (SSHv2).txt [INFO][30.03.2017 08:33:29] Opening Connection [INFO][30.03.2017 08:33:29] Linux Flavor has yet to be determined [INFO][30.03.2017 08:33:29] Sending command uname [INFO][30.03.2017 08:33:29] Sending EOF [INFO][30.03.2017 08:33:29] Reading PaeSSH result [INFO][30.03.2017 08:33:29] [STDOUT] Linux

[INFO][30.03.2017 08:33:29] [STDERR] [INFO][30.03.2017 08:33:29] Uname: linux }}}

Result of Sensor 35840.Data.txt Data['CheckFlavor'].asString := '1'; Data['UsedSha2'].asString := '1'; Data['blockedsens'].asString := ''; Data['canlinux'].asString := '0'; Data['deviceid'].asString := '35588'; Data['elevation'].asString := '0'; Data['elevationkind'].asString := ''; Data['elevationname'].asString := ''; Data['elevationpass'].asString := ''; Data['fastcount'].asString := '0'; Data['host'].asString := 'IP removed'; Data['hostv6'].asString := ''; Data['inerror'].asString := '1'; Data['interfacenumber'].asString := ''; Data['inum'].asString := ''; Data['ipversion'].asString := '0'; Data['isexesensor'].asString := '0'; Data['lastmsg'].asString := '#E0 Failed to create shell'; Data['lastuptime'].asString := '0'; Data['notonpod'].asString := '0'; Data['password'].asString := '***'; Data['port'].asString := '22'; Data['privatekey'].asString := '***'; Data['reboot'].asString := '42823.3372514583'; Data['reqmsginterval'].asString := '900'; Data['resultfile'].asString := 'Result of Sensor 35840.txt'; Data['sensorid'].asString := '35840'; Data['shelltimeout'].asString := '10'; Data['simulate'].asString := '0'; Data['ssh_linuxflavor'].asString := ''; Data['sshversion_devicegroup'].asString := '2'; Data['sshversion_sensor'].asString := '0'; Data['timeout'].asString := '60'; Data['tlsexplicit_default'].asString := ''; Data['tlsexplicit_ftp'].asString := ''; Data['tlsexplicit_imap'].asString := ''; Data['tlsexplicit_pop3'].asString := ''; Data['tlsexplicit_port'].asString := ''; Data['tlsexplicit_smtp'].asString := ''; Data['uptimecount'].asString := '0'; Data['usednstime'].asString := '0'; Data['user'].asString := 'root'; Data['writeresult'].asString := '1';

Regards Marcel


Article Comments

What shell is used for that system? Does df basically work?


Mar, 2017 - Permalink

The shell is BASH, df works!


Mar, 2017 - Permalink

Are you using sudo or the compatibility mode within the linux credential section of the device?


Mar, 2017 - Permalink

- compatibility mode does not work (encrpytion algorithm failed) - Sudo works :-)

Thanks for your help!


Mar, 2017 - Permalink

Cool, you're welcome! :)


Mar, 2017 - Permalink

sudo with, without or using su does not help here - other ideas?


Feb, 2018 - Permalink

Hi,

Do you get the same error? What shell are you using (or better, the user you have configured)?


kind regards,
Stephan Linke, Tech Support Team


Feb, 2018 - Permalink

If it helps - log from a working sensor with "su" root and password on vCSA 6.5. Shell is bash:

[INFO][16.02.2018 09:54:37] Opening Connection
[INFO][16.02.2018 09:54:37] Linux Flavor was determined previously
[INFO][16.02.2018 09:54:37] Linux Flavor: Linux
[INFO][16.02.2018 09:54:37] Shell: $SHELL = /bin/bash
42900 pts/0    00:00:00 bash

[INFO][16.02.2018 09:54:37] Sending command df -TP -x tmpfs -x devtmpfs -x debugfs
[INFO][16.02.2018 09:54:38] Sending EOF
[INFO][16.02.2018 09:54:38] Reading PaeSSH result
[INFO][16.02.2018 09:54:38] [STDOUT] Filesystem                               Type 1024-blocks    Used Available Capacity Mounted on

**removed content**

[INFO][16.02.2018 09:54:38] [STDERR] 
[INFO][16.02.2018 09:54:38] Sending exit
[INFO][16.02.2018 09:54:38] Sending EOF

Feb, 2018 - Permalink

Hi Marcel,

You could give this one a shot:
Monitoring Linux Distributions Incompatible With The SSH Disk Free Sensor

You should be able to use "df -TP -x tmpfs -x devtmpfs -x debugfs" as command.


Kind regards,
Stephan Linke, Tech Support Team


Feb, 2018 - Permalink