[ZBX-2204] ZABBIX with SSH2 support on FreeBSD8.0 Created: 2010 Mar 22  Updated: 2017 May 30  Resolved: 2012 Aug 27

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

Type: Incident report Priority: Minor
Reporter: Derick Smit Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: freebsd
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

FreeBSD8.0, Zabbix 1.8.1 Server with SSH2 support compiled in


Attachments: JPEG File SSH monitors.jpg     Zip Archive ZBX-2204.zabbix_server.log.zip    

 Description   

When creating a new agentless SSH monitor, the first one works fine. Adding any more though results in non-working monitors with no apparent reason.



 Comments   
Comment by richlv [ 2010 Mar 22 ]

works just fine on linux. which libssh version was zabbix compiled against ?
please provide logfile at debuglevel 4 - preferably having single host w/o items, first ssh item added, then second added and wait for some time to be sure it does not collect any data.

make sure to increase max logfile size so that it contains some useful information

Comment by Derick Smit [ 2010 Mar 22 ]

Logfile set to debug mode. It shows the one SSH agentless monitor that works (ssh.run[rgel30cpu,10.83.114.201,22,utf8]), but it doesn't seem to even attempt running the other three (see to be attached screenshot).

As the three other monitors are clones of the working SSH monitor, I can't figure out why only the one would run fine, but not the other three.

Comment by Derick Smit [ 2010 Mar 22 ]

4 SSH monitors in total, yet only the first one seems to be run.

Comment by Derick Smit [ 2010 Mar 23 ]

Just regarding libssh, exact version I've got installed is:
libssh2-1.2.4, 2

Comment by Derick Smit [ 2012 Apr 19 ]

Guys, you may as well close this ticket, 2010 has been over for quite some time now. Besides, I doubt I'll run into this error again, and if I do, I'll just switch to a Linux distro that we know works.

Comment by Alexei Vladishev [ 2012 Aug 27 ]

Sorry we didn't help you much with the original issue. I am closing it for now, feel free to reopen.

Generated at Sun Apr 06 15:12:55 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.