Package: rsyslog
Version: 8.2302.0-1
Severity: normal
Tags: patch upstream
X-Debbugs-Cc: arul.jenis...@gmail.com

Dear Maintainer,

   * What led up to the situation?
     configuring ipv6 address for a hostname in /etc/hosts and ipv4 target
     address in rsyslog.conf action.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
       Steps to recreate
       1. Edit /etc/hosts file and add the following line
           fe80::2204:fff:fef7:3dbe dns6

       2. Edit /etc/rsyslog.conf and add the following two lines.

        $template MyFormat,"<%pri%>1 %timegenerated:::date-rfc3339%
        %hostname% %app-name% %procid% %msgid% %structured-data%
        %%!msg1%"
           *.info action(type="omfwd" Target="dns6" Address="100.1.2.61"
           Device="mgmt" Port="514" Protocol="udp" Template="MyFormat")

       3. run rsyslogd daemon and observe crash.
               root@docker-core:/# /usr/sbin/rsyslogd -n    
                         Segmentation fault

   * What was the outcome of this action?
      rsyslogd crashes with the following trace
        (gdb) bt
        #0  0x00007ffff79e1b90 in freeaddrinfo () from
                /lib/x86_64-linux-gnu/libc.so.6
        #1  0x0000555555570aa9 in doTryResume (pWrkrData=0x7fffe000f360) at
                omfwd.c:909
        #2  0x00005555555b94ef in actionDoRetry
                (pThis=pThis@entry=0x55555562c7a0, 
pWti=pWti@entry=0x55555565e150) at
                ../action.c:800
        #3  0x00005555555ba13b in actionTryResume (pWti=0x55555565e150,
                pThis=0x55555562c7a0) at ../action.c:917
        #4  actionPrepare (pThis=0x55555562c7a0, pWti=0x55555565e150) at
                ../action.c:944
        #5  0x00005555555bbc72 in processMsgMain
                (pAction=pAction@entry=0x55555562c7a0, 
pWti=pWti@entry=0x55555565e150,
                pMsg=pMsg@entry=0x7fffec0016d0, 
ttNow=ttNow@entry=0x7ffff69f98a0) at
                ../action.c:1527
        #6  0x00005555555bc144 in doSubmitToActionQ (pAction=0x55555562c7a0,
                pWti=0x55555565e150, pMsg=0x7fffec0016d0) at ../action.c:1699
        #7  0x00005555555b3f26 in execAct (stmt=0x55555562c130,

   * What outcome did you expect instead?
        rsyslogd can print a error log but shouldn't crash.


-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-148-generic (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages rsyslog depends on:
ii  libc6         2.36-9+deb12u1
ii  libestr0      0.1.11-1
ii  libfastjson4  1.2304.0-1
ii  liblognorm5   2.0.6-4
ii  libsystemd0   252.12-1~deb12u1
ii  libuuid1      2.38.1-5+b1
ii  libzstd1      1.5.4+dfsg2-5
ii  zlib1g        1:1.2.13.dfsg-1

Versions of packages rsyslog recommends:
ii  logrotate  3.21.0-1

Versions of packages rsyslog suggests:
pn  rsyslog-doc                       <none>
pn  rsyslog-gssapi                    <none>
pn  rsyslog-mongodb                   <none>
pn  rsyslog-mysql | rsyslog-pgsql     <none>
pn  rsyslog-openssl | rsyslog-gnutls  <none>
pn  rsyslog-relp                      <none>

-- no debconf information

  • Bug#1053193: rsyslogd: crashes on freeaddrinfo() Arul Jeniston Mc

Reply via email to