Discussion:
[rsyslog] $ModLoad imtcp or module(load="imtcp")
Mauricio Tavares
2014-03-28 18:10:06 UTC
Permalink
CentOS 6.4 has rsyslog 5.8.10 by default:

[root at scan ~]# rsyslogd -v
rsyslogd 5.8.10, compiled with:
FEATURE_REGEXP: Yes
FEATURE_LARGEFILE: No
GSSAPI Kerberos 5 support: Yes
FEATURE_DEBUG (debug build, slow code): No
32bit Atomic operations supported: Yes
64bit Atomic operations supported: Yes
Runtime Instrumentation (slow code): No

See http://www.rsyslog.com for more information.
[root at scan ~]#

I thought that the module(load="imtcp") was the new way to configure modules,

# Provides TCP syslog reception
# $ModLoad imtcp
# $InputTCPServerRun 514
module(load="imtcp")
input(type="imtcp" port=514)

but it does not seem to like that:

Mar 28 13:44:13 scan rsyslogd-3000: unknown priority name "" [try
http://www.rsyslog.com/e/3000 ]
Mar 28 13:44:13 scan rsyslogd: the last error occured in
/etc/rsyslog.conf, line 19:"module(load="imtcp")"
Mar 28 13:44:13 scan rsyslogd: warning: selector line without actions
will be discarded
Mar 28 13:44:13 scan rsyslogd-3000: unknown priority name "" [try
http://www.rsyslog.com/e/3000 ]
Mar 28 13:44:13 scan rsyslogd: the last error occured in
/etc/rsyslog.conf, line 20:"input(type="imtcp" port=514)"
Mar 28 13:44:13 scan rsyslogd: warning: selector line without actions
will be discarded
Mar 28 13:44:13 scan rsyslogd-2124: CONFIG ERROR: could not interpret
master config file '/etc/rsyslog.conf'. [try
http://www.rsyslog.com/e/2124 ]

So, is this version too old to support the module(load) thingie?
Boylan, James
2014-03-28 18:33:33 UTC
Permalink
Yes. To get access to the new configuration format you need to upgrade to at least v7.

-- James
-- Sent from my mobile --

----- Reply message -----
From: "Mauricio Tavares" <raubvogel at gmail.com>
To: "rsyslog-users" <rsyslog at lists.adiscon.com>
Subject: [rsyslog] $ModLoad imtcp or module(load="imtcp")
Date: Fri, Mar 28, 2014 1:08 PM

CentOS 6.4 has rsyslog 5.8.10 by default:

[root at scan ~]# rsyslogd -v
rsyslogd 5.8.10, compiled with:
FEATURE_REGEXP: Yes
FEATURE_LARGEFILE: No
GSSAPI Kerberos 5 support: Yes
FEATURE_DEBUG (debug build, slow code): No
32bit Atomic operations supported: Yes
64bit Atomic operations supported: Yes
Runtime Instrumentation (slow code): No

See http://www.rsyslog.com for more information.
[root at scan ~]#

I thought that the module(load="imtcp") was the new way to configure modules,

# Provides TCP syslog reception
# $ModLoad imtcp
# $InputTCPServerRun 514
module(load="imtcp")
input(type="imtcp" port=514)

but it does not seem to like that:

Mar 28 13:44:13 scan rsyslogd-3000: unknown priority name "" [try
http://www.rsyslog.com/e/3000 ]
Mar 28 13:44:13 scan rsyslogd: the last error occured in
/etc/rsyslog.conf, line 19:"module(load="imtcp")"
Mar 28 13:44:13 scan rsyslogd: warning: selector line without actions
will be discarded
Mar 28 13:44:13 scan rsyslogd-3000: unknown priority name "" [try
http://www.rsyslog.com/e/3000 ]
Mar 28 13:44:13 scan rsyslogd: the last error occured in
/etc/rsyslog.conf, line 20:"input(type="imtcp" port=514)"
Mar 28 13:44:13 scan rsyslogd: warning: selector line without actions
will be discarded
Mar 28 13:44:13 scan rsyslogd-2124: CONFIG ERROR: could not interpret
master config file '/etc/rsyslog.conf'. [try
http://www.rsyslog.com/e/2124 ]

So, is this version too old to support the module(load) thingie?
_______________________________________________
rsyslog mailing list
http://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.
Loading...