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.

Bug 1223566

Summary: RFE: imrelp does not support binding to a specific ruleset before rsyslog 8.x
Product: Red Hat Enterprise Linux 7 Reporter: James Ralston <ralston>
Component: rsyslogAssignee: Radovan Sroka <rsroka>
Status: CLOSED ERRATA QA Contact: Stefan Dordevic <sdordevi>
Severity: unspecified Docs Contact: Mirek Jahoda <mjahoda>
Priority: unspecified    
Version: 7.1CC: bressers, cww, lmiksik, mpoole, pvrabec, rsroka, sdordevi
Target Milestone: rcKeywords: FutureFeature, Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Release Note
Doc Text:
The _rsyslog_ RELP module now binds to a specific rule set With this update, the _rsyslog_ Reliable Event-Logging Protocol (RELP) module is now capable of binding to specific rule set with each input instance. The `input()` instance rule set has higher priority than the `module()` rule set.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 05:35:53 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:
Bug Depends On:    
Bug Blocks: 1203710, 1296594, 1313485    
Attachments:
Description Flags
Backport of ruleset parameter
none
Backport of ruleset parameter(2) none

Description James Ralston 2015-05-20 21:55:24 UTC 
Description of problem:

In rsyslog 7.x, the imrelp module does not support binding to a specific ruleset [1].

E.g., this won't work:

input (type="imrelp" port="1514" ruleset="custom-ruleset1")
input (type="imrelp" port="2514" ruleset="custom-ruleset2")

This means that sites that bind specific rulesets to specific listeners in order to classify incoming syslog messages from remote clients cannot use imrelp listeners.

This deficiency is corrected in rsyslog 8.x [2].

Please take one of the following actions:

1. Backport this feature to rsyslog 7.x.
2. Rebase to rsyslog 8.x.
3. Provide rsyslog 8.x using an "rsyslog8" package.

Version-Release number of selected component (if applicable):

rsyslog-7.4.7-7.el7_0.x86_64

Additional info:

[1] http://www.rsyslog.com/doc/v7-stable/configuration/modules/imrelp.html
[2] http://www.rsyslog.com/doc/v8-stable/configuration/modules/imrelp.html
Comment 5 Radovan Sroka 2016-02-22 14:48:29 UTC 
Created attachment 1129331 [details]
Backport of ruleset parameter

After this backport, module() and input() have ruleset parameter and input ruleset has higher priority than module ruleset.

There are some configs for receiver:

--------------------------------------------------

ruleset(name="testrs") {
    action(type="omfile" file="/tmp/testfile")
}


module( load="imrelp"
        ruleset="testrs")
input(  type="imrelp" port="5000")

---------------------------------------------------

ruleset(name="testrs1") {
    action(type="omfile" file="/tmp/testfile")
}

ruleset(name="testrs2") {
    action(type="omfile" file="/tmp/testfile2")
}


module(load="imrelp")
input(type="imrelp" port="5000" ruleset="testrs1")
input(type="imrelp" port="10000" ruleset="testrs2")

--------------------------------------------------

ruleset(name="testrs1") {
    action(type="omfile" file="/tmp/testfile")
}

ruleset(name="testrs2") {
    action(type="omfile" file="/tmp/testfile2")
}


module(load="imrelp" ruleset="testrs1")
input(type="imrelp" port="5000" )
input(type="imrelp" port="10000" ruleset="testrs2")

--------------------------------------------------


And sender config:

--------------------------------------------------

module( load="imuxsock")
input(type="imuxsock" socket="/tmp/socket" createpath="on")
module(load="omrelp")

*.* action(type="omrelp" target="127.0.0.1" port="5000")
*.* action(type="omfile" file="/tmp/in.log")

*.* action(type="omrelp" target="127.0.0.1" port="10000")

--------------------------------------------------


logger -u /tmp/socket <message>
Comment 8 Radovan Sroka 2016-05-17 14:48:21 UTC 
Created attachment 1158335 [details]
Backport of ruleset parameter(2)

Resolved double free found by Stefan Dordevic
Comment 15 errata-xmlrpc 2016-11-04 05:35:53 UTC 
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://rhn.redhat.com/errata/RHEA-2016-2401.html