Hello all, I am running the latest tumbleweed with kernel 5.0.13 on an IBM POWER6 box. After doing an update syslog-ng core dumps and never does start.
● 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 Sun 2019-05-19 16:53:39 EDT; 48s ago
Process: 11396 ExecStartPre=/usr/sbin/syslog-ng-service-prepare (code=exited, status=0/SUCCESS)
Process: 11399 ExecStart=/usr/sbin/syslog-ng -F $SYSLOG_NG_PARAMS (code=dumped, signal=SEGV)
Main PID: 11399 (code=dumped, signal=SEGV)
I was going to try reporting this as a bug but bugzilla.opensuse.org isn’t responding.
Could you check my syslog-ng 3.21.1 packages from OBS? They are available at https://build.opensuse.org/project/show/home:czanik:syslog-ng-githead And unlike the URL would normally mean, the repo contains 3.21.1 release (at least for now). If it works for you, then I push it to Base:System/syslog-ng and then to Tumbleweed.
In that case could you open a problem report upstream at https://github.com/balabit/syslog-ng/issues including a backtrace made from the core file? I have run syslog-ng successfully on POWER9 and Aarch64 (64bit ARM), so if you use POWER6, this might be an endianness problem.
If you don’t mind testing git snapshots, I’d recommend testing syslog-ng from my git snapshot repository. This time I updated it to today’s latest git version, which includes an update to the threading library used by syslog-ng (ivykis). I did not check the change log of ivykis in depth, but I know that it has a number of platform fixes. If it does not fix your use case, then please submit a full backtrace to syslog-ng issues: https://github.com/balabit/syslog-ng/issues
Also noting that the RPM built in the OBS has a 3.22 version built 7 days ago while the github project latest branch appears to be 3.13
Not sure how that works out…