On Thu, 30 May 2013, C. L. Martinez wrote:
On Mon, May 27, 2013 at 2:46 PM, David Lang <[email protected]> wrote:
On Mon, 27 May 2013, C. L. Martinez wrote:
.. but it doesn't works (by2.log is empty always). Using this type of
configuration with rsyslog 5.8.x under CentOS servers, works.
I have attached debug log, but I can't where it can be the problem.
from the logs, it looks like the worker thread fails every time it tries to
write to disk.
One thing I would suggest is to simplify your configuration.
unless you have other things in your config, there is no advantage to
defining an action queue for one output.
In addition, if you are just going to write the logs out to disk for the
action, there's also not really any value in defining an action queue. If
the disk isn't full, it will just write to the file, if the disk is full it
can't write to the queue file
Try stripping your config down to just:
$MaxMessageSize 64k
$ModLoad imtcp # needs to be done just once
$MainMsgQueueSize 8000000
$InputTCPServerRun 10514
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
*.* /tmp/by2.log
& ~
and see what happens.
David Lang
Thanks David, and sorry for my late response. Problem is solved now.
what was the problem?
David Lang
_______________________________________________
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.
