Bug 810762

Summary:	Zabbix should depend on (and pull in) traceroute
Product:	[Fedora] Fedora EPEL	Reporter:	David Kovalsky <dkovalsk>
Component:	zabbix	Assignee:	Dan Horák <dan>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	high
Version:	el6	CC:	benl, dan, jeff, nelsonab, volker27
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	zabbix-1.8.12-1.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-30 07:58:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description David Kovalsky 2012-04-09 01:04:59 UTC

I've installed a minimal system with Zabbix and noticed that traceroute is not pulled in. It should be, as web UI allows operations such as ping or traceroute. 

Without traceroute installed, the web UI is quiet, but logs show:
  3557:20120409:025701.668 NODE 0: Executing command: '/bin/traceroute $HOSTNAME_REMOVED'
sh: /bin/traceroute: No such file or directory

zabbix-1.8.10-1.el6.x86_64

Comment 1 Volker Fröhlich 2012-04-10 20:59:39 UTC

On the other hand you could argue to remove the traceroute example from the database dump.

Since traceroute has no additional dependencies and probably makes sense on a monitoring server, one could add it.

Comment 2 David Kovalsky 2012-04-11 10:58:08 UTC

Good call :) The tools are even configurable in the web UI with admin privs. 

But I agree, traceroute does make sense to me on a monitoring server too. It's really a small package with no additional dependencies.

Comment 3 Dan Horák 2012-04-12 07:08:50 UTC

thanks for opinions, traceroute will be added in 1.8.12