Yup, these are errors and I have asked Tim (whom I am currently mentoring towards rsyslog development in the long term) to fix them. HOWEVER, it is correct that the testbench does not throw an error, because the config is to NOT abort on errors. So in that regard it works like it should.
Tim will be fixing the tests and add tests that match what the test currently did (if this is needed). Rainer 2015-01-19 5:03 GMT+01:00 Thomas D. <[email protected]>: > Hi, > > I noticed the following output from the testbench which looks like an > not detected error: > > > > [validation-run.sh]: testing configuraton validation > > > > testing a failed configuration verification run > > > > rsyslogd: the -u command line option will go away soon. > > > > For the 0x02 bit, please use the -C option instead.rsyslogd: version > 8.8.0.master, config validation run (level 1), master config > ./testsuites/invalid.conf > > > > rsyslogd: invalid or yet-unknown config file command 'invalid' - have > you forgotten to load a module? [try http://www.rsyslog.com/e/3003 ] > > > > rsyslogd: CONFIG ERROR: there are no active actions configured. Inputs > will run, but no output whatsoever is created. [try > http://www.rsyslog.com/e/2103 ] > > > > rsyslogd: run failed with error -2103 (see rsyslog.h or try > http://www.rsyslog.com/e/2103 to learn what that number means) > > > > testing a valid config verification run > > > > rsyslogd: the -u command line option will go away soon. > > > > For the 0x02 bit, please use the -C option instead.rsyslogd: version > 8.8.0.master, config validation run (level 1), master config > ./testsuites/valid.conf > > > > rsyslogd: End of config validation run. Bye. > > > > testing empty config file > > > > rsyslogd: the -u command line option will go away soon. > > > > For the 0x02 bit, please use the -C option instead.rsyslogd: version > 8.8.0.master, config validation run (level 1), master config /dev/null > > > > rsyslogd: CONFIG ERROR: there are no active actions configured. Inputs > will run, but no output whatsoever is created. [try > http://www.rsyslog.com/e/2103 ] > > > > rsyslogd: run failed with error -2103 (see rsyslog.h or try > http://www.rsyslog.com/e/2103 to learn what that number means) > > > > SUCCESS: validation run tests > > > > PASS: validation-run.sh > > > > > =============================================================================== > > > > TEST: [asynwr_simple.sh]: simple test for async file writing > > > > rsyslogd: invalid or yet-unknown config file command > 'OMFileFlushIOBufferSize' - have you forgotten to load a module? [try > http://www.rsyslog.com/e/3003 ] > > > > rsyslogd started with pid 17775 > > > > 00001 open connections > > > > starting run 1 > > > > Sending 35555 messages. > > > > 00035555 messages sent > > > > runtime: 0.054 > > > > 00001 close connections > > > > End of tcpflood Run > > > > imdiag[13500]: mainqueue empty > > > > > ------------------------------------------------------------------------------- > > > > PASS: asynwr_simple.sh > > > > > =============================================================================== > > > > TEST: [asynwr_timeout.sh]: test async file writing timeout writes > > > > rsyslogd: invalid or yet-unknown config file command > 'OMFileFlushIOBufferSize' - have you forgotten to load a module? [try > http://www.rsyslog.com/e/3003 ] > > > > rsyslogd started with pid 17821 > > > > 00001 open connections > > > > starting run 1 > > > > Sending 35555 messages. > > > > 00035555 messages sent > > > > runtime: 0.060 > > > > 00001 close connections > > > > End of tcpflood Run > > > > imdiag[13500]: mainqueue empty > > > > > ------------------------------------------------------------------------------- > > > > PASS: asynwr_timeout.sh > > TEST: [asynwr_deadlock.sh]: a case known to have caused a deadlock in > the past > > > > rsyslogd: invalid or yet-unknown config file command > 'OMFileFlushIOBufferSize' - have you forgotten to load a module? [try > http://www.rsyslog.com/e/3003 ] > > > > rsyslogd started with pid 18086 > > > > 00001 open connections > > > > starting run 1 > > > > Sending 1 messages. > > > > 00000001 messages sent > > > > runtime: 0.000 > > > > 00001 close connections > > > > End of tcpflood Run > > > > processing must continue soon > > > > imdiag[13500]: mainqueue empty > > > > > ------------------------------------------------------------------------------- > > > > PASS: asynwr_deadlock.sh > > > > -Thomas > _______________________________________________ > 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. > _______________________________________________ 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.

