Version-Release number of selected component: stalld-1.16-3.fc38 Additional info: reporter: libreport-2.17.9 type: CCpp reason: stalld killed by SIGABRT journald_cursor: s=26bde72f94244d7499e94f1116a4770d;i=aeab41;b=00fd62f5ede842f190d631c960e0074d;m=1413d12e;t=5f832239f1ae6;x=3ca1cd992ec38aa2 executable: /usr/bin/stalld cmdline: /usr/bin/stalld --systemd -p 1000000000 -r 20000 -d 3 -t 30 --foreground --pidfile /run/stalld.pid cgroup: 0::/system.slice/stalld.service rootdir: / uid: 0 kernel: 6.2.9-300.fc38.x86_64 package: stalld-1.16-3.fc38 runlevel: unknown backtrace_rating: 4 crash_function: sprintf Truncated backtrace: Thread no. 1 (3 frames) #9 sprintf at /usr/include/bits/stdio2.h:30 #10 find_debugfs_sched_debug at src/utils.c:427 #11 find_sched_debug_path at src/utils.c:470
Created attachment 1957392 [details] File: proc_pid_status
Created attachment 1957393 [details] File: maps
Created attachment 1957394 [details] File: limits
Created attachment 1957395 [details] File: environ
Created attachment 1957396 [details] File: open_fds
Created attachment 1957397 [details] File: mountinfo
Created attachment 1957398 [details] File: os_info
Created attachment 1957399 [details] File: cpuinfo
Created attachment 1957400 [details] File: core_backtrace
Created attachment 1957401 [details] File: dso_list
Created attachment 1957402 [details] File: var_log_messages
Created attachment 1957403 [details] File: machineid
Created attachment 1957404 [details] File: backtrace
Having the stalld service enabled seems to cause this. reporter: libreport-2.17.10 type: CCpp reason: stalld killed by SIGABRT journald_cursor: s=26bde72f94244d7499e94f1116a4770d;i=40933e0;b=59a79eac56ee4f4eb3e362973d8597a0;m=13f3318;t=5fbe8086a24e3;x=ab420a197661d463 executable: /usr/bin/stalld cmdline: /usr/bin/stalld --systemd -p 1000000000 -r 20000 -d 3 -t 30 --foreground --pidfile /run/stalld.pid cgroup: 0::/system.slice/stalld.service rootdir: / uid: 0 kernel: 6.3.3-200.fc38.x86_64 package: stalld-1.16-3.fc38 runlevel: unknown backtrace_rating: 4 crash_function: sprintf comment: Having the stalld service enabled seems to cause this.
I believe I encountered the same problem on Fedora rawhide: # coredumpctl info -1 PID: 18241 (stalld) UID: 0 (root) GID: 0 (root) Signal: 6 (ABRT) Timestamp: Thu 2023-06-29 09:05:39 EDT (4min 30s ago) Command Line: /usr/bin/stalld --systemd -p 1000000000 -r 20000 -d 3 -t 30 --l> Executable: /usr/bin/stalld Control Group: /system.slice/stalld.service Unit: stalld.service Slice: system.slice Boot ID: e94467f7e87846e9be3ae37f41572df9 Machine ID: 4bf80b5319374414937ecae37aaa5c42 Hostname: vm-10-0-185-58.hosted.upshift.rdu2.redhat.com Storage: /var/lib/systemd/coredump/core.stalld.0.e94467f7e87846e9be3ae37> Size on Disk: 22.6K Package: stalld/1.16-3.fc38 build-id: a0a35c85adb172c0aef420ef18be176c9de31539 Message: Process 18241 (stalld) of user 0 dumped core. Module stalld from rpm stalld-1.16-3.fc38.x86_64 Stack trace of thread 18241: #0 0x00007fae7808f734 __pthread_kill_implementation (libc.so.6> #1 0x00007fae7803e75e raise (libc.so.6 + 0x3e75e) #2 0x00007fae7802687f abort (libc.so.6 + 0x2687f) #3 0x00007fae78027755 __libc_message.cold (libc.so.6 + 0x27755) #4 0x00007fae781229c9 __fortify_fail (libc.so.6 + 0x1229c9) #5 0x00007fae78122384 __chk_fail (libc.so.6 + 0x122384) #6 0x00007fae7807afb0 __vsprintf_internal (libc.so.6 + 0x7afb0) #7 0x00007fae78123c1f __sprintf_chk (libc.so.6 + 0x123c1f) #8 0x00005605fcec709a main (stalld + 0x309a) #9 0x00007fae780280ca __libc_start_call_main (libc.so.6 + 0x28> #10 0x00007fae7802818b __libc_start_main@@GLIBC_2.34 (libc.so.6> #11 0x00005605fcec87e5 _start (stalld + 0x47e5) ELF object binary architecture: AMD x86-64 #