#970355 syslog-ng : segfault at 0 ip 00007fa46a2bf7b2 sp 00007ffed353fb30 error 6 in libsyslog-ng-3.19.so.0.0.0[7fa46a2a9000+5a000]

Package:
syslog-ng
Source:
syslog-ng
Submitter:
Jean-Marc LACROIX
Date:
2026-10-19 08:21:02 UTC
Severity:
normal
Tags:
#970355#5
Date:
2020-09-15 06:30:37 UTC
From:
To:
Dear maintainers,

On amd64, i have following error....


==> /var/log/syslog-ng/current_logs/BY_FACILITY.kern.notice.log <==
2020-09-15T08:25:53+02:00 s_dev_kernel_kmsg@asus-190 kernel:
6,35313,87037029084,-;syslog-ng[10311]: segfault at 0 ip
00007fa46a2bf7b2 sp 00007ffed353fb30 error 6 in
libsyslog-ng-3.19.so.0.0.0[7fa46a2a9000+5a000]
2020-09-15T08:25:53+02:00 s_dev_kernel_kmsg@asus-190 kernel:
6,35314,87037029092,-;Code: e8 c3 9b fe ff 4c 89 e7 e8 eb dc fe ff 48 89
c7 e8 23 ca fe ff e9 15 ff ff ff 66 0f 1f 44 00 00 48 8b 83 f0 00 00 00
48 89 df <c7> 00 00 00 00 00 48 83 c4 08 5b 5d 41 5c 41 5d e9 b9 fc ff ff 66

About the curent configuration, there is no disc full...
ansible@asus-190:~$ df
Sys. de fichiers                      blocs de 1K   Utilisé Disponible
Uti% Monté sur
udev                                      6015136         0    6015136
0% /dev
tmpfs                                     1213460      2924    1210536
1% /run
/dev/mapper/vg_debian-lv_rootfs_crypt      927000    134336     728360
16% /
/dev/mapper/vg_debian-lv_usr              7511832   5714960    1434140
80% /usr
tmpfs                                        5120         4       5116
1% /run/lock
tmpfs                                     2426900     57124    2369776
3% /dev/shm
/dev/mapper/vg_debian-lv_boot              463826    193086     242273
45% /boot
/dev/sda2                                   98304     39534      58770
41% /boot2/efi
/dev/sdb1                                  191551      5199     186352
3% /boot/efi
/dev/sdb5                                 2817056   1688848     965392
64% /debian_rescue
/dev/mapper/vg_debian-lv_home            80388420  74191172    2894992
97% /home
/dev/mapper/vg_debian-lv_tmp               943128     82076     795928
10% /tmp
/dev/mapper/vg_debian-lv_var               860591      7183     808724
1% /var
/dev/mapper/vg_debian-lv_var_cache         863632    140484     667980
18% /var/cache
/dev/mapper/vg_debian-lv_var_lib           959909     69128     842002
8% /var/lib
/dev/mapper/vg_debian-lv_var_lib_apt      1057092    431004     563584
44% /var/lib/apt
/dev/mapper/vg_debian-lv_var_log           560120    225992     293132
44% /var/log
cgroup                                    6067296         0    6067296
0% /sys/fs/cgroup
/dev/sde3                               862818100 120357724  698561908
15% /mnt/backup
ansible@asus-190:~$

My syslog configuration is in attached file

Thanks in advance for your help

Jean-Marc

#970355#10
Date:
2020-09-16 08:16:49 UTC
From:
To:
Hi Jean-Marc,

Please check if a core file is available related to the segmentation
fault. If there is any please make it available for me/us.

Also, can you run syslog-ng-debun with the -r parameter and send the
generated report bundle?

Another question, is the segmentation fault reproducible? Is syslog-ng
crashing frequently?

#970355#15
Date:
2020-09-30 14:15:10 UTC
From:
To:


Dear Maintainer, hello Jean-Marc,
I tried to get some more information from the kernel message,
but found just that it points to this function [1].
There I assume that the argument s is a null pointer.

Bug I fear that without a proper backtrace this might not yet enough to fix the fault.

For getting a coredump or using gdb you might have a look at [2].
For the latter you might want to first install the package syslog-ng-dbg.

Kind regards,
Bernhard


[1] https://sources.debian.org/src/syslog-ng/3.19.1-5/lib/logproto/logproto-server.h/#L163

[2] https://wiki.debian.org/HowToGetABacktrace#Core_dump
https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols

#970355#22
Date:
2020-09-16 08:15:41 UTC
From:
To:
Hi Jean-Marc,

Please check if a core file is available related to the segmentation
fault. If there is any please make it available for me/us.

Also, can you run syslog-ng-debun with the -r parameter and send the
generated report bundle?

Another question, is the segmentation fault reproducible? Is syslog-ng
crashing frequently?

#970355#29
Date:
2026-10-18 20:42:03 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
syslog-ng, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 970355@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
SZALAY Attila <sasa@debian.org> (supplier of updated syslog-ng package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sun, 18 Oct 2026 20:33:27 +0100
Source: syslog-ng
Architecture: source
Version: 4.12.0-1
Distribution: unstable
Urgency: medium
Maintainer: syslog-ng maintainers <syslog-ng-maintainers@alioth-lists.debian.net>
Changed-By: SZALAY Attila <sasa@debian.org>
Closes: 831908 833283 844372 970355 992428 996246 1050692 1111518 1138428 1143061
Changes:
 syslog-ng (4.12.0-1) unstable; urgency=medium
 .
   * New upstream version 4.12.0 (Closes: #1143061, #1138428)
   * Clean up old and obsolated bugs (Closes: #831908, #844372, #970355, #992428, #996246)
   * Prepare new temporary release
   * Update debian patches
   * Dropping removed SCL modules
   * Re-enable secure logging module
   * Add new SCL config files to the syslog-ng-scl module
   * debian: Migrate legacy syslog-ng configs on upgrade (Closes: #833283)
   * debian: Update default configs to 4.12 (Closes: #1050692)
   * debian: Fix init script LSB header.
     Thanks to Andrew Bower <andrew@bower.uk> (Closes: #1111518)
   * Commenting about the GRPC module into the debian/README.source
Checksums-Sha1:
 301a2b61b3759e8d7297a24249736a5f8100ea84 4299 syslog-ng_4.12.0-1.dsc
 b5b0514b17f66a835a07713ea4307b91b2b199b2 2491465 syslog-ng_4.12.0.orig.tar.gz
 50cdfcccc94a08e6a082ffe114b8d03637a0a463 47660 syslog-ng_4.12.0-1.debian.tar.xz
 0672b083121e98c2b1283c699c7a417241c367a6 18385 syslog-ng_4.12.0-1_amd64.buildinfo
Checksums-Sha256:
 ae813e775eb8508b26b22ed764e8fdd9d3e89555f9f70d852eb9b6739914e20e 4299 syslog-ng_4.12.0-1.dsc
 94c88cb6d23d95c82a25366ae5455e6b0854716f27ab8f9288bdc7983188a381 2491465 syslog-ng_4.12.0.orig.tar.gz
 549d8c74f837497531d3a0ebab7ad33939ad2e0c361c94d53a6e74fc93f59d9b 47660 syslog-ng_4.12.0-1.debian.tar.xz
 cd30df305354247739c8b4c1ee30801f1f520bc2ddf8bc2bb94160c863f93cfd 18385 syslog-ng_4.12.0-1_amd64.buildinfo
Files:
 4dcf4cbc3937264e40a5873abf0a6337 4299 admin optional syslog-ng_4.12.0-1.dsc
 bc6bf2abe2705ac7e8daa36118c61785 2491465 admin optional syslog-ng_4.12.0.orig.tar.gz
 406376180601ff6f9dd34d72393a9e59 47660 admin optional syslog-ng_4.12.0-1.debian.tar.xz
 d2a6677d824c8d83d7e03603b8e60815 18385 admin optional syslog-ng_4.12.0-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJEBAEBCgAuFiEEDLxdlTMbVcF2xVjk+A0hGpn97vgFAmrVIYYQHHNhc2FAZGVi
aWFuLm9yZwAKCRD4DSEamf3u+FRtD/oDTped4HVDnt+MZ8LfHlh4fyzx8BTOD/Sk
Gvc9uFp73zoS+RMSm49LRAK9nZojJd7L3WLC48WQk7wCDFLQ6nwhttinJqO+fWEK
SGS6PEqDH5+m8nqW09C/r3zbAy3ydSoiNXncy6qKcn5LD/UVaqH8ekFKn/4H2Bfx
hD4SsQaB27mZULNCVSm0qex1P0qwo0i/wrjMJj0Nq9lveNkidE4pUYh6xCGI2ff/
eQ9I5zAZCY2PJXxIXetN8W32d/J1bS7Yutx46h9xbr6ZZ8yJDiSeU5ik0iiTFtcA
/A2LgxBkwI5NY92yeOSJ+3KCqM0DcFwy/RdU7abzTSJBoc5q6WT6KdxxlYUgOvs2
p3FLbtQwP9QjXzb1SUakVYFPGjbjOfGyxd2Pf9Miq6NaduaE/gBqXPoY+kx8dX4U
rUWpBDBEob5Z2J/LR1WP/YrgFIEi2Ds2MYEsNxQWdZUkdL11pRIb772jbTTe49Uk
RWhCJfCinBsTKO+4SWvLLEwLY9Q3w/qufT0d721ff0ll/fWjHREDJEoaoKbtvq0E
r1pox2QQF494gPwiOJXLPJCjzjFi8vY411uSv9LmsOrUGB0jozUQcYxq1xzO/FLo
3yO9jbiXZoYoHWoafsxpe0IvvU5VIBG5glC0MdgiTArNk4oCA2zJ14qQ70l5eSHh
ARASRpJamg==
=OkXZ
-----END PGP SIGNATURE-----

#970355#34
Date:
2026-10-19 08:19:09 UTC
From:
To:
Dears mainteners,

Please find bellow more information on recent Debian . Initial issue is
always here ...


ansible@hn-asusgl752-400:~$ uname -a
Linux hn-asusgl752-400 7.1.8+deb14.1-amd64 #1 SMP PREEMPT_DYNAMIC Debian
7.1.8-2 (2026-08-15) x86_64 GNU/Linux
ansible@hn-asusgl752-400:~$ cat /etc/debian_version
13.7
ansible@hn-asusgl752-400:~$


  ansible@hn-asusgl752-400:~$ apt policy syslog-ng
syslog-ng:
   Installé : 4.8.1-5+deb13u1
   Candidat : 4.8.1-5+deb13u1
  Table de version :
      4.8.1-7 80
          80 http://ftp.de.debian.org/debian forky/main amd64 Packages
  *** 4.8.1-5+deb13u1 500
         500 http://ftp.de.debian.org/debian trixie/main amd64 Packages
         100 /var/lib/dpkg/status
      3.38.1-5+deb12u1 90
          90 http://ftp.de.debian.org/debian bookworm/main amd64 Packages
ansible@hn-asusgl752-400:~$



  ansible@hn-asusgl752-400:~$  sudo syslog-ng-debun -r

Syslog-NG DEBUg buNdle generator




Start environment detection




Linux-type FHS detected




Distributor ID: Debian



Description:    Debian GNU/Linux 13 (trixie)




Release:        13
Codename:       trixie

Operating System Name: Linux

Debian specific checks
Check package files integrity
Package syslog-ng files are intact
??5?????? c /etc/default/syslog-ng
??5?????? c /etc/logrotate.d/syslog-ng
missing     /etc/syslog-ng/patterndb.d
missing     /etc/syslog-ng/python
missing   c /etc/syslog-ng/python/README.md
??5?????? c /etc/syslog-ng/syslog-ng.conf
Package syslog-ng-core files are intact
Package syslog-ng-mod-mongodb files are intact
Package syslog-ng-mod-sql files are intact
Package syslog-ng-scl files are intact
list syslog-related packages

Start general info collection
System's full uname: Linux hn-asusgl752-400 7.1.8+deb14.1-amd64 #1 SMP
PREEMPT_DYNAMIC Debian 7.1.8-2 (2026-08-15) x86_64 GNU/Linux
Getting network-interface information: Success
Getting network routes: Success
Getting DNS resolution-related information: Done
List all processes
Mount and disk free info collection
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument

Start Syslog-specific info collection
Copy configuration files from /etc/syslog-ng
75 blocks
Copy SCL configuration files
309 blocks
Gathering PKI information... done.
SVpid: 7811 SNGpid: 7812 Chpids:
Syslog-ng's exact version: syslog-ng 4 (4.8.1)
/usr/sbin/syslog-ng-ctl stats
/usr/sbin/syslog-ng-ctl query get *
/usr/sbin/syslog-ng-ctl show-license-info
/usr/sbin/syslog-ng-ctl credentials status
32 blocks
dpkg-query: no path found matching pattern
/lib/x86_64-linux-gnu/libglib-2.0.so.0
dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libc.so.6
dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libm.so.6
dpkg-query: no path found matching pattern
/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libcap.so.2
dpkg-query: no path found matching pattern
/lib/x86_64-linux-gnu/libpcre2-8.so.0
dpkg-query: no path found matching pattern
/lib/x86_64-linux-gnu/libivykis.so.0
dpkg-query: no path found matching pattern
/lib/x86_64-linux-gnu/libjson-c.so.5
dpkg-query: no path found matching pattern
/lib/x86_64-linux-gnu/libsystemd.so.0
dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libssl.so.3
dpkg-query: no path found matching pattern
/lib/x86_64-linux-gnu/libcrypto.so.3
dpkg-query: no path found matching pattern
/lib/x86_64-linux-gnu/libatomic.so.1
dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libz.so.1
dpkg-query: no path found matching pattern
/lib/x86_64-linux-gnu/libzstd.so.1
dpkg-query: package 'diversion' is not installed and no information is
available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
dpkg-query: package 'by' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
dpkg-query: package 'from' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
Detecting init system: falling back to SystemV init style...
Generating second batch of statistics

/usr/sbin/syslog-ng-ctl stats
/usr/sbin/syslog-ng-ctl query get *

Generating hashes... done.
Debug Bundle generation: Done.
tar: ./var/syslog-ng.ctl: socket ignored
Terminating live message watcher:



Furthermore ...
Still


1007537.810115] syslog-ng[8019]: segfault at 0 ip 00007fe8b66885bf sp
00007ffcc8d50970 error 6 in
libsyslog-ng-3.28.so.0.0.0[475bf,7fe8b6671000+64000] likely on CPU 1
(core 1, socket 0)
[1007537.810160] Code: 00 48 85 c0 74 05 48 89 ea ff d0 f6 45 04 01 74
32 0f b6 85 60 02 00 00 a8 04 0f 85 ab 00 00 00 48 8b 85 68 01 00 00 48
89 ef <c7> 00 00 00 00 00 48 83 c4 08 5d 41
5c e9 0f fc ff ff 0f 1f 80 00
[1007603.488577] syslog-ng[9963]: segfault at 0 ip 00007fe8b66885bf sp
00007ffcc8d50970 error 6 in
libsyslog-ng-3.28.so.0.0.0[475bf,7fe8b6671000+64000] likely on CPU 1
(core 1, socket 0)
[1007603.488592] Code: 00 48 85 c0 74 05 48 89 ea ff d0 f6 45 04 01 74
32 0f b6 85 60 02 00 00 a8 04 0f 85 ab 00 00 00 48 8b 85 68 01 00 00 48
89 ef <c7> 00 00 00 00 00 48 83 c4 08 5d 41
5c e9 0f fc ff ff 0f 1f 80 00










Best regards