Prior to this update, there was a limit of 50 'exec' entries in /etc/snmp/snmpd.conf. With more than 50 such entries in the configuration file, snmpd reported "Error: No further UCD-compatible entries" in the system log. In this update this fixed limit is removed and there can be any number of 'exec' entries in the snmpd configuration file.
Description of problem:
If there are more than 50 Executables/scripts entries in snmpd.conf, net-snmp-5.5-37.el6_2.1.x86_64 produces the following error in /var/log/messages and ignores the entries above 50:
"/etc/snmp/snmpd.conf: line XX: Error: No further UCD-compatible entries"
Version-Release number of selected component (if applicable):
net-snmp-5.5-37.el6_2.1.x86_64
How reproducible:
Every time.
Steps to Reproduce:
1. enter more than 50 "exec" entries in the snmpd.conf file
2. restart snmp
Actual results:
Error message is logged in /var/log/messages
"/etc/snmp/snmpd.conf: line XX: Error: No further UCD-compatible entries"
Expected results:
No errors.
Additional info:
The error is produced because there is a limit in snmpd ( in extend.c ) of max 50 exec entries.
We have built a test package which fixes the issue. We increased the value of:
Max_compatability_entries int = 50;
Is it possible to increase the number in the next release?
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Prior to this update, there was a limit of 50 'exec' entries in /etc/snmp/snmpd.conf. With more than 50 such entries in the configuration file, snmpd reported "Error: No further UCD-compatible entries" in the system log. In this update this fixed limit is removed and there can be any number of 'exec' entries in the snmpd configuration file.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-0421.html