You are not logged in.

#1 2021-04-05 13:46:59

mgrimes
Member
Registered: 2012-08-16
Posts: 4

sshd frequently dumping core

On several different systems, I am seeing regular core dumps from sshd.  Something like:

Apr 05 05:31:13 wee audit[2726571]: SECCOMP auid=4294967295 uid=99 gid=99 ses=4294967295 pid=2726571 comm="sshd" exe="/usr/bin/sshd" sig=31 arch=c000003e syscall=41 compat=0 ip=0x7f47634e68fb code=0x0
Apr 05 05:31:13 wee audit[2726571]: ANOM_ABEND auid=4294967295 uid=99 gid=99 ses=4294967295 pid=2726571 comm="sshd" exe="/usr/bin/sshd" sig=31 res=1
Apr 05 05:31:13 wee sshd[2726570]: fatal: Timeout before authentication for 42.192.186.106 port 52710
Apr 05 05:31:13 wee kernel: audit: type=1326 audit(1617615073.628:201570): auid=4294967295 uid=99 gid=99 ses=4294967295 pid=2726571 comm="sshd" exe="/usr/bin/sshd" sig=31 arch=c000003e syscall=41 compat=0 ip=0x7f47634e68fb code=0x0
Apr 05 05:31:13 wee kernel: audit: type=1701 audit(1617615073.628:201571): auid=4294967295 uid=99 gid=99 ses=4294967295 pid=2726571 comm="sshd" exe="/usr/bin/sshd" sig=31 res=1
Apr 05 05:31:13 wee systemd[1]: Started Process Core Dump (PID 2727170/UID 0).
Apr 05 05:31:13 wee audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@48-2727170-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 05 05:31:13 wee kernel: audit: type=1130 audit(1617615073.768:201572): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@48-2727170-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 05 05:31:14 wee systemd-coredump[2727171]: Process 2726571 (sshd) of user 99 dumped core.

                                               Stack trace of thread 2726571:
                                               #0  0x00007f47634e68fb __socket (libc.so.6 + 0x1008fb)
                                               #1  0x00007f47634df013 openlog_internal (libc.so.6 + 0xf9013)
                                               #2  0x00007f47634df4f7 __vsyslog_internal (libc.so.6 + 0xf94f7)
                                               #3  0x00007f47634df803 __syslog_chk (libc.so.6 + 0xf9803)
                                               #4  0x0000563f51ea7d4c n/a (sshd + 0x65d4c)
                                               #5  0x0000563f51ea51ec n/a (sshd + 0x631ec)
                                               #6  0x0000563f51e75da9 n/a (sshd + 0x33da9)
                                               #7  0x0000563f51ea7cc5 n/a (sshd + 0x65cc5)
                                               #8  0x0000563f51ea80b1 n/a (sshd + 0x660b1)
                                               #9  0x0000563f51e51376 n/a (sshd + 0xf376)
                                               #10 0x00007f4763422f80 __restore_rt (libc.so.6 + 0x3cf80)
                                               #11 0x00007f47634dca67 __select (libc.so.6 + 0xf6a67)
                                               #12 0x0000563f51eae745 n/a (sshd + 0x6c745)
                                               #13 0x0000563f51eb46b3 n/a (sshd + 0x726b3)
                                               #14 0x0000563f51eb47b9 n/a (sshd + 0x727b9)
                                               #15 0x0000563f51e61411 n/a (sshd + 0x1f411)
                                               #16 0x0000563f51e4e903 n/a (sshd + 0xc903)
                                               #17 0x00007f476340db25 __libc_start_main (libc.so.6 + 0x27b25)
                                               #18 0x0000563f51e5109e n/a (sshd + 0xf09e)
Apr 05 05:31:14 wee kernel: audit: type=1131 audit(1617615074.398:201573): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@48-2727170-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 05 05:31:14 wee audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@48-2727170-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 05 05:31:14 wee systemd[1]: systemd-coredump@48-2727170-0.service: Succeeded.

It seems to be happening 1-5 times per day for the last several weeks (maybe months) on at least two different Arch systems (both relatively up-to-date).

I'm not having any issues connecting via ssh to these machines, but I'm concerned about the security implications.

Offline

#2 2021-04-05 13:55:10

seth
Member
Registered: 2012-09-03
Posts: 50,012

Re: sshd frequently dumping core

ssh tries t olog somethig and fails, likely due to seccomp, when trying to open a socket.
So check your seccomp config.

Offline

#3 2021-04-05 16:28:53

mgrimes
Member
Registered: 2012-08-16
Posts: 4

Re: sshd frequently dumping core

That makes me feel better about the security implications. Thanks!
Unfortunately, I don't know much about seccomp and Google is failing to point me to any seccomp config.

Offline

#4 2021-04-05 17:07:56

seth
Member
Registered: 2012-09-03
Posts: 50,012

Re: sshd frequently dumping core

What happens is that somebody from China (42.192.186.106) tries to connect but doesn't authenticate during the grace period.
That's fine and the child process is supposed to die but obviously not to SIGSYS.

This here looks related, do you have that (deprecated) key in your config?
https://lists.opensuse.org/opensuse-bug … 04234.html

Offline

#5 2021-04-06 22:02:05

krist
Member
Registered: 2007-09-27
Posts: 10

Re: sshd frequently dumping core

I'm seeing exactly the same. `UsePrivilegeSeparation` is not set in my sshd_config.

Offline

#6 2021-04-07 06:55:06

seth
Member
Registered: 2012-09-03
Posts: 50,012

Re: sshd frequently dumping core

https://github.com/openssh/openssh-port … p-filter.c has some recent action, esp. on socket access.
https://github.com/openssh/openssh-port … ecb6c3421a cannot be in the present package
It fixes https://bugzilla.mindrot.org/show_bug.cgi?id=3276 - which is a SIGSYS in relation with latest glibc

=> 99.9% cause

Edit: can you reliably ssh the machine in spite?

Last edited by seth (2021-04-07 06:58:12)

Offline

#7 2021-04-12 11:01:52

krist
Member
Registered: 2007-09-27
Posts: 10

Re: sshd frequently dumping core

Yes, ssh works fine other than that. The crashes only appear to happen on unsolicited login attempts with user 99 (nobody).

Last edited by krist (2021-06-14 09:19:02)

Offline

#8 2021-08-01 08:09:00

rfried123
Member
Registered: 2021-08-01
Posts: 4

Re: sshd frequently dumping core

Seeing the same coredumps and stacktraces here in the same situation (scripted breackin attempts from mostly china ips).
Quantity statistics: ~ 1 crash every 150 connections

Versions: openssh 8.6p1-1, glibc 2.33-5, kernel 5.13.5-arch1-1

Stacktrace::

                #0  0x00007f49b4d42e8b __socket (libc.so.6 + 0xffe8b)
                #1  0x00007f49b4d3b707 openlog_internal (libc.so.6 + 0xf8707)
                #2  0x00007f49b4d3bbe7 __vsyslog_internal (libc.so.6 + 0xf8be7)
                #3  0x00007f49b4d3bef3 __syslog_chk (libc.so.6 + 0xf8ef3)
                ...

Does anyone know a workaround or fix?

Offline

#9 2021-08-01 12:43:37

seth
Member
Registered: 2012-09-03
Posts: 50,012

Re: sshd frequently dumping core

I had hoped the patch in #6 would address this - apparently not.
For a more general "workaround" geoblock IP ranges that you don't expect legitimate access from.

For a fix, it'd probably be helpful to compile sshd debug enabled for a better backtrace, https://wiki.archlinux.org/title/Debugg … ing_traces

Offline

#10 2021-08-09 23:19:11

lod
Member
Registered: 2017-09-22
Posts: 9

Re: sshd frequently dumping core

I'm running in the same problem.

sudo coredumpctl gdb 1102443
           PID: 1102443 (sshd)
           UID: 99 (nobody)
           GID: 99 (nobody)
        Signal: 31 (SYS)
     Timestamp: Tue 2021-08-10 00:46:02 CEST (19min ago)
  Command Line: $'sshd: unknown [net]'
    Executable: /usr/bin/sshd
 Control Group: /system.slice/sshd.service
          Unit: sshd.service
         Slice: system.slice
       Boot ID: 3ebceaa181ed4cc2b1a26619e30d6c91
    Machine ID: c22961e82cf84500bf312d2a6181ad7c
      Hostname: .....
       Storage: /var/lib/systemd/coredump/core.sshd.99.3ebceaa181ed4cc2b1a26619e30d6c91.1102443.1628549162000000.zst (present)
     Disk Size: 154.8K
       Message: Process 1102443 (sshd) of user 99 dumped core.
                
                Found module linux-vdso.so.1 with build-id: 54e0dba403a2570cf1c2dc6bba33a1fd5eb595cb
                Found module libcap-ng.so.0 with build-id: 345acbd3f1a251a101cd25c90bf0b3adb9f5c70e
                Found module ld-linux-x86-64.so.2 with build-id: 040cc3dd10461562f177df39e3be2f3704258c3c
                Found module libresolv.so.2 with build-id: c915c72668282861a813f7ea3c0780f37b681dc0
                Found module libkeyutils.so.1 with build-id: ac405ddd17be10ce538da3211415ee50c8f8df79
                Found module libkrb5support.so.0 with build-id: c4ee4ad1dc2da57487bc2419b88f1b6873184582
                Found module libcom_err.so.2 with build-id: eb61ef71c8b97846db759fb89a115405cff6dd30
                Found module libk5crypto.so.3 with build-id: 632a59ed7c35704d84645e6d1e9873348d1eb802
                Found module libpthread.so.0 with build-id: 07c8f95b4f3251d08550217ad8a1f31066229996
                Found module libdl.so.2 with build-id: 5abc547e7b0949f89f3c0e21ab0c8331a7440a8a
                Found module libaudit.so.1 with build-id: ebf0a40919d7bb093d2f3ddfd08bdfe35f2e9f18
                Found module libc.so.6 with build-id: 4b406737057708c0e4c642345a703c47a61c73dc
                Found module libkrb5.so.3 with build-id: c61cb4da63b8a839ee7df99eaf9dbd3d0968534c
                Found module libgssapi_krb5.so.2 with build-id: 9be9d3348399b72b76161a64e6d9fd760b77163a
                Found module libcrypt.so.2 with build-id: a25307ba7d929153e2dddf45f25aa8485408ca8f
                Found module libz.so.1 with build-id: 81bf6e728a6d6f5b105b0f8b25f6c614ce10452a
                Found module libutil.so.1 with build-id: af6d8200064ee6e6a01252884d166b44f0a6121b
                Found module libcrypto.so.1.1 with build-id: 81b77a8e0b6e1c0db19644a5f120890f02762021
                Found module libpam.so.0 with build-id: cc094abc5e6bb62f5156ed1ff5d828957cebe46c
                Found module sshd with build-id: e134bb5325cf66e1180402c3d903442caddc5e4e
                Stack trace of thread 1102443:
                #0  0x00007f0ef9c8ce8b __socket (libc.so.6 + 0xffe8b)
                #1  0x00007f0ef9c85707 openlog_internal (libc.so.6 + 0xf8707)
                #2  0x00007f0ef9c85be7 __vsyslog_internal (libc.so.6 + 0xf8be7)
                #3  0x00007f0ef9c85ef3 __syslog_chk (libc.so.6 + 0xf8ef3)
                #4  0x00005569ba989dfc syslog (sshd + 0x67dfc)
                #5  0x00005569ba98a56c sshlogv (sshd + 0x6856c)
                #6  0x00005569ba98778e sshfatal (sshd + 0x6578e)
                #7  0x00005569ba9567aa mm_log_handler (sshd + 0x347aa)
                #8  0x00005569ba989d72 do_log (sshd + 0x67d72)
                #9  0x00005569ba98a56c sshlogv (sshd + 0x6856c)
                #10 0x00005569ba98a863 sshsigdie (sshd + 0x68863)
                #11 0x00005569ba931446 grace_alarm_handler (sshd + 0xf446)
                #12 0x00007f0ef9bc9da0 __restore_rt (libc.so.6 + 0x3cda0)
                #13 0x00007f0ef9c83197 __select (libc.so.6 + 0xf6197)
                #14 0x00005569ba991625 ssh_packet_read_seqnr (sshd + 0x6f625)
                #15 0x00005569ba997933 ssh_dispatch_run (sshd + 0x75933)
                #16 0x00005569ba997a49 ssh_dispatch_run_fatal (sshd + 0x75a49)
                #17 0x00005569ba941919 do_authentication2 (sshd + 0x1f919)
                #18 0x00005569ba9305a7 main (sshd + 0xe5a7)
                #19 0x00007f0ef9bb4b25 __libc_start_main (libc.so.6 + 0x27b25)
                #20 0x00005569ba93115e _start (sshd + 0xf15e)

GNU gdb (GDB) 10.2
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/sshd...
[New LWP 1102443]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `sshd: unknown [net]'.
Program terminated with signal SIGSYS, Bad system call.
#0  0x00007f0ef9c8ce8b in socket () from /usr/lib/libc.so.6
(gdb) bt
#0  0x00007f0ef9c8ce8b in socket () from /usr/lib/libc.so.6
#1  0x00007f0ef9c85707 in openlog_internal () from /usr/lib/libc.so.6
#2  0x00007f0ef9c85be7 in __vsyslog_internal () from /usr/lib/libc.so.6
#3  0x00007f0ef9c85ef3 in __syslog_chk () from /usr/lib/libc.so.6
#4  0x00005569ba989dfc in syslog (__fmt=0x5569ba9d5214 "%.500s", __pri=2) at /usr/include/bits/syslog.h:31
#5  do_log (level=level@entry=SYSLOG_LEVEL_FATAL, force=force@entry=0, suffix=suffix@entry=0x0, fmt=0x7ffcdd211380 "mm_log_handler: write: %s", args=args@entry=0x7ffcdd211860) at log.c:416
#6  0x00005569ba98a56c in sshlogv (file=<optimized out>, func=0x7ffcdd211380 "mm_log_handler: write: %s", line=108, showfunc=<optimized out>, level=SYSLOG_LEVEL_FATAL, suffix=0x0, 
    fmt=0x5569ba9c9cc2 "write: %s", args=0x7ffcdd211860) at log.c:485
#7  0x00005569ba98778e in sshfatal (file=file@entry=0x5569ba9cc980 "monitor_wrap.c", func=func@entry=0x5569ba9cd0e0 <__func__.27> "mm_log_handler", line=line@entry=108, showfunc=showfunc@entry=1, 
    level=level@entry=SYSLOG_LEVEL_FATAL, suffix=suffix@entry=0x0, fmt=0x5569ba9c9cc2 "write: %s") at fatal.c:43
#8  0x00005569ba9567aa in mm_log_handler (level=SYSLOG_LEVEL_FATAL, forced=<optimized out>, msg=<optimized out>, ctx=0x5569bba22b50) at monitor_wrap.c:108
#9  0x00005569ba989d72 in do_log (level=level@entry=SYSLOG_LEVEL_FATAL, force=force@entry=0, suffix=suffix@entry=0x0, fmt=0x7ffcdd212290 "Timeout before authentication for %s port %d", 
    args=args@entry=0x7ffcdd212770) at log.c:403
#10 0x00005569ba98a56c in sshlogv (file=<optimized out>, func=0x7ffcdd212290 "Timeout before authentication for %s port %d", line=371, showfunc=<optimized out>, 
    level=level@entry=SYSLOG_LEVEL_FATAL, suffix=0x0, fmt=0x5569ba9c3700 "Timeout before authentication for %s port %d", args=0x7ffcdd212770) at log.c:485
#11 0x00005569ba98a863 in sshsigdie (file=file@entry=0x5569ba9c3004 "sshd.c", func=func@entry=0x5569ba9c4890 <__func__.26> "grace_alarm_handler", line=line@entry=371, showfunc=showfunc@entry=0, 
    level=level@entry=SYSLOG_LEVEL_ERROR, suffix=suffix@entry=0x0, fmt=0x5569ba9c3700 "Timeout before authentication for %s port %d") at log.c:454
#12 0x00005569ba931446 in grace_alarm_handler (sig=<optimized out>) at sshd.c:371
#13 <signal handler called>
#14 0x00007f0ef9c83197 in select () from /usr/lib/libc.so.6
#15 0x00005569ba991625 in ssh_packet_read_seqnr (ssh=ssh@entry=0x5569bba37960, typep=typep@entry=0x7ffcdd214f23 "", seqnr_p=seqnr_p@entry=0x7ffcdd214f24) at packet.c:1364
#16 0x00005569ba997933 in ssh_dispatch_run (ssh=ssh@entry=0x5569bba37960, mode=mode@entry=0, done=done@entry=0x5569bba39570) at dispatch.c:96
#17 0x00005569ba997a49 in ssh_dispatch_run_fatal (ssh=ssh@entry=0x5569bba37960, mode=mode@entry=0, done=done@entry=0x5569bba39570) at dispatch.c:133
#18 0x00005569ba941919 in do_authentication2 (ssh=ssh@entry=0x5569bba37960) at auth2.c:176
#19 0x00005569ba9305a7 in main (ac=<optimized out>, av=<optimized out>) at sshd.c:2226
quit) 

Last edited by lod (2021-08-09 23:19:51)

Offline

#11 2021-08-10 06:20:38

loqs
Member
Registered: 2014-03-06
Posts: 17,197

Re: sshd frequently dumping core

__socket calls socket and that is trapped by seccomp?
https://github.com/bminor/glibc/blob/gl … cket.c#L30

Must be missing something.

seth do you think audting the call trace would help?  https://github.com/openssh/openssh-port … lter.c#L22

Offline

#12 2021-08-10 06:42:54

seth
Member
Registered: 2012-09-03
Posts: 50,012

Re: sshd frequently dumping core

#10 0x00005569ba98a56c in sshlogv (file=<optimized out>, func=0x7ffcdd212290 "Timeout before authentication for %s port %d", line=371, showfunc=<optimized out>, 
    level=level@entry=SYSLOG_LEVEL_FATAL, suffix=0x0, fmt=0x5569ba9c3700 "Timeout before authentication for %s port %d", args=0x7ffcdd212770) at log.c:485
#11 0x00005569ba98a863 in sshsigdie (file=file@entry=0x5569ba9c3004 "sshd.c", func=func@entry=0x5569ba9c4890 <__func__.26> "grace_alarm_handler", line=line@entry=371, showfunc=showfunc@entry=0, 
    level=level@entry=SYSLOG_LEVEL_ERROR, suffix=suffix@entry=0x0, fmt=0x5569ba9c3700 "Timeout before authentication for %s port %d") at log.c:454
#12 0x00005569ba931446 in grace_alarm_handler (sig=<optimized out>) at sshd.c:371
#13 <signal handler called>
#14 0x00007f0ef9c83197 in select () from /usr/lib/libc.so.6
#15 0x00005569ba991625 in ssh_packet_read_seqnr (ssh=ssh@entry=0x5569bba37960, typep=typep@entry=0x7ffcdd214f23 "", seqnr_p=seqnr_p@entry=0x7ffcdd214f24) at packet.c:1364
#16 0x00005569ba997933 in ssh_dispatch_run (ssh=ssh@entry=0x5569bba37960, mode=mode@entry=0, done=done@entry=0x5569bba39570) at dispatch.c:96
#17 0x00005569ba997a49 in ssh_dispatch_run_fatal (ssh=ssh@entry=0x5569bba37960, mode=mode@entry=0, done=done@entry=0x5569bba39570) at dispatch.c:133
#18 0x00005569ba941919 in do_authentication2 (ssh=ssh@entry=0x5569bba37960) at auth2.c:176
#19 0x00005569ba9305a7 in main (ac=<optimized out>, av=<optimized out>) at sshd.c:2226

The socket is from the log, sshd dies because of sssigdie() because select() times out and triggers a  sigalarm
https://github.com/openssh/libopenssh/b … hd.c#L1915
https://github.com/openssh/libopenssh/b … shd.c#L335
https://github.com/openssh/libopenssh/b … et.c#L1287

Edit: though expectable in this context… and not an excuse for sigsys.

Last edited by seth (2021-08-10 06:49:49)

Offline

#13 2021-08-10 08:09:34

seth
Member
Registered: 2012-09-03
Posts: 50,012

Re: sshd frequently dumping core

#5  do_log (level=level@entry=SYSLOG_LEVEL_FATAL, force=force@entry=0, suffix=suffix@entry=0x0, fmt=0x7ffcdd211380 "mm_log_handler: write: %s", args=args@entry=0x7ffcdd211860) at log.c:416
#6  0x00005569ba98a56c in sshlogv (file=<optimized out>, func=0x7ffcdd211380 "mm_log_handler: write: %s", line=108, showfunc=<optimized out>, level=SYSLOG_LEVEL_FATAL, suffix=0x0, 
    fmt=0x5569ba9c9cc2 "write: %s", args=0x7ffcdd211860) at log.c:485
#7  0x00005569ba98778e in sshfatal (file=file@entry=0x5569ba9cc980 "monitor_wrap.c", func=func@entry=0x5569ba9cd0e0 <__func__.27> "mm_log_handler", line=line@entry=108, showfunc=showfunc@entry=1, 
    level=level@entry=SYSLOG_LEVEL_FATAL, suffix=suffix@entry=0x0, fmt=0x5569ba9c9cc2 "write: %s") at fatal.c:43
#8  0x00005569ba9567aa in mm_log_handler (level=SYSLOG_LEVEL_FATAL, forced=<optimized out>, msg=<optimized out>, ctx=0x5569bba22b50) at monitor_wrap.c:108
#9  0x00005569ba989d72 in do_log (level=level@entry=SYSLOG_LEVEL_FATAL, force=force@entry=0, suffix=suffix@entry=0x0, fmt=0x7ffcdd212290 "Timeout before authentication for %s port %d", 
    args=args@entry=0x7ffcdd212770) at log.c:403
#10 0x00005569ba98a56c in sshlogv (file=<optimized out>, func=0x7ffcdd212290 "Timeout before authentication for %s port %d", line=371, showfunc=<optimized out>, 
    level=level@entry=SYSLOG_LEVEL_FATAL, suffix=0x0, fmt=0x5569ba9c3700 "Timeout before authentication for %s port %d", args=0x7ffcdd212770) at log.c:485
#11 0x00005569ba98a863 in sshsigdie (file=file@entry=0x5569ba9c3004 "sshd.c", func=func@entry=0x5569ba9c4890 <__func__.26> "grace_alarm_handler", line=line@entry=371, showfunc=showfunc@entry=0, 
    level=level@entry=SYSLOG_LEVEL_ERROR, suffix=suffix@entry=0x0, fmt=0x5569ba9c3700 "Timeout before authentication for %s port %d") at log.c:454

I assume it doesn't like that the log attempt causes an inner (fatal) log (hence trying to write into the syslog while writing into the syslog) because atomicio() fails to write the expected length of data.
Obviously somehing that should™ not happen (trying to log that you cannot log…)
do_log() in log.c:399 has a recursion catch that resorts to calling syslog…

You could try to "sshd -D -E /path/to/some/file" in the service - and file an upstream bug.

Offline

#14 2021-08-10 13:27:58

lod
Member
Registered: 2017-09-22
Posts: 9

Re: sshd frequently dumping core

Well, looks like -E file works as a workaround. No more core-dumps in the last 5'ish hours. I will file a bug report later. Cheers, mate!

fixed in 8.7

Last edited by lod (2021-09-02 12:49:12)

Offline

Board footer

Powered by FluxBB