Version-Release number of selected component: sysstat-11.5.4-2.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/lib64/sa/sadc -F -L -S DISK 1 1 /var/log/sa crash_function: rawmemchr executable: /usr/lib64/sa/sadc journald_cursor: s=51d0161390b44f36aa10aa18981ab183;i=18a6a;b=dc5ae4db6e6e4d749dd3aaef8d57bd11;m=fc193bb11;t=558ecdd029e3a;x=87ef3fe8239ba926 kernel: 4.12.9-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (3 frames) #0 rawmemchr at ../sysdeps/x86_64/rawmemchr.S:54 #1 _IO_str_init_static_internal at strops.c:55 #2 __isoc99_vsscanf at isoc99_vsscanf.c:45
Created attachment 1325533 [details] File: backtrace
Created attachment 1325534 [details] File: cgroup
Created attachment 1325535 [details] File: core_backtrace
Created attachment 1325536 [details] File: cpuinfo
Created attachment 1325537 [details] File: dso_list
Created attachment 1325538 [details] File: environ
Created attachment 1325539 [details] File: exploitable
Created attachment 1325540 [details] File: limits
Created attachment 1325541 [details] File: maps
Created attachment 1325542 [details] File: open_fds
Created attachment 1325543 [details] File: proc_pid_status
Created attachment 1325544 [details] File: var_log_messages
Hello Leonid, thanks for the report. Are you using docker with overlay fs? What is in your /etc/mtab file? There was fixed similar crash recently in the upstream: https://github.com/sysstat/sysstat/commit/d40c8ecc530303d7e802617f21a9ac85dbcd68bd Thanks, peter
(In reply to Peter Schiffer from comment #13) > Hello Leonid, > > thanks for the report. Are you using docker with overlay fs? What is in your > /etc/mtab file? There was fixed similar crash recently in the upstream: > https://github.com/sysstat/sysstat/commit/ > d40c8ecc530303d7e802617f21a9ac85dbcd68bd > > Thanks, > > peter Hello Peter, I really do have a ridiculously long "overlay" line in my /etc/mtab, so it definitely appears like a manifestation of this bug.
I'm seeing the same thing on FC26 using docker with overlay fs. It's causing the constant creation of cores. $ coredumpctl dump PID: 10935 (sadc) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Mon 2018-01-29 08:30:39 CST (7min ago) Command Line: /usr/lib64/sa/sadc -F -L -S DISK 1 1 /var/log/sa Executable: /usr/lib64/sa/sadc Control Group: /system.slice/sysstat-collect.service Unit: sysstat-collect.service Slice: system.slice Boot ID: 43d4ae48738c4ac4aec67aa07efc54f2 Machine ID: 73861be378814311b60f5534c69a80b7 Hostname: <snip> Storage: /var/lib/systemd/coredump/core.sadc.0.43d4ae48738c4ac4aec67aa07efc54f2.10935.1517236239000000.lz4 (inaccessible) Message: Process 10935 (sadc) of user 0 dumped core. Stack trace of thread 10935: #0 0x00007f8101a2aa4f __rawmemchr (libc.so.6) #1 0x00007f8101a0f592 _IO_str_init_static_internal (libc.so.6) #2 0x00007f81019fbfbd __isoc99_vsscanf (libc.so.6) #3 0x00007f81019fbf24 __isoc99_sscanf (libc.so.6) #4 0x000000000040cc42 get_filesystem_nr (sadc) #5 0x00000000004044f9 wrap_get_filesystem_nr (sadc) #6 0x0000000000402c37 sa_sys_init (sadc) #7 0x00000000004021d4 main (sadc) #8 0x00007f81019ac88a __libc_start_main (libc.so.6) #9 0x000000000040254a _start (sadc)
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.