[syslog-ng] Syslog-ng Crashes on CentOS Linux release 7.2.1511 (Core) - Segfaults

[Traiano Welcome]

Hi List

syslog-ng 3.5.6 fails to start up on a newly installed CentOS 7 server:

Environment details:

OS: 3.10.0-327.10.1.el7.x86_64
Distro: CentOS Linux release 7.2.1511 (Core)
Syslog-ng: syslog-ng-3.5.6-3.el7.x86_64

I'm doing a fresh install on CentOS linux and installing syslog ng from
epel-release repo. syslog-ng fails to start up via systemd as follows:

systemctl restart syslog-ng

Job for syslog-ng.service failed because a fatal signal was delivered to
the control process. See "systemctl status syslog-ng.service" and
"journalctl -xe" for details.

Looking at journalctl -xe output:


- Unit syslog-ng.service has failed.
--
-- The result is failed.

Dec 12 09:40:40 ip-172-31-23-167 systemd[1]: Unit syslog-ng.service entered
failed state.

Dec 12 09:40:40 ip-172-31-23-167 systemd[1]: syslog-ng.service failed.

Dec 12 09:40:40 ip-172-31-23-167 systemd[1]: syslog-ng.service holdoff time
over, scheduling restart.

Dec 12 09:40:40 ip-172-31-23-167 systemd[1]: Starting System Logger
Daemon...

-- Subject: Unit syslog-ng.service has begun start-up

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit syslog-ng.service has begun starting up.

Dec 12 09:40:40 ip-172-31-23-167 kernel: syslog-ng[9920]: segfault at 0 ip
(null) sp 00007fff5bbba5b8 error 14 in syslog-ng[400000+2000]

Dec 12 09:40:40 ip-172-31-23-167 systemd[1]: syslog-ng.service: main
process exited, code=killed, status=11/SEGV

Dec 12 09:40:40 ip-172-31-23-167 systemd[1]: Failed to start System Logger
Daemon.

-- Subject: Unit syslog-ng.service has failed

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[Balazs Scheidler]

This should be a useful post that CzanikP just posted:

https://www.balabit.com/blog/installing-latest-syslog-ng-on-rhel-and-other-rpm-distributions/

Post by Traiano Welcome
Hi List
OS: 3.10.0-327.10.1.el7.x86_64
Distro: CentOS Linux release 7.2.1511 (Core)
Syslog-ng: syslog-ng-3.5.6-3.el7.x86_64
I'm doing a fresh install on CentOS linux and installing syslog ng from
systemctl restart syslog-ng
Job for syslog-ng.service failed because a fatal signal was delivered to
the control process. See "systemctl status syslog-ng.service" and
"journalctl -xe" for details.
- Unit syslog-ng.service has failed.
--
-- The result is failed.
Dec 12 09:40:40 ip-172-31-23-167 systemd[1]: Unit syslog-ng.service
entered failed state.
Dec 12 09:40:40 ip-172-31-23-167 systemd[1]: syslog-ng.service failed.
Dec 12 09:40:40 ip-172-31-23-167 systemd[1]: syslog-ng.service holdoff
time over, scheduling restart.
Dec 12 09:40:40 ip-172-31-23-167 systemd[1]: Starting System Logger
Daemon...
-- Subject: Unit syslog-ng.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit syslog-ng.service has begun starting up.
Dec 12 09:40:40 ip-172-31-23-167 kernel: syslog-ng[9920]: segfault at 0 ip
(null) sp 00007fff5bbba5b8 error 14 in syslog-ng[400000+2000]
Dec 12 09:40:40 ip-172-31-23-167 systemd[1]: syslog-ng.service: main
process exited, code=killed, status=11/SEGV
Dec 12 09:40:40 ip-172-31-23-167 systemd[1]: Failed to start System Logger
Daemon.
-- Subject: Unit syslog-ng.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit syslog-ng.service has failed.
Would anyone know how to fix this, or if this is a bug?
Thanks in advance,
Traiano
____________________________________________________________
__________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?
product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq