Bug 817203
Summary: | Time to update fping to version 3? | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Christopher Meng <i> |
Component: | fping | Assignee: | Charles R. Anderson <cra> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | el6 | CC: | cleaver-redhat, cra |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-30 15:54:24 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: | |
Embargoed: |
Description
Christopher Meng
2012-04-28 02:38:51 UTC
*** Bug 850995 has been marked as a duplicate of this bug. *** If you are interested in testing fping-3, I have made builds here: EL6: http://koji.fedoraproject.org/koji/buildinfo?buildID=355982 EL5: http://koji.fedoraproject.org/koji/buildinfo?buildID=355986 Extra testing before I push these to EPEL repos would be appreciated. Thanks. I just test it.Seems OK. ? I just want to put here on the record that I have been having problems with fping-3 on EL5. I had been running it on my production nagios & autostatus server, but it seems to be dying during heavy usage which causes false downtime alerts in autostatus. That is why I haven't pushed an update to EPEL5 or EPEL6 yet. I need to do more testing before opening a bug report on this, and also retest with fping-3.5. I just want to put here on the record that I have been having problems with fping-3 on EL5. I had been running it on my production nagios & autostatus server, but it seems to be dying during heavy usage which causes false recovery alerts in autostatus (i.e. things that have been un-pingable all of a sudden come back as up from fping, but they really aren't up). That is why I haven't pushed an update to EPEL5 or EPEL6 yet. I need to do more testing before opening a bug report on this, and also retest with fping-3.5. There was a recent bug fix in 3.5 that may have solved the problem you were experiencing. It did on our Icinga/Xymon server. This has been running pretty well in Fedora for a while now. Any chance it can be rebased in EPEL at this point? I'm keeping epel7 updated, but I hesitate to change the major version in el6 from 2.4 to 3.x due to the EPEL Updates Policy: https://fedoraproject.org/wiki/EPEL_Updates_Policy "All updates should strive to avoid situations that require manual intervention to keep the package functioning after update. Major updates with changes to user experence are to be avoided." Here is a build of fping 3.10 for el6: http://koji.fedoraproject.org/koji/buildinfo?buildID=673200 This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. 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 EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. 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 EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above. EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of EPEL please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |