Version-Release number of selected component: pcp-6.0.5-1.fc38 Additional info: reporter: libreport-2.17.11 type: CCpp reason: pmproxy killed by SIGSEGV journald_cursor: s=013f1b28607345409ef55a40a91eb446;i=935;b=06acedb0c2a44486af15748abb4b8aae;m=1a830ee;t=6031e6730dbed;x=b41174cb64250d5a executable: /usr/libexec/pcp/bin/pmproxy cmdline: /usr/libexec/pcp/bin/pmproxy -F -A rootdir: / uid: 970 kernel: 6.4.10-200.fc38.x86_64 package: pcp-6.0.5-1.fc38 runlevel: unknown backtrace_rating: 4 crash_function: seriesPassBaton Truncated backtrace: Thread no. 1 (9 frames) #0 seriesPassBaton at /usr/src/debug/pcp-6.0.5-1.fc38.x86_64/src/libpcp_web/src/batons.c:131 #1 pmDiscoverInvokeClosedCallBacks at /usr/src/debug/pcp-6.0.5-1.fc38.x86_64/src/libpcp_web/src/discover.c:650 #2 pmDiscoverPurgeDeleted at /usr/src/debug/pcp-6.0.5-1.fc38.x86_64/src/libpcp_web/src/discover.c:217 #3 changed_callback at /usr/src/debug/pcp-6.0.5-1.fc38.x86_64/src/libpcp_web/src/discover.c:1774 #4 fs_change_callBack at /usr/src/debug/pcp-6.0.5-1.fc38.x86_64/src/libpcp_web/src/discover.c:459 #5 uv__inotify_read at src/unix/linux.c:2419 #6 uv__io_poll at src/unix/linux.c:1476 #7 uv_run at src/unix/core.c:447 #8 main_loop at /usr/src/debug/pcp-6.0.5-1.fc38.x86_64/src/pmproxy/src/server.c:901
Created attachment 1983887 [details] File: proc_pid_status
Created attachment 1983888 [details] File: maps
Created attachment 1983889 [details] File: limits
Created attachment 1983890 [details] File: cgroup
Created attachment 1983891 [details] File: environ
Created attachment 1983892 [details] File: open_fds
Created attachment 1983893 [details] File: mountinfo
Created attachment 1983894 [details] File: os_info
Created attachment 1983895 [details] File: cpuinfo
Created attachment 1983896 [details] File: core_backtrace
Created attachment 1983897 [details] File: exploitable
Created attachment 1983898 [details] File: dso_list
Created attachment 1983899 [details] File: backtrace
We've been unable to reproduce this locally so far. Its possible it has been fixed in the pcp-6.1.x series. If further insights into reproducing this are available, please let us know. Thanks!
Still unable to reproduce this, and no new reports. We're now up to pcp-6.2.x series so thinking is this was fixed as a side-effect of some other change. Please reopen with details if it recurs, thanks!