What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Failed to connect. Please check the SSH log of the target device or try the Compatibility Mode of th

Votes:

0

After updating multiple Sophos Firewalls to Version 9.403 the SSH Sensors aren't working anymore. (Sophos Change log: NUTM-3813 [Basesystem] Remove SSH weak algorithms)

The SSH Sensor shows "Failed to connect. Please check the SSH log of the target device or try the Compatibility Mode of the sensor's SSH engine ande target s consider updating thystem's operating system. Reason: ssh_connect failed"

The SSH Log on the Firewall says: "fatal: no matching mac found:..."

PRTG is up to date and also tried the Compatibility Mode.

firewall prtg sophos ssh

Created on Feb 27, 2017 10:22:44 AM



7 Replies

Votes:

0

Hi there,

If you enable the "SSH Compatibility Mode", what error message do you get then? What is shown in the log of the device? Are you able to login manually (e.g. via Putty) on the target device via SSH?

Best regards.

Created on Feb 28, 2017 11:51:22 AM by  Dariusz Gorka [Paessler Support]



Votes:

0

On SSH Compatibility Mode the Sensor shows "Das Hostsystem kann PRTG's Befehl nicht verarbeiten: "". (Code: PE096)".

Login with Putty is working fine.

Created on Mar 1, 2017 1:16:18 PM



Votes:

0

Hi,

Please activate the "Write sensor result to disk (Filename: "Result of Sensor [ID].txt")" option in the sensor settings and provide us the sensor logs, they are located on the PRTG Core Server or the remote probe under "C:\ProgramData\Paessler\PRTG Network Monitor\Logs(Sensors)".

Created on Mar 1, 2017 1:32:52 PM by  Dariusz Gorka [Paessler Support]



Votes:

0

The logs say: 0.06 0.12 0.13 1/287 4855

Created on Mar 14, 2017 8:07:59 AM



Votes:

0

Hi there,

From what sensors did you got this result? Is this the whole log as there have to be at least two files in the folder?

Created on Mar 14, 2017 10:10:55 AM by  Dariusz Gorka [Paessler Support]



Votes:

0

Its from the sshloadavgsensor Sensor.

there is a second log Result of Sensor 17828.Data.txt

Data['CheckFlavor'].asString := '1';
Data['DoNotCheckShell'].asString := '';
Data['UsedSha2'].asString := '1';
Data['blockedsens'].asString := '';
Data['canlinux'].asString := '0';
Data['checkfailed'].asString := '0';
Data['command'].asString := 'cat /proc/loadavg';
Data['deviceid'].asString := '14257';
Data['elevation'].asString := '0';
Data['elevationkind'].asString := '';
Data['elevationname'].asString := '';
Data['elevationpass'].asString := '';
Data['fastcount'].asString := '0';
Data['host'].asString := '';
Data['hostv6'].asString := '';
Data['inerror'].asString := '0';
Data['interfacenumber'].asString := '';
Data['inum'].asString := '';
Data['ipversion'].asString := '0';
Data['isexesensor'].asString := '0';
Data['lastmsg'].asString := '#P1';
Data['lastuptime'].asString := '0';
Data['notonpod'].asString := '0';
Data['password'].asString := '***';
Data['port'].asString := '22';
Data['privatekey'].asString := '***';
Data['reboot'].asString := '42795.5297218866';
Data['reqmsginterval'].asString := '60';
Data['resultfile'].asString := 'Result of Sensor 17828.txt';
Data['sensorid'].asString := '17828';
Data['shelltimeout'].asString := '10';
Data['simulate'].asString := '0';
Data['ssh_linuxflavor'].asString := '0';
Data['ssh_linuxshell'].asString := '$SHELL = /bin/bash
 1601 ?        00:00:00 bash

';
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 := 'loginuser';
Data['writeresult'].asString := '1';

And a third "....17828 (SSHv2).txt"

[INFO][14.03.2017 07:55:08] Opening Connection
[INFO][14.03.2017 07:55:08] Linux Flavor was determined previously
[INFO][14.03.2017 07:55:08] Linux Flavor: Linux
[INFO][14.03.2017 07:55:08] Shell: $SHELL = /bin/bash
 1601 ?        00:00:00 bash


[INFO][14.03.2017 07:55:08] Sending command cat /proc/loadavg
[INFO][14.03.2017 07:55:08] Sending EOF
[INFO][14.03.2017 07:55:08] Reading PaeSSH result
[INFO][14.03.2017 07:55:08] [STDOUT] 0.06 0.12 0.13 1/287 4855


[INFO][14.03.2017 07:55:08] [STDERR] 
[INFO][14.03.2017 07:55:08] Sending exit
[INFO][14.03.2017 07:55:08] Sending EOF

Created on Mar 14, 2017 11:34:22 AM

Last change on Mar 14, 2017 12:29:31 PM by  Dariusz Gorka [Paessler Support]



Votes:

0

Hi there,

Thanks for the logs. The issue still remains and the error message is still(?):

"Das Hostsystem kann PRTG's Befehl nicht verarbeiten: "". (Code: PE096)".

If so, then please add the Load Average sensor anew as the result "0.06 0.12 0.13 1/287 4855" is actually okay. Does this work?

Best regards.

Created on Mar 14, 2017 12:35:27 PM by  Dariusz Gorka [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.