[ZBXNEXT-2252] Add timeout option to SSH simple check Created: 2014 Apr 11  Updated: 2023 Sep 27  Resolved: 2023 Sep 27

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F), Server (S)
Affects Version/s: None
Fix Version/s: None

Type: Change Request Priority: Minor
Reporter: Raymond Kuiper Assignee: Unassigned
Resolution: Fixed Votes: 4
Labels: newitemkey, ssh, timeout
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by ZBXNEXT-2881 SSH Agent Timeout too small Closed
Sub-task
part of ZBXNEXT-1096 Configurable Timeout per item (host i... Closed

 Description   

Some network appliances impose a delay on returning a valid SSH banner when setting up a connection as a 'security' measure.
The only way around this is to either monitor on a simple tcp port 22 connection, or adjust the Timeout option in the zabbix_server.conf which is a bit overkill.

For these devices it would be really handy to be able to pass a timeout parameter to the itemkey:

net.tcp.service[ssh,<ip>,<port>,<timeout>]

Or something similar.

Preferably we could use a userparameter to supply the timeout value so we can adjust a generic template on the hostlevel if needed.

 Comments   
Comment by Oleksii Zagorskyi [ 2015 Jul 08 ]

ZBXNEXT-1096 would resolve current request in a more general way.

Comment by Arthur Ivanov [ 2015 Jul 16 ]

i also affected by this issue.
trying to monitor some routers by ssh with no success, because those routers have 3G/LTE connections. So handshake can be 2+ seconds. I describe it at ZBXNEXT-2881

Comment by Arthur Ivanov [ 2015 Jul 16 ]

also, i don't know why errors
24065:20150715:220040.582 error reason for "mikrotik:ssh.run[pppCurrentOperator]" changed: Cannot obtain authentication methods: Would block requesting userauth list
24066:20150715:220040.721 item "mikrotik:ssh.run[pppAccessTechnology]" became not supported: Cannot establish SSH session: Unable to exchange encryption keys
24065:20150715:220050.669 error reason for "mikrotik:ssh.run[pppModemStatus]" changed: Cannot establish generic session channel
24064:20150715:220442.081 error reason for "mikrotik:ssh.run[pppAccessTechnology]" changed: Password authentication failed: Would block waiting
24064:20150715:220541.099 error reason for "mikrotik:ssh.run[pppCurrentOperator]" changed: Cannot establish SSH session: Unable to exchange encryption keys
24064:20150715:220543.970 error reason for "mikrotik:ssh.run[pppFunctionality]" changed: Cannot establish SSH session: Unable to exchange encryption keys
24066:20150715:220553.435 error reason for "mikrotik:ssh.run[pppModemStatus]" changed: Cannot establish SSH session: Unable to exchange encryption keys

written at server log,but not at proxy who gather those items.

Comment by Martynov Ilya [ 2015 Sep 26 ]

Try changing the parameter "Timeout" in zabbix_server.log

Comment by Aleksandrs Saveljevs [ 2016 Jun 06 ]

Similar request for all kinds of net.tcp.service[] items, as well as net.tcp.port[]: ZBXNEXT-3295.

Comment by Dmitrijs Goloscapovs [ 2023 Sep 27 ]

Versatile timeouts (including configurable timeouts for ssh checks) have been implemented in 7.0.0alpha5. Please follow ZBXNEXT-1096 for more information.

Generated at Thu Apr 18 13:28:07 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.