| Summary: | SNMP is not functional in Zabbix 2.0 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | james Whitby <jim> |
| Component: | RPM Packages | Assignee: | Dimitri Jakov <mitya> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | Keywords: | Triaged |
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | zabbix | CVE: | |
| Status comment: | |||
|
Description
james Whitby
2014-10-28 00:26:53 CET
>Zabbix requires at least ver 2.2 for snmp to be functional
where did you see that ?Keywords:
(none) =>
Triaged The package is due to be removed in Mageia 5 unless someone steps up to maintain it and update it to at least 2.2.x. (In reply to Manuel Hiebel from comment #1) > >Zabbix requires at least ver 2.2 for snmp to be functional > where did you see that ? Somewhere in zabbix related forums. (In reply to David Walser from comment #2) > The package is due to be removed in Mageia 5 unless someone steps up to > maintain it and update it to at least 2.2.x. Kinda suspected as much, since it is 2 ver behind current. Oh well. I tried to compile it, but (configure) it hangs on the mysqlclient.so, indicating it isn't there, when in fact it is. Thanks Looking at Fedora's package may help get it building correctly. Speaking of Zabbix, if you use that, we could use help testing the update candidate for it in Bug 13628. (In reply to David Walser from comment #5) > Looking at Fedora's package may help get it building correctly. > > Speaking of Zabbix, if you use that, we could use help testing the update > candidate for it in Bug 13628. I'd be happy to test it. Not sure what help I might be, since it doesn't work properly for me anyway.. Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Status:
NEW =>
RESOLVED |