Ad Widget

Collapse

Issue with Remote SSH Command in Action Configuration

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • bullmike
    Junior Member
    • Jul 2014
    • 10

    #1

    Issue with Remote SSH Command in Action Configuration

    Hello,

    I've created an action to accompany a trigger that should log in via SSH to a router and ping a few IP to bring back up a VPN tunnel to a remote location. As a test I modified the host with an invalid IP address to trigger the action.

    In the event details I get the following error message for the SSH connection:

    === Cannot establish SSH session: Unable to exchange encryption keys ===

    From the zabbix server - v2.2.1 on Centos 6.5 via Yum EPEL installation - I can SSH to the host without issue and added the RSA key to known_hosts using the username/password as specified in the the configuration for the Remote SSH command.

    I turned on Debug logging but it doesn't seem to provide any information that may be useful in troubleshooting the issue.

    Any ideas?
  • filipp.sudanov
    Senior Member
    Zabbix Certified Specialist
    • May 2014
    • 137

    #2
    1. Go through the docs to check if nothing is missed - https://www.zabbix.com/documentation...pes/ssh_checks
    2. Zabbix server is running under "zabbix" user. That user has it's own known_hosts. Try something like "su - zabbix" - not sure about exact command for CentOS and check if you can connect to you server from zabbix user. You man need to alter /etc/passwd and put a proper command intepreter for zabbix user.

    Comment

    • bullmike
      Junior Member
      • Jul 2014
      • 10

      #3
      Turns out the device that I was trying to SSH into only supported SSH1 no SSH2. As far as I know Zabbix requires SSH2 to function correctly.

      A good way to test if you end device is compatible with SSH2 is to login to your zabbix server and issue a 'ssh -2 user@ip' you will get an error similar to the following if your device doesn't support (or doesnt have enabled ) SSH2.

      Protocol major versions differ: 2 vs. 1"

      Comment

      Working...