I am trying to get Ubuntu 22.04 rsyslog clients to connect to a Red Hat 8.8
rsyslog server using RELP over TLS. The Red Hat server has been configured
using the guidelines supplied by Red Hat. Both client and server have
certificates issued by a common certificate authority.. The Ubuntu client
is r
on many systems, the permissions of a program started at boot are no longer
simple root (systemd is being configured to to retrict the programs
significantly
So I would suggest that you try starting rsyslog as root manually and see if
that avoids this error message. If so, then it's a differen
Good day
I'm still experiencing this situation where OOM-killer kills the rsyslogd
process for consuming too much memory. What do you suggest is the next step to
take to address this memory leak?
Kind Regards
---
From: Adriaan de Waal
Sent: 12 December 2023 06:
Thanks David
I have tried running it with ryslogd -n as root but it gives the same error
message. I made sure before running it that the rsyslog service and the
syslog socket were stopped but it gives the same error. I should also say
that I have switched to openssl when the omrelp module is loaded
The error is very clear that rsyslog is not able to read the file, so either you
have the wrong path, or there is a permission problem (classic/apparmor/selinux
permissions)
If you enable debug logging and capture that, you can go through it looking for
the error message and see exactly what i
Thanks David
it was a directory and files permission issue
So in the directory containing my ca, client certificate and private keys
file
chown root:syslog *.pem
chmod 640 *.pem
And then the containing directory
chown root:syslog /etc/
chmod 750 /etc/
followed by
systemctl restart rsyslog
And it
6 matches
Mail list logo
