[rsyslog-notify] Forum Thread: Re: ruleset does not work, no writing into file - (Mode 'reply')

[noreply at adiscon.com]

User: dlang 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=24399#p24399

Message: 
----------
privdrop has problems on several distros due to the permissions on the
directories where you are going to be writing logs, check that.

Also check if SELinux is giving you problems. It could be that when it's
started up, it starts with one set of permissions, but when you start it
manually there are different permissions.

If this does not help, it could be a problem that going into debug mode
solves.

Unfortunantly, rsyslog 5.8.10 is very old, the current community supported
version is 7.6 and we expect 8.2 to be released pretty soon. There have
been a HUGE number of changes since 5.8 was released almost two years ago.
CentOS sticks with that version because that's what RedHat ships. RedHat
support still supports that version with their paid support.

We are happy to try and help you, but when it gets beyond simple
configuration things, and starts getting into odd behavior that differs
between debug and normal runs, you will probably need to either upgrade to
a recent version that the community is supporting for free, or look at
getting some paid support for the older version (if you  want to go the
paid support route, e-mail <!-- e --><a
href="mailto:info at adiscon.com">info at adiscon.com</a><!-- e --> and they will
work with you)