I'm trying to set up TLS 1.3 for rsyslog on Debian 10 system. The default
rsyslog on Deb 10 is 8.2102. I've tried to use TLS by inserting this in a
file in rsyslog.d/tls.conf on my client:
module(load="imtcp"
StreamDriver.mode="1"
StreamDriver.authmode="anon"
Free community support (at least from me) is only for the latest
release. For paying support customers, we also look at older releases.
The reason is that in far too many cases I wasted my time
investigating long-fixed bugs. It's inefficient and honestly not fun
at all. Nothing to do in your free
Hi,
We can't upgrade to the very latest versions of rsyslog (for several
reasons), but we are considering upgrading to 8.2106, after this upgrade
if the problem persists would you be able to help us?
Best regards,
Ricardo Esteves.
On 3/25/22 12:43, Rainer Gerhards wrote:
I may be wrong -
>
> This is the directory. I think this is what you mean? DIS is the group
listed as [ADMN GRP] previously. Thank you for looking at thism, again
first experience with rsyslog and was inherited.
drwxrwxrwx. root DIS system_u:object_r:nfs_t:s0 rsyslog_DIR
check directory permissions and check SELinux/AppArmor permissions.
We really aren't going to be able to make much better guesses without seeing the
full config.
David Lang
On Wed, 20 Apr 2022, Mike Michael via rsyslog wrote:
Date: Wed, 20 Apr 2022 14:44:15 -0400
From: Mike Michael via
since you just added the permission changes to the rsyslog config, they are
almost certain to be the cause of the grief.
the standard unix permissions of the directory look good, I don't know your
system enough to say if the SELinux permissions are good or not (hopefully
someone else can
We astrated getting failures with rsyslog a few weeks back, and cannot find
any evidence of any change being mader at that time. Long story short,
inherited system, has been working/running for years, sans problems. I have
checked forums/internet, checked permissions on the DIR where logs are
Thank you David! Sorry, the entire conf file is below. Again the only thing
I touched, and this was in an attempt to fix, was adding the
$PrivDropToUser/Group (which makes ntro change is present or commented out).
# rsyslog configuration file
$umask
$FileCreateMode 0660
$DirCreateMode 0755
so I see nothing in the included file that writes to a dynamic filename, and no
template that matches the error you posted earlier, so there is additional
configuration that you didn't post here.
Also we would need to see the permissions for the directory this is trying to
write to (including
Hello.
I searched for a few hours and did not find any solid technical (not
belief based) in having systemd's journald in the logging path. So I
decided to remove it and use only rsyslog. I appreciate the effort
made by the rsyslog team to support journald, but simply did not find
any reason
yes, the module() statement is the best way to load a module (there is an
earlier way to do it, but if you have to give it any parameters, use module() )
can you please document how you disabled journald? every time I've asked the
systemd folks how to do so, I've been told that it's a
11 matches
Mail list logo
