I hit a build-time test issue, test ./imdtls-basic-tlscommands.sh is
failing:
$ ./imdtls-basic-tlscommands.sh
testbench: TZ env var not set, setting it to UTC
------------------------------------------------------------
19:45:59[0] Test: ./imdtls-basic-tlscommands.sh
------------------------------------------------------------
config rstb_378687_9480e098nhaE_.conf is:
1 module(load="../plugins/imdiag/.libs/imdiag"
2 listenportfilename="rstb_378687_9480e098nhaE.imdiag.port"
3 serverrun="0"
4 aborttimeout="580"
5
properterminationfile="/home/ubuntu/git/packages/rsyslog/rsyslog/tests/rstb_378687_9480e098nhaE.proper-termination"
6 mainmsgqueuetimeoutshutdown="10000"
7 mainmsgqueuetimeoutenqueue="30000"
8 inputshutdowntimeout="60000"
9 defaultactionqueuetimeoutshutdown="20000"
10 defaultactionqueuetimeoutenqueue="30000")
11 global(debug.abortOnProgramError="on")
12 # Capture rsyslogd own messages (startup, shutdown, errors) to the
.started
13 # file. Tests use this file to check for expected rsyslogd-internal
messages.
14 # This rule also ensures at least one output action exists in the
default
15 # ruleset, which is required by rsyslogd even when only inputs are
configured.
16 if $syslogtag contains "rsyslogd" then action(type="omfile"
file="./rstb_378687_9480e098nhaE.started")
17 ###### end of testbench instrumentation part, test conf follows:
18
19 global( defaultNetstreamDriverCAFile="./tls-certs/ca.pem"
20 defaultNetstreamDriverCertFile="./tls-certs/cert.pem"
21 defaultNetstreamDriverKeyFile="./tls-certs/key.pem"
22 )
23
24 module( load="../plugins/imdtls/.libs/imdtls" )
25 input( type="imdtls"
26
tls.tlscfgcmd="Protocol=ALL,-SSLv2,-SSLv3,-TLSv1,-TLSv1.1,-TLSv1.3
27 Options=Bugs"
28 port="0"
29 listenPortFileName="rstb_378687_9480e098nhaE.imdtls.port")
30
31 action(type="omfile" file="rstb_378687_9480e098nhaE.out.log")
rsyslogd: NOTE: RSYSLOG_DEBUG_TIMEOUTS_TO_STDERR activated
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 0x5c8cd083bc80 started
rsyslog debug: main Q:Reg: started with state 3, num workers now 1
19:45:59[0] rsyslogd startup indicator seen, pid 318211
waiting for file rstb_378687_9480e098nhaE.imdiag.port
imdiag port: 42067
waiting for file rstb_378687_9480e098nhaE.imdtls.port
exported: PORT_RCVR=54607
tcpflood: custom config set to 'Protocol=-ALL,TLSv1.3'
tcpflood: Successfully added Command Protocol:-ALL,TLSv1.3
[DEBUG] Init Session to 127.0.0.1:54607 ...
starting run 1
Sending 10 messages.
00000000 messages sent[DEBUG] Starting DTLS session ...
SSL_connect failed
tcpflood: openssl error 'initDTLSSess3' with error code=1
tcpflood: Unknown SSL Error in 'initDTLSSess3' (0), SSL_get_error: 1
tcpflood: initDTLSSess3 Errorstack: error:0A0000BF:SSL routines::no protocols
available
error during tcpflood on port 53185! But test continues...
19:45:59 Shutting down instance 1
imdiag: wait q_empty: qsize 0 nempty 1
imdiag[42067]: mainqueue empty
rsyslogd debug: info: trying to cooperatively stop input imdiag, timeout 60000
ms
rsyslogd debug: info: trying to cooperatively stop input imdtls, timeout 60000
ms
19:46:00[1] wait on shutdown of 318211
rsyslogd debug: input thread term: timeout expired waiting on thread imdtls
termination - canceling
rsyslog debug: main Q:Reg/w0: enter WrkrExecCleanup
rsyslog debug: 0x5c8cd0825330: worker exiting
rsyslog debug: main Q:Reg/w0: thread joined
content_check did not yet succeed
content_check did not yet succeed
============================================================
FILE "rstb_378687_9480e098nhaE.out.log" content:
1 2026-08-27T19:45:59.493922+00:00 s-rsyslog rsyslogd-2357: warning
during parsing file (null), on or before line 32: backward-compatible insecure
default in use: global(abortOnUncleanConfig="off"); use
global(compatibility.defaults.secure="strict") to enable the secure default
[v8.2608.0 try https://www.rsyslog.com/e/2357 ]
2 2026-08-27T19:45:59.497172+00:00 s-rsyslog rsyslogd: [origin
software="rsyslogd" swVersion="8.2608.0" x-pid="318211"
x-info="https://www.rsyslog.com";] start
3 2026-08-27T19:47:00.520161+00:00 s-rsyslog rsyslogd: [origin
software="rsyslogd" swVersion="8.2608.0" x-pid="318211"
x-info="https://www.rsyslog.com";] exiting on signal 15.
FAIL: content_check failed to find "OpenSSL Error Stack:"
Core dump policy:
ulimit -c: unlimited
kernel.core_pattern: |/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u
-g%g -F%F -- %E
kernel.core_uses_pid: 1
fs.suid_dumpable: 2
local generic core files: unreliable; core_pattern uses an external collector
INFO: skipping generic local core scan because core_pattern uses an external
collector
No owned rsyslogd core dumps found
=== Error Logs Collection ===
gather-check-logs.sh not found, collecting available logs manually...
No failed-tests.log found
not reporting failure as RSYSLOG_STATSURL is not set
19:47:00[61] FAIL: Test ./imdtls-basic-tlscommands.sh (took 61 seconds)
I ran it in resolute, and the expected rsyslog server logs are not there
in the stonking case. They are:
2026-08-27T21:02:11.416664+00:00 r-rsyslog rsyslogd: [origin
software="rsyslogd" swVersion="8.2512.0" x-pid="285153"
x-info="https://www.rsyslog.com";] start
2026-08-27T21:02:11.556628+00:00 r-rsyslog rsyslogd: SSL_ERROR_UNKNOWN Error in
'DTLSHandleSessions': 'error:00000000:lib(0)::reason(0)(0)' with ret=1,
errno=0(Success), sslapi='DTLSv1_listen' [v8.2512.0]
2026-08-27T21:02:11.556646+00:00 r-rsyslog rsyslogd: net_ossl:remote '(null)'
OpenSSL Error Stack: error:0A0000F4:SSL routines::unexpected message [v8.2512.0]
2026-08-27T21:02:11.556648+00:00 r-rsyslog rsyslogd: imdtls: DTLSv1_listen
failed for DTLS client [v8.2512.0]
2026-08-27T21:02:12.394599+00:00 r-rsyslog rsyslogd: [origin
software="rsyslogd" swVersion="8.2512.0" x-pid="285153"
x-info="https://www.rsyslog.com";] exiting on signal 15.
I'll manually setup this configuration and carefully run it under debugging to
see what is going on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2153351
Title:
Merge rsyslog from Debian for stonking cycle
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2153351/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
