[ZBX-1246] ssh checks return data, but it is not inserted in the database Created: 2009 Nov 10  Updated: 2017 May 30  Resolved: 2009 Dec 04

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 1.9.0 (alpha)
Fix Version/s: 1.9.0 (alpha)

Type: Incident report Priority: Blocker
Reporter: richlv Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

trunk rev 8234

Attachments: PNG File ssh_item.png    

 Description   

created ssh item with password authentication (see screenshot for item config).
according to server log, item data is returned correctly :

23833:20091110:102420.520 In substitute_simple_macros (data:'ssh.run[echo_1,localhost]')
23833:20091110:102420.521 In get_value() key:'ssh.run[echo_1,localhost]'
23833:20091110:102420.521 In ssh_run()
23833:20091110:102420.632 ssh_run() Supported authentication methods:'publickey,password,keyboard-interactive'
23833:20091110:102420.633 ssh_run() Authentication by password succeeded.
23833:20091110:102420.638 ssh_run() exitcode: 0 bytecount: 2
23833:20091110:102420.638 End of ssh_run():SUCCEED

but nothing is inserted in the database.
changing command to 'echo 11' results in :
"ssh_run() exitcode: 0 bytecount: 3"

this seems to indicate that data is indeed returned and received correctly

 Comments   
Comment by richlv [ 2009 Nov 20 ]

for the record, server has ssh support compiled in

Comment by Alexander Vladishev [ 2009 Nov 24 ]

Can't reproduce.
Please attach item configuration screen.
Thanks!

Comment by Dmitry Borovikov [ 2009 Dec 04 ]

This issue was actual only for Numeric(unsigned) and Numeric(float) item type of information. But in any case, you always must be sure, that the returned data can be interpreted as numeric, without any conversions (only "numeric" form can be accepted as an exception).

Comment by richlv [ 2009 Dec 04 ]

confirming the fix in trunk rev 8513

Generated at Wed Jan 22 03:41:16 EET 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.