Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionDavid Fernandez
2014-11-18 15:36:08 UTC
Description of problem:
If omsnmp trapoid or messageoid parameters are specified as "FILE-MIB::oid_name" instead of OID numeric form (e.g. "1.3.6.1.4.1.19406.1.2.1"), the trap sending fails with error:
rsyslogd-2006: omsnmp_sendsnmp: Adding trap OID failed '
ADISCON-MONITORWARE-MIB::syslogtrap' with error 'Unknown Object Identifier'
[try http://www.rsyslog.com/e/2006 ]
The mib files were put in /usr/share/mibs, and /usr/share/snmp/mibs (the directory reported by net-snmp-config --default-mibdirs).
The same thing works ok in rhel6.
Also, if using the utility snmptrap, it works ok in rhel7:
snmptrap -v 2c -c public udp:my.server.xxx '' 'ADISCON-MONITORWARE-MIB::syslogtrap' 'ADISCON-MONITORWARE-MIB::syslogMsg' s 'test' 'ADISCON-MONITORWARE-MIB::syslogSeverity' i 6 'ADISCON-MONITORWARE-MIB::syslogFacility' i 23 'ADISCON-MONITORWARE-MIB::syslogTag' s 'df_test:'
Version-Release number of selected component (if applicable):
7.4.7-6.el7
How reproducible:
Always.
Steps to Reproduce:
1. Put relevant MIB files defining the OIDs required in /usr/share/mibs and /usr/share/snmp/mibs; e.g. ADISCON-MIB (from http://www.adiscon.org/download/ADISCON-MIB.txt), and ADISCON-MONITORWARE-MIB (from http://www.adiscon.org/download/ADISCON-MONITORWARE-MIB.txt)
2. Configure rsyslog appropirately: e.g. put a file in /etc/rsyslog.d/ called xxx.conf with something like:
# File 1
input(type="imfile"
File="/var/df/rsyslog_test_file1.txt"
Tag="df_test_1:"
Severity="info"
Facility="local5"
ReadMode="1"
StateFile="stat-file1")
# File 2
input(type="imfile"
File="/var/df/rsyslog_test_file2.txt"
Tag="df_test_2:"
Severity="info"
Facility="local6"
ReadMode="1"
StateFile="stat-file2")
module(load="omsnmp")
local5.info action( type="omsnmp"
transport="udp"
server="my.server.xxx"
port="162"
version="1"
community="public"
trapoid="ADISCON-MONITORWARE-MIB::syslogtrap"
messageoid="ADISCON-MONITORWARE-MIB::syslogMsg" )
local6.info action( type="omsnmp"
transport="udp"
server="my.server.xxx"
port="162"
version="1"
community="public"
trapoid="1.3.6.1.4.1.19406.1.2.1"
messageoid="1.3.6.1.4.1.19406.1.1.2.1" )
3. mkdir /var/df
touch /var/df/rsyslog_test_file{1,2}.txt
{ echo "test"; echo; } >>rsyslog_test_file2.txt
works (see /var/log/messages)
{ echo "test"; echo; } >>rsyslog_test_file1.txt
fails (see /var/log/messages)
Actual results:
Fail with error:
rsyslogd-2006: omsnmp_sendsnmp: Adding trap OID failed 'ADISCON-MONITORWARE-MIB::syslogtrap' with error 'Unknown Object Identifier'
[try http://www.rsyslog.com/e/2006 ]
Expected results:
No errors expected.
Additional info:
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.
https://access.redhat.com/errata/RHBA-2017:2306