[rsyslog] Development of failsafe disk based queue

[David Ecker]

Hi,

3.21.5 created an assertion error.

rsyslogd: msg.c:208: MsgUnlockLockingCase: Assertion `pThis != ((void
*)0)' failed.

close to the end. Propably short before the abort signal.

I mounted /rsyslog (ext3) with the option : sync

Here is a copy of my rsyslog.conf:
#---------------------------------------
$ModLoad imuxsock.so   
$ModLoad imklog.so     

$WorkDirectory /rsyslog
$ActionQueueFileName buffer
$ActionQueueMaxDiskSpace 1g
$ActionQueueSaveOnShutdown on
$ActionQueueType Disk
$ActionQueueMaxFileSize 1m
$ActionQueueCheckpointInterval 1
$ActionResumeRetryCount -1
*.* @@10.8.0.1:514
#---------------------------------------

I attached the output from"

rsyslogd -c 3 -f /etc/rsyslog.conf  > error.txt 2>&1

Actually only one messagefile was written, no .qi file was created.

bye
David Ecker


Rainer Gerhards schrieb:
> On Wed, 2008-10-01 at 08:43 -0700, david at lang.hm wrote:
>   
>> On Wed, 1 Oct 2008, David Ecker wrote:
>>
>>     
>>> Already did both with 2.18.3 but'll try again with 3.21.5 and 3.18.4. My
>>> guess is, that the O_DIRECT in combination with the O_SYNC flag (turning
>>> of cache) will have an impact.
>>>       
>> O_DIRECT is doing very different things. I don't think you need to worry 
>> about those things, having the data not go into the OS cache is a drawback 
>> not an advantage becouse it means that when you go to pull the data back 
>> out of the file it will need to actually touch disk. it also imposes 
>> significant alignment issues on the application that I don't think you 
>> want to have to desl with.
>>     
>
> plus rsyslog does not care about the alignment (at this time), so I think it is dangerous...
>
> Rainer
>
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com
>   

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: error.txt
URL: <http://lists.adiscon.net/pipermail/rsyslog/attachments/20081006/27a3ac8b/attachment.txt>