Fedora Account System
Red Hat Associate
Red Hat Customer
+++ This bug was initially created as a clone of Bug #1719350 +++ The current version of net-snmp (net-snmp-5.8-7.el8.x86_64) flood messages file with following messages on the system having ipv6 disabled. ipaddress_linux: could not open /proc/net/if_inet6: No such file or directory Upstream has already fixed this bug by just writing this line once instead of so many times. ---------------------------------------------------------------------- From cd09fd82522861830aaf9d237b26eef5f9ba50d2 Mon Sep 17 00:00:00 2001 From: Bart Van Assche <bvanassche> Date: Wed, 21 Nov 2018 20:47:42 -0800 Subject: [PATCH] MIB-II: Only log once that opening /proc/net/if_inet6 failed If IPv6 has been disabled (ipv6.disable=1) then opening /proc/net/if_inet6 fails. Only log this once instead of thousand of times a day. Reported-by: Fif <lefif.net> --- agent/mibgroup/ip-mib/data_access/ipaddress_linux.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/agent/mibgroup/ip-mib/data_access/ipaddress_linux.c b/agent/mibgroup/ip-mib/data_access/ipaddress_linux.c index 5ddead3e0..280575ce3 100644 --- a/agent/mibgroup/ip-mib/data_access/ipaddress_linux.c +++ b/agent/mibgroup/ip-mib/data_access/ipaddress_linux.c @@ -234,7 +234,7 @@ _load_v6(netsnmp_container *container, int idx_offset) #define PROCFILE "/proc/net/if_inet6" if (!(in = fopen(PROCFILE, "r"))) { - snmp_log_perror("ipaddress_linux: could not open " PROCFILE); + NETSNMP_LOGONCE((LOG_ERR, "ipaddress_linux: could not open " PROCFILE)); return -2; } ---------------------------------------------------------------------- More info at https://sourceforge.net/p/net-snmp/bugs/2903/
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
FEDORA-2020-c3ab547325 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c3ab547325
FEDORA-2020-44b769adaf has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-44b769adaf
FEDORA-2020-7303a69282 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-7303a69282
FEDORA-2020-c3ab547325 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-c3ab547325` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c3ab547325 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-44b769adaf has been pushed to the Fedora 30 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-44b769adaf` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-44b769adaf See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-7303a69282 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-7303a69282` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-7303a69282 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-44b769adaf has been pushed to the Fedora 30 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-7303a69282 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-c3ab547325 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.