Mailinglist Archive: opensuse-bugs (6588 mails)

< Previous Next >
[Bug 1143190] New: syslog-ng-3.19.1-3.3.aarch64: segfault at start
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 29 Jul 2019 08:05:31 +0000
  • Message-id: <bug-1143190-21960@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1143190


Bug ID: 1143190
Summary: syslog-ng-3.19.1-3.3.aarch64: segfault at start
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
Reporter: matwey.kornilov@xxxxxxxxx
QA Contact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

Created attachment 811889
--> http://bugzilla.opensuse.org/attachment.cgi?id=811889&action=edit
systemd-core

Hello,

I am running syslog-ng-3.19.1-3.3.aarch64 at openSUSE Tumbleweed 20190724 and
syslog service is crashing at the startup as following:

# systemctl status syslog
● syslog-ng.service - System Logging Service
Loaded: loaded (/usr/lib/systemd/system/syslog-ng.service; enabled; vendor
preset: disabled)
Active: failed (Result: core-dump) since Tue 2019-05-28 12:58:57 MSK; 2
months 1 days ago
Process: 1150 ExecStartPre=/usr/sbin/syslog-ng-service-prepare (code=exited,
status=0/SUCCESS)
Process: 1152 ExecStart=/usr/sbin/syslog-ng -F $SYSLOG_NG_PARAMS
(code=dumped, signal=SEGV)
Main PID: 1152 (code=dumped, signal=SEGV)

мая 28 12:58:57 localhost systemd[1]: syslog-ng.service: Service
RestartSec=100ms expired, scheduling restart.
мая 28 12:58:57 localhost systemd[1]: syslog-ng.service: Scheduled restart
job,
restart counter is at 5.
мая 28 12:58:57 localhost systemd[1]: Stopped System Logging Service.
мая 28 12:58:57 localhost systemd[1]: syslog-ng.service: Start request
repeated
too quickly.
мая 28 12:58:57 localhost systemd[1]: syslog-ng.service: Failed with result
'core-dump'.
мая 28 12:58:57 localhost systemd[1]: Failed to start System Logging Service.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
Follow Ups