Rsyslog: imfile-symlink occasionally fails

Created on 18 Mar 2019  路  10Comments  路  Source: rsyslog/rsyslog

reports: http://build.rsyslog.com/testbench-showtest.php?testname=imfile-symlink%

Not all may show actual errors, but given the volume I am sure some are at least races.

@jvymazal could you have a look?

bug
Source
picture rgerhards

All 10 comments

I will add to the doc that imfile symlink functionality is flaky and should be avoided. I'll also see to disable the test. We can redo this once the issue is fixed. Better plainly state it doesn't work than the make user fall into a trap.

rgerhards picture rgerhards on 12 Apr 2019

Probably good approach, I got snowed under other stuff and although I still plan to look into it, it does not look like it will be a quick fix...

jvymazal picture jvymazal on 12 Apr 2019
👍1

same with me ;-)

rgerhards picture rgerhards on 12 Apr 2019

@jvymazal I added some more debug to the test and noticed something interesting. Full log: https://build.rsyslog.com/#/builders/144/builds/2254/steps/3/logs/test-suite_log, excerpt:

creating rstb_717260_e3639ad4.targets/8.log
+ ./inputfilegen -m 1 -i 7
+ ls -l rstb_717260_e3639ad4.targets/8.log
-rw-r--r-- 1 buildbot buildbot 17 Apr 12 15:27 rstb_717260_e3639ad4.targets/8.log
+ ln -s rstb_717260_e3639ad4.targets/8.log rsyslog-link.8.log
+ ln -s rsyslog-link.8.log rstb_717260_e3639ad4.input.8.log
++ tb_timestamp
+++ date +%H:%M:%S
+++ date +%s
++ printf '%s[%s] ' 15:27:18 1
+ printf '%s generated file %s\n' '15:27:18[1] ' 8
15:27:18[1]  generated file 8
+ ls -l rsyslog-link.8.log
lrwxrwxrwx 1 buildbot buildbot 34 Apr 12 15:27 rsyslog-link.8.log -> rstb_717260_e3639ad4.targets/8.log
+ set +x
content_check_with_count success, "HEADER msgnum:000000" occured 8 times
creating rstb_717260_e3639ad4.targets/9.log
+ ./inputfilegen -m 1 -i 8
+ ls -l rstb_717260_e3639ad4.targets/9.log
-rw-r--r-- 1 buildbot buildbot 17 Apr 12 15:27 rstb_717260_e3639ad4.targets/9.log
+ ln -s rstb_717260_e3639ad4.targets/9.log rsyslog-link.9.log
+ ln -s rsyslog-link.9.log rstb_717260_e3639ad4.input.9.log
++ tb_timestamp
+++ date +%H:%M:%S
+++ date +%s
++ printf '%s[%s] ' 15:27:18 1
+ printf '%s generated file %s\n' '15:27:18[1] ' 9
15:27:18[1]  generated file 9
+ ls -l rsyslog-link.9.log
ls: cannot access 'rsyslog-link.9.log': No such file or directory
+ set +x

Do you have an idea of why rsyslog-link.9.log does not exist while ln -s rstb_717260_e3639ad4.targets/9.log rsyslog-link.9.log seems to have worked?

rgerhards picture rgerhards on 12 Apr 2019

Unless there is some weird way to silence error from ln -s output, I do not think I ever encountered situation where the symlink would not exist without preceding error message.

jvymazal picture jvymazal on 15 Apr 2019

Unless there is some weird way to silence error from ln -s output, I do not think I ever encountered situation where the symlink would not exist without preceding error message.

yeah, same with me. I have added -v to ln. Let's see if we get some more info the next time (of course, over the weekend it didn't occur ;-)).

rgerhards picture rgerhards on 15 Apr 2019

Finally, the problem re-occured (CI is not that busy ATM):

FAIL: imfile-symlink
====================
testbench: TZ env var not set, setting it to UTC
------------------------------------------------------------
13:15:03[0]  Test: ./imfile-symlink.sh
------------------------------------------------------------
[inotify mode]
config rstb_64
4896_e3639ad4_.conf is:
     1  module(load="../plugins/imdiag/.libs/imdiag")
     2  global(inputs.timeout.shutdown="60000"
     3         default.action.queue.timeoutshutdown="20000"
     4         default.action.queue.timeoutEnqueue="20000")
     5  $MainmsgQueueTimeoutEnqueue 20000 # use legacy-style so that we can override if needed
     6  $IMDiagListenPortFileName rstb_644896_e3639ad4.imdiag.port
     7  $IMDiagServerRun 0
     8  $IMDiagAbortTimeout 580
     9  
    10  :syslogtag, contains, "rsyslogd"  ./rstb_644896_e3639ad4.started
    11  ###### end of testbench instrumentation part, test conf follows:
    12  
    13  # comment out if you need more debug info:
    14      global( debug.whitelist="on"
    15          debug.files=["imfile.c"])
    16  module(load="../plugins/imfile/.libs/imfile"
    17         mode="inotify" normalizePath="off")
    18  input(type="imfile" File="./rstb_644896_e3639ad4.input-symlink.log" Tag="file:"
    19      Severity="error" Facility="local7" addMetadata="on")
    20  input(type="imfile" File="./rstb_644896_e3639ad4.input.*.log" Tag="file:"
    21      Severity="error" Facility="local7" addMetadata="on")
    22  template(name="outfmt" type="list") {
    23      constant(value="HEADER ")
    24      property(name="msg" format="json")
    25      constant(value=", filename: ")
    26      property(name="$!metadata!filename")
    27      constant(value=", fileoffset: ")
    28      property(name="$!metadata!fileoffset")
    29      constant(value="\n")
    30  }
    31  if $msg contains "msgnum:" then
    32      action( type="omfile" file="rstb_644896_e3639ad4.out.log" template="outfmt")
rsyslogd: NOTE: RSYSLOG_DEBUG_TIMEOUTS_TO_STDERR activated
rsyslogd: imfile: no working or state file directory set, imfile will create state files in the current working directory (probably the root dir). Use global(workDirectory="/some/path") to set the working directory [v8.1905.0.master try https://www.rsyslog.com/e/2450 ]
main Q:Reg: worker start requested, num workers currently 0
main Q:Reg: wrkr start initiated with state 0, num workers now 1
rsyslog debug: main Q:Reg: worker 0x55ccdc047f60 started
rsyslog debug: main Q:Reg: started with state 3, num workers now 1
13:15:03[0]  rstb_644896_e3639ad4:.pid found, pid 22264
13:15:03[1]  rsyslogd startup msg seen, pid  22264
imdiag port: 34101
creating rstb_644896_e3639ad4.targets/2.log
+ ./inputfilegen -m 1 -i 1
+ ls -l rstb_644896_e3639ad4.targets/2.log
-rw-r--r-- 1 buildbot buildbot 17 Apr 30 13:15 rstb_644896_e3639ad4.targets/2.log
+ ln -sv rstb_644896_e3639ad4.targets/2.log rsyslog-link.2.log
'rsyslog-link.2.log' -> 'rstb_644896_e3639ad4.targets/2.log'
+ ln -sv rsyslog-link.2.log rstb_644896_e3639ad4.input.2.log
'rstb_644896_e3639ad4.input.2.log' -> 'rsyslog-link.2.log'
++ tb_timestamp
+++ date +%H:%M:%S
+++ date +%s
++ printf '%s[%s] ' 13:15:04 1
+ printf '%s generated file %s\n' '13:15:04[1] ' 2
13:15:04[1]  generated file 2
+ ls -l rsyslog-link.2.log
lrwxrwxrwx 1 buildbot buildbot 34 Apr 30 13:15 rsyslog-link.2.log -> rstb_644896_e3639ad4.targets/2.log
+ set +x
content_check_with_count success, "HEADER msgnum:000000" occured 2 times
creating rstb_644896_e3639ad4.targets/3.log
+ ./inputfilegen -m 1 -i 2
+ ls -l rstb_644896_e3639ad4.targets/3.log
-rw-r--r-- 1 buildbot buildbot 17 Apr 30 13:15 rstb_644896_e3639ad4.targets/3.log
+ ln -sv rstb_644896_e3639ad4.targets/3.log rsyslog-link.3.log
'rsyslog-link.3.log' -> 'rstb_644896_e3639ad4.targets/3.log'
+ ln -sv rsyslog-link.3.log rstb_644896_e3639ad4.input.3.log
'rstb_644896_e3639ad4.input.3.log' -> 'rsyslog-link.3.log'
++ tb_timestamp
+++ date +%H:%M:%S
+++ date +%s
++ printf '%s[%s] ' 13:15:04 1
+ printf '%s generated file %s\n' '13:15:04[1] ' 3
13:15:04[1]  generated file 3
+ ls -l rsyslog-link.3.log
lrwxrwxrwx 1 buildbot buildbot 34 Apr 30 13:15 rsyslog-link.3.log -> rstb_644896_e3639ad4.targets/3.log
+ set +x
content_check_with_count success, "HEADER msgnum:000000" occured 3 times
creating rstb_644896_e3639ad4.targets/4.log
+ ./inputfilegen -m 1 -i 3
+ ls -l rstb_644896_e3639ad4.targets/4.log
-rw-r--r-- 1 buildbot buildbot 17 Apr 30 13:15 rstb_644896_e3
639ad4.targets/4.log
+ ln -sv rstb_644896_e3639ad4.targets/4.log rsyslog-link.4.log
'rsyslog-link.4.log' -> 'rstb_644896_e3639ad4.targets/4.log'
+ ln -sv rsyslog-link.4.log rstb_644896_e3639ad4.input.4.log
'rstb_644896_e3639ad4.input.4.log' -> 'rsyslog-link.4.log'
++ tb_timestamp
+++ date +%H:%M:%S
+++ date +%s
++ printf '%s[%s] ' 13:15:04 1
+ printf '%s generated file %s\n' '13:15:04[1] ' 4
13:15:04[1]  generated file 4
+ ls -l rsyslog-link.4.log
lrwxrwxrwx 1 buildbot buildbot 34 Apr 30 13:15 rsyslog-link.4.log -> rstb_644896_e3639ad4.targets/4.log
+ set +x
content_check_with_count success, "HEADER msgnum:000000" occured 4 times
creating rstb_644896_e3639ad4.targets/5.log
+ ./inputfilegen -m 1 -i 4
+ ls -l rstb_644896_e3639ad4.targets/5.log
-rw-r--r-- 1 buildbot buildbot 17 Apr 30 13:15 rstb_644896_e3639ad4.targets/5.log
+ ln -sv rstb_644896_e3639ad4.targets/5.log rsyslog-link.5.log
'rsyslog-link.5.log' -> 'rstb_644896_e3639ad4.targets/5.log'
+ ln -sv rsyslog-link.5.log rstb_644896_e3639ad4.input.5.log
'rstb_644896_e3639ad4.input.5.log' -> 'rsyslog-link.5.log'
++ tb_timestamp
+++ date +%H:%M:%S
+++ date +%s
++ printf '%s[%s] ' 13:15:04 1
+ printf '%s generated file %s\n' '13:15:04[1] ' 5
13:15:04[1]  generated file 5
+ ls -l rsyslog-link.5.log
lrwxrwxrwx 1 buildbot buildbot 34 Apr 30 13:15 rsyslog-link.5.log -> rstb_644896_e3639ad4.targets/5.log
+ set +x
content_check_with_count success, "HEADER msgnum:000000" occured 5 times
creating rstb_644896_e3639ad4.targets/6.log
+ ./inputfilegen -m 1 -i 5
+ ls -l rstb_644896_e3639ad4.targets/6.log
-rw-r--r-- 1 buildbot buildbot 17 Apr 30 13:15 rstb_644896_e3639ad4.targets/6.log
+ ln -sv rstb_644896_e3639ad4.targets/6.log rsyslog-link.6.log
'rsyslog-link.6.log' -> 'rstb_644896_e3639ad4.targets/6.log'
+ ln -sv rsyslog-link.6.log rstb_644896_e3639ad4.input.6.log
'rstb_644896_e3639ad4.input.6.log' -> 'rsyslog-link.6.log'
++ tb_timestamp
+++ date +%H:%M:%S
+++ date +%s
++ printf '%s[%s] ' 13:15:04 1
+ printf '%s generated file %s\n' '13:15:04[1] ' 6
13:15:04[1]  generated file 6
+ ls -l rsyslog-link.6.log
lrwxrwxrwx 1 buildbot buildbot 34 Apr 30 13:15 rsyslog-link.6.log -> rstb_644896_e3639ad4.targets/6.log
+ set +x
content_check_with_count success, "HEADER msgnum:000000" occured 6 times
creating rstb_644896_e3639ad4.targets/7.log
+ ./inputfilegen -m 1 -i 6
+ ls -l rstb_644896_e3639ad4.targets/7.log
-rw-r--r-- 1 buildbot buildbot 17 Apr 30 13:15 rstb_644896_e3639ad4.targets/7.log
+ ln -sv rstb_644896_e3639ad4.targets/7.log rsyslog-link.7.log
'rsyslog-link.7.log' -> 'rstb_644896_e3639ad4.targets/7.log'
+ ln -sv rsyslog-link.7.log rstb_644896_e3639ad4.input.7.log
'rstb_644896_e3639ad4.input.7.log' -> 'rsyslog-link.7.log'
++ tb_timestamp
+++ date +%H:%M:%S
+++ date +%s
++ printf '%s[%s] ' 13:15:04 1
+ printf '%s generated file %s\n' '13:15:04[1] ' 7
13:15:04[1]  generated file 7
+ ls -l rsyslog-link.7.log
lrwxrwxrwx 1 buildbot buildbot 34 Apr 30 13:15 rsyslog-link.7.log -> rstb_644896_e3639ad4.targets/7.log
+ set +x
content_check_with_count success, "HEADER msgnum:000000" occured 7 times
creating rstb_644896_e3639ad4.targets/8.log
+ ./inputfilegen -m 1 -i 7
+ ls -l rstb_644896_e3639ad4.targets/8.log
-rw-r--r-- 1 buildbot buildbot 17 Apr 30 13:15 rstb_644896_e3639ad4.targets/8.log
+ ln -sv rstb_644896_e3639ad4.targets/8.log rsyslog-link.8.log
'rsyslog-link.8.log' -> 'rstb_644896_e3639ad4.targets/8.log'
+ ln -sv rsyslog-link.8.log rstb_644896_e3639ad4.input.8.log
'rstb_644896_e3639ad4.input.8.log' -> 'rsyslog-link.8.log'
++ tb_timestamp
+++ date +%H:%M:%S
+++ date +%s
++ printf '%s[%s] ' 13:15:04 1
+ printf '%s generated file %s\n' '13:15:04[1] ' 8
13:15:04[1]  generated file 8
+ ls -l rsyslog-link.8.log
lrwxrwxrwx 1 buildbot buildbot 34 Apr 30 13:15 rsyslog-link.8.log -> rstb_644896_e3639ad4.targets/8.log
+ set +x
content_check_with_count success, "HEADER msgnum:000000" occured 8 times
creating rstb_644896_e3639ad4.targets/9.log
+ ./inputfilegen -m 1 -i 8
+ ls -l rstb_644896_e3639ad4.targets/9.log
-rw-r--r-- 1 buildbot buildbot 17 Apr 30 13:15 rstb_644896_e3639ad4.targets/9.log
+ ln 
-sv rstb_644896_e3639ad4.targets/9.log rsyslog-link.9.log
'rsyslog-link.9.log' -> 'rstb_644896_e3639ad4.targets/9.log'
+ ln -sv rsyslog-link.9.log rstb_644896_e3639ad4.input.9.log
'rstb_644896_e3639ad4.input.9.log' -> 'rsyslog-link.9.log'
++ tb_timestamp
+++ date +%H:%M:%S
+++ date +%s
++ printf '%s[%s] ' 13:15:04 1
+ printf '%s generated file %s\n' '13:15:04[1] ' 9
13:15:04[1]  generated file 9
+ ls -l rsyslog-link.9.log
ls: cannot access 'rsyslog-link.9.log': No such file or directory
+ set +x
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count hav
e 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
content_check_with_count have 8, wait for 9 times (8 lines), msg: HEADER msgnum:000000
Shutting down instance 1
imdiag: wait q_empty: qsize 0 nempty 1
imdiag: wait q_empty: qsize 0 nempty 2
imdiag: wait q_empty: qsize 0 nempty 3
imdiag: wait q_empty: qsize 0 nempty 4
imdiag: wait q_empty: qsize 0 nempty 5
imdiag: wait q_empty: qsize 0 nempty 6
imdiag[34101]: mainqueue empty
rsyslogd debug: info: trying to cooperatively stop input ../plugins/imdiag/.libs/imdiag, timeout 60000 ms
rsyslogd debug: info: trying to cooperatively stop input imfile, timeout 60000 ms
rsyslog debug: main Q:Reg/w0: enter WrkrExecCleanup
rsyslog debug: 0x55ccdc0480f0: worker exiting
rsyslog debug: main Q:Reg/w0: thread joined
13:16:07[64]  wait on shutdown of 22264
content_check_with_count failed, expected "HEADER msgnum:000000" to occur 9 times, but found it 8 times
file rstb_644896_e3639ad4.out.log content is:
     1  HEADER msgnum:00000000:, filename: ./rstb_644896_e3639ad4.input-symlink.log, fileoffset: 0
     2  HEADER msgnum:00000001:, filename: ./rstb_644896_e3639ad4.input.2.log, fileoffset: 0
     3  HEADER msgnum:00000002:, filename: ./rstb_644896_e3639ad4.input.3.log, fileoffset: 0
     4  HEADER msgnum:00000003:, filename: ./rstb_644896_e3639ad4.input.4.log, fileoffset: 0
     5  HEADER msgnum:00000004:, filename: ./rstb_644896_e3639ad4.input.5.log, fileoffset: 0
     6  HEADER msgnum:00000005:, filename: ./rstb_644896_e3639ad4.input.6.log, fileoffset: 0
     7  HEADER msgnum:00000006:, filename: ./rstb_644896_e3639ad4.input.7.log, fileoffset: 0
     8  HEADER msgnum:00000007:, filename: ./rstb_644896_e3639ad4.input.8.log, fileoffset: 0
reporting failure to http://build.rsyslog.com/testbench-failedtest.php
2019-04-30 13:16:08 URL:http://build.rsyslog.com/testbench-failedtest.php?Testname=imfile-symlink.sh&Testenv=rsyslog+docker-ubuntu18-codecov&Testmachine=23b8ac44012b&exitcode=1&logurl=https%3A%2F%2Fbuild.rsyslog.com%2F%23builders%2F181%2Fbuilds%2F2094&rndstr=jnxv8i34u78fg23 [31/31] -> "/dev/null" [1]
13:16:08[65]  FAIL: Test ./imfile-symlink.sh (took 65 seconds)
FAIL imfile-symlink.sh (exit status: 1)
rgerhards picture rgerhards on 6 May 2019

@jvymazal I think I finally know what happens! Have a look (only relevant part):

+ ./inputfilegen -m 1 -i 8
+ ls -l rstb_644896_e3639ad4.targets/9.log
-rw-r--r-- 1 buildbot buildbot 17 Apr 30 13:15 rstb_644896_e3639ad4.targets/9.log
+ ln 
-sv rstb_644896_e3639ad4.targets/9.log rsyslog-link.9.log
'rsyslog-link.9.log' -> 'rstb_644896_e3639ad4.targets/9.log'
+ ln -sv rsyslog-link.9.log rstb_644896_e3639ad4.input.9.log
'rstb_644896_e3639ad4.input.9.log' -> 'rsyslog-link.9.log'
+ ls -l rsyslog-link.9.log
ls: cannot access 'rsyslog-link.9.log': No such file or directory

As we can see, the symlink is created - but then it disappears. The reason is inside the framework! Upon (every!) test exit, rsyslog-link.*.log is deleted. So a parallel test ran the exit procedure just at the "right" time and removed that file.

So the root cause is that we did not notice that the test was not fully converted to support parallel test runs. I'll fix this. The good news is that this issue is NOT rooted in an actual code bug.

rgerhards picture rgerhards on 6 May 2019

That is good news indeed, great catch, many thanks for the debugging effort.

jvymazal picture jvymazal on 6 May 2019
❤1

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

lock[bot] picture lock[bot] on 24 Dec 2019
Was this page helpful?
0 / 5 - 0 ratings

Related issues

rmunn picture rmunn  路  5Comments
shannider picture shannider  路  4Comments
JPvRiel picture JPvRiel  路  10Comments
selivan picture selivan  路  7Comments
mashayev picture mashayev  路  9Comments