Hi Marcin, glad to see im not the only one experiencing the problem. I have the same setup you do, I am using RELP and file monitoring as well.

The main reason I noticed it was because im migrating from sysklogd to rsyslog on our prod RHEL5 boxes and boxes that normally had a lot of syslog output suddenly had none or extremely delayed logging. I never added any config changes to the queue's as I didnt think we had enough volume to merit changing the defaults but thats what im trying first on my end.

Ive also had a weird issue this weekend where rsyslog/pdns are not playing well together and testing has proven (by using restoring rsyslog configs to defaults) that the delay related to rsyslog caused pdns to be unable to respond to dns lookups after a reboot.

Ill try your test config on one of my lab boxes and follow up.

Thanks,

On 05/22/2012 11:27 AM, Rainer Gerhards wrote:
Excellent, small config is always good! I'll try to reproduce this tomorrow
morning. Thanks for your persistence!
Rainer

-----Original Message-----
From: [email protected] [mailto:rsyslog-
[email protected]] On Behalf Of Marcin Miroslaw
Sent: Tuesday, May 22, 2012 5:25 PM
To: [email protected]
Subject: Re: [rsyslog] rsyslog-5.8.11 omit syncing is always on?

W dniu 22.05.2012 13:48, Rainer Gerhards pisze:
Hi Folks,

just to break the silence: this issue is on my list of things to look
at. As
usual, it's just quite busy (and thankfully with paid work as well),
so this
waits on a timeslot...
Hi!
I know you have many work. I asked Julio about his use case because i
have a little problem to reproduce situation on test box.
Now meseems i can reproduce problem with maximally stripped config
file[1].
This steps should allow to reproduce situation:
1. start rsyslog with given config
2. cat "some text file, a several dozen of lines should be enough">>
/var/log/exim/exim_main.log
3. try to use logger and log any message
4. if it works wait sometime, eventually repeat step 2
5. try to use logger

David, you didn't hit such problem because you probably doesn't monitor
files and send logs via relp. (In my tests it looks like both situation
are needed: filemonitor and sending via relp).

Regards,
Marcin

[1] - config file:
$ModLoad immark.so
$ModLoad imuxsock.so
$ModLoad imklog.so
$ModLoad imrelp.so
$ModLoad omrelp.so
$ModLoad imfile

$WorkDirectory          /var/spool/rsyslog
$ActionQueueType        LinkedList
$ActionQueueFileName    dbq
$ActionResumeRetryCount -1
$MainMsgQueueMaxDiskSpace       312M
$MainMsgQueueSaveOnShutdown     on
$MainMsgQueueCheckpointInterval 80
$MainMsgQueueSyncQueueFiles     on
$MainMsgQueueTimeoutShutdown    10000

$InputFileName /var/log/exim/exim_main.log
$InputFileTag meteor.exim_main:
$InputFileStateFile meteor.exim_main
$InputFileFacility mail
$InputFilePollInterval 1
$InputRunFileMonitor

*.* :omrelp:10.10.100.101:20514
*.*     /var/log/wszystko.log

_______________________________________________
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
_______________________________________________
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
_______________________________________________
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

Reply via email to