Daniel

I'm seeing the same on my 13.1 jail. But this only happens when syslog-ng is launched from the rc script, then is see 3 instances running in parallel and a...

Here is the trace from the core file: ```# lldb -c /var/db/syslog-ng.core /usr/local/sbin/syslog-ng (lldb) target create "/usr/local/sbin/syslog-ng" --core "/var/db/syslog-ng.core" Core file '/var/db/syslog-ng.core' (x86_64) was loaded. (lldb) bt all * thread...

I have no problem sharing my config: ```# cat /usr/local/etc/syslog-ng.conf @version:3.36 @include "scl.conf" # syslog-ng configuration file. # # This should behave pretty much like the original syslog on RedHat....

@OverOrion, i'm not shure this is what i'm seeing. The program in my destination _is_ existing and once i run syslog-ng without the supervisor process i don't see the issue...

> IV_EXCLUDE_POLL_METHOD=kqueue This seems to do the trick, not seeing any more SIGABRTs so far when running from rc(8). Thanks a lot! ``` --- /usr/local/etc/rc.d/syslog-ng 2022-06-29 17:08:13.951949000 +0200 +++ /usr/local/etc/rc.d/syslog-ng...

Hi, nothing is wrong, the tool is trying to connect to a M3UA service at 127.0.0.1:2905/sctp, but there is no such service running. best /daniel

Hi, you can find the config file in you ss7MAPer root folder. It is called 'config'. best

Hi, can you give me the output of: - 'uname -a' - 'erl -version' best /daniel

Hi, please do not hijack issues, but open a new one instead. best /d

Hi, this seems to be a known bug when running erlang binaries on older cpus (without sse2). You can fix this by building your erlang from source and configure it...