After additional testing seems that configuration is correct.
Messages were processed correctly when we send them via omrelp. Basic
testing with logger was not successful.
It mean that if we want use imrelp then also client has to send
messages via omrelp? As we were not able process messages via logger
or omfwd it look so.
Best Regards,
Jozef
______________________________________________________________
Od: "Rainer Gerhards via rsyslog" <rsyslog@lists.adiscon.com>
Komu: "rsyslog-users" <rsyslog@lists.adiscon.com>
Dátum: 24.02.2023 18:25
Predmet: Re: [rsyslog] imrelp - no messages processed
CC: <rgerha...@hq.adiscon.com>
also: do you send a proper RELP greeting via telnet? If not, this is
the reason the connection is closed.
Rainer
El vie, 24 feb 2023 a las 18:23, David Lang via rsyslog
(<rsyslog@lists.adiscon.com>) escribió:
what is the rest of your config? what you have shown is the config
to receive
logs, but not any instructions to rsyslog to write logs out.
David Lang
On Fri, 24 Feb 2023, Jozef Zajac via rsyslog wrote:
Date: Fri, 24 Feb 2023 15:41:42 +0100
From: Jozef Zajac via rsyslog <rsyslog@lists.adiscon.com>
To: rsyslog@lists.adiscon.com
Cc: Jozef Zajac <zajac.jo...@centrum.sk>
Subject: [rsyslog] imrelp - no messages processed
Hi everyone,
I'm trying to put rsyslog into a docker container with the imrelp
module.
Setup is quite easy:
rsyslog_docker_global/03-modules.conf:2:module(load="imrelp")
rsyslog_docker_lin/rsyslog.d/11-input-tcp.conf:1:input(type="imrelp"
port="2514" maxDataSize="10k" keepAlive="on")
Unfortunately, there are no logs, but service looks fine. Logger
is working
with UDP (imudp module) but not in imrelp tcp. When I tried the
ptcp module,
logging worked fine.
Setup:
Ubuntu - 22.04 LTS, 5.15.0-56-generic
docker version
Client: Docker Engine - Community
Version: 23.0.1
API version: 1.42
Go version: go1.19.5
Git commit: a5ee5b1
Built: Thu Feb 9 19:47:01 2023
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 23.0.1
API version: 1.42 (minimum version 1.12)
Go version: go1.19.5
Git commit: bc3805a
Built: Thu Feb 9 19:47:01 2023
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.18
GitCommit: 2456e983eb9e37e47538f59ea18f2043c9a73640
runc:
Version: 1.1.4
GitCommit: v1.1.4-0-g5fd4c4d
docker-init:
Version: 0.19.0
GitCommit: de40ad0
rsyslog - 8.2302
rsyslog-relp - 8.2302
librelp0 - 1.11.0
When I try to connect to imrelp with telnet and close the session,
I receive
this error:
v8.2302 (docker)
syslog.err rsyslogd: imrelp[2514]: error 'server closed relp
session, session
broken', object 'lstn 2514: conn to clt127.0.0.1/localhost' -
input may not
work as intended [v8.2302.0 try https://www.rsyslog.com/e/2353
<https://www.rsyslog.com/e/2353> ]
v8.1901 (no docker)
syslog.err rsyslogd: imrelp[514]: error 'server closed relp
session, session
broken', object 'lstn 514: conn to clt 127.0.0.1/localhost' -
input may not
work as intended [v8.1901.0 try https://www.rsyslog.com/e/2353
<https://www.rsyslog.com/e/2353> ]
v8.2112 (no docker)
syslog.err syslogd: imrelp[514]: error 'server closed relp
session, session
broken', object 'lstn 514: conn to clt 127.0.0.1/localhost' -
input may not
work as intended [v8.2112.0 try https://www.rsyslog.com/e/2353
<https://www.rsyslog.com/e/2353> ]
When I ran rsyslog in debug mode, nothing unusual showed up.
(/usr/sbin/rsyslogd -i /var/run/syslog.pid -f /etc/rsyslog.conf -dn)
Is there something that I'm missing on this basic setup ?
Thank you for any advice
Best regards,
Tomas Bekecs
_______________________________________________
rsyslog mailing list
https://lists.adiscon.net/mailman/listinfo/rsyslog
<https://lists.adiscon.net/mailman/listinfo/rsyslog>
http://www.rsyslog.com/professional-services/
<http://www.rsyslog.com/professional-services/>
What's up with rsyslog? Follow https://twitter.com/rgerhards
<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.
_______________________________________________
rsyslog mailing list
https://lists.adiscon.net/mailman/listinfo/rsyslog
<https://lists.adiscon.net/mailman/listinfo/rsyslog>
http://www.rsyslog.com/professional-services/
<http://www.rsyslog.com/professional-services/>
What's up with rsyslog? Follow https://twitter.com/rgerhards
<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.
_______________________________________________
rsyslog mailing list
https://lists.adiscon.net/mailman/listinfo/rsyslog
<https://lists.adiscon.net/mailman/listinfo/rsyslog>
http://www.rsyslog.com/professional-services/
<http://www.rsyslog.com/professional-services/>
What's up with rsyslog? Follow https://twitter.com/rgerhards
<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.
_______________________________________________
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.
