I have a rule as follows that will not work if I attempt to use the
symbolic representation for local3 facility. I can change the priority to
anything I want and it will not log to either the local logfile nor will it
be forwarded to the remote server.

local3.* {
        action(type="omfwd" target="10.40.46.198" port="10514"
protocol="tcp")
        action(type="omfile" file="/var/log/local3.log")
}

However, If I instead use the numeric equivalent value for local3
(LOG_LOCAL3=19) from syslog.h, it works fine, logging to both the local
file as well as forwarding to my remote server.

19.* {
        action(type="omfwd" target="10.40.46.198" port="10514"
protocol="tcp")
        action(type="omfile" file="/var/log/local3.log")
}

Has anyone else experienced this issue?

I'm running rsyslog version:
rsyslogd 8.24.0-34.el7, compiled with:
PLATFORM: x86_64-redhat-linux-gnu
PLATFORM (lsb_release -d):
FEATURE_REGEXP: Yes
GSSAPI Kerberos 5 support: Yes
FEATURE_DEBUG (debug build, slow code): No
32bit Atomic operations supported: Yes
64bit Atomic operations supported: Yes
memory allocator: system default
Runtime Instrumentation (slow code): No
uuid support: Yes
Number of Bits in RainerScript integers: 64

thanks,

*Scott Slattery*

*Sr. Systems & Cloud Architect*

*Cloud, Compute, Information & Architecture Team*

motorolasolutions.com

*O: 602.529.8226*

*E*: [email protected]

-- 


*For more information on how and why we collect your personal 
information, please visit our Privacy Policy 
<https://www.motorolasolutions.com/en_us/about/privacy-policy.html?elqTrackId=8980d888905940e39a2613a7a3dcb0a7&elqaid=2786&elqat=2#privacystatement>.*
_______________________________________________
rsyslog mailing list
https://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to