Bug 207616
| Summary: | [REPOCOPY] net-mgmt/zabbix24 -> zabbix3 (server/agent/frontend/proxy) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | pg | ||||||||||||
| Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||||||||||
| Status: | Closed FIXED | ||||||||||||||
| Severity: | Affects Some People | CC: | akuz84, dbaio, feld, gregory.orange, kbowling, martin, pg | ||||||||||||
| Priority: | --- | ||||||||||||||
| Version: | Latest | ||||||||||||||
| Hardware: | Any | ||||||||||||||
| OS: | Any | ||||||||||||||
| Bug Depends on: | |||||||||||||||
| Bug Blocks: | 208029 | ||||||||||||||
| Attachments: |
|
||||||||||||||
Created attachment 167600 [details]
poudriere log of zabbix3-server
Created attachment 167601 [details]
poudriere log of zabbix3-agent
Created attachment 167602 [details]
poudriere log of zabbix3-proxy
Created attachment 167603 [details]
poudriere log of zabbix3-frontend
Just to let you know: I've been running your zabbix3 port on a test box for three days. Everything worked very well including the database upgrade. Kudos! https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207896 is probably relevant here I just noticed that there is no option to compile zabbix3-server, zabbix3-proxy or zabbix3-agent with TLS support.
Since one of the main new things about Zabbix 3 is encrypted communication between monitoring entities, perhaps we should adapt the Makefile to read like:
OPTIONS_DEFINE= IPV6 FPING JABBER CURL LDAP IPMI SSH NMAP JAVAGW \
LIBXML2 OPENSSL
...
OPENSSL_DESC= Support for SSL-encrypted communication
...
OPENSSL_CONFIGURE_WITH= openssl
OPENSSL_USE= OPENSSL=yes
Apparently both mbed TLS (PolarSSL) and GnuTLS are also possible. But I am not familiar with those.
Committed with minor changes, thanks! (In reply to Martin Waschbüsch from comment #7) Martin, would you mind opening a separate PR for that? The current zabbix3 is functional, but I agree this feature should be exposed and it would be worth allowing the user to choose which TLS implementation they want to build against. That definitely goes beyond the scope of this repocopy PR. A commit references this bug: Author: feld Date: Tue Mar 15 13:48:02 UTC 2016 New revision: 411162 URL: https://svnweb.freebsd.org/changeset/ports/411162 Log: net-mgmt/zabbix24 -> zabbix3 Welcome zabbix3 to the ports tree PR: 207616 Changes: head/net-mgmt/Makefile head/net-mgmt/zabbix3-agent/ head/net-mgmt/zabbix3-agent/Makefile head/net-mgmt/zabbix3-frontend/ head/net-mgmt/zabbix3-frontend/Makefile head/net-mgmt/zabbix3-proxy/ head/net-mgmt/zabbix3-proxy/Makefile head/net-mgmt/zabbix3-server/ head/net-mgmt/zabbix3-server/Makefile head/net-mgmt/zabbix3-server/distinfo head/net-mgmt/zabbix3-server/files/pkg-message.in head/net-mgmt/zabbix3-server/pkg-plist.agent head/net-mgmt/zabbix3-server/pkg-plist.frontend |
Created attachment 167599 [details] shell archive Zabbix 3 is LTS version (All versions since 2.0.0 officially supported for 5 years) Please REPOCOPY zabbix24 to zabbix3