mirror of
https://github.com/rsyslog/rsyslog.git
synced 2025-12-13 04:50:41 +01:00
State file handling was invalid. When a file was moved and re-created rsyslog could use the file_id if the new file to write the old files' state file. This could make the file reader stuck until it reached the previous offset. Depending on file sizes this could never happen AND would cause large message loss. This situation was timing dependent (a race) and most frequently occurred under log rotation. In polling mode the bug was less likely, but could also occur. closes: https://github.com/rsyslog/rsyslog/issues/3465 closes: https://github.com/rsyslog/rsyslog/issues/3468
31 lines
826 B
Bash
Executable File
31 lines
826 B
Bash
Executable File
#!/bin/bash
|
|
# added 2016-11-02 by rgerhards
|
|
# This is part of the rsyslog testbench, licensed under ASL 2.0
|
|
. ${srcdir:=.}/diag.sh init
|
|
. $srcdir/diag.sh check-inotify
|
|
generate_conf
|
|
add_conf '
|
|
global(workDirectory="'${RSYSLOG_DYNNAME}'.spool")
|
|
|
|
module(load="../plugins/imfile/.libs/imfile")
|
|
|
|
input( type="imfile"
|
|
file="./'$RSYSLOG_DYNNAME'.input"
|
|
tag="file:"
|
|
startmsg.regex="^msgnum"
|
|
PersistStateInterval="1"
|
|
)
|
|
|
|
template(name="outfmt" type="string" string="%msg:F,58:2%\n")
|
|
if $msg contains "msgnum:" then
|
|
action(type="omfile" file=`echo $RSYSLOG_OUT_LOG` template="outfmt")
|
|
'
|
|
# generate input file first. Note that rsyslog processes it as
|
|
# soon as it start up (so the file should exist at that point).
|
|
./inputfilegen -m5 -d4000 > $RSYSLOG_DYNNAME.input
|
|
startup
|
|
shutdown_when_empty
|
|
wait_shutdown
|
|
seq_check 0 3
|
|
exit_test
|