Description of problem: Cockpit-pcp installed, "Store Metrics" within cockpit enabled When trying to zoom out in the system usage graphs (any of them) beyond what pcp keeps in its current log. In other words, the crash occurs when cockpit tries to access usage data from older/archived pcp logs. The pcp logs do exist and can be read with pcp cmdline tools. No manual configuration changes where made to pcp. Restarting pmlogger manually forces pcp to archive the current log and start a new one, hereby forcing the crash when usage data from before the archival step is attempted to be viewed. This happened on Fedora 29 and still after the upgrade to 30. Version-Release number of selected component: cockpit-pcp-192-1.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/libexec/cockpit-pcp crash_function: __pmInProfile executable: /usr/libexec/cockpit-pcp journald_cursor: s=ce2c5e569a68422a912bcd5004ff3a96;i=85f35;b=a5003371e90048bead5ddea16828dab0;m=19db4a8a47;t=587fca87f4b68;x=b4e552b2036395ba kernel: 5.0.9-301.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __pmInProfile at profile.c:169 #1 __pmdaNextInst at callback.c:147 #3 __pmdaCountInst at callback.c:189 #4 pmdaFetch at callback.c:569 #5 linux_fetch at pmda.c:8210 #6 __pmFetchLocal at fetchlocal.c:129 #7 pmFetch_ctx at fetch.c:160 #8 pmFetch at fetch.c:234 #9 cockpit_pcp_metrics_tick at src/bridge/cockpitpcpmetrics.c:352 #10 on_timeout_tick at src/bridge/cockpitmetrics.c:179
Created attachment 1562527 [details] File: backtrace
Created attachment 1562528 [details] File: cgroup
Created attachment 1562529 [details] File: core_backtrace
Created attachment 1562530 [details] File: cpuinfo
Created attachment 1562531 [details] File: dso_list
Created attachment 1562532 [details] File: environ
Created attachment 1562533 [details] File: exploitable
Created attachment 1562534 [details] File: limits
Created attachment 1562535 [details] File: maps
Created attachment 1562536 [details] File: mountinfo
Created attachment 1562537 [details] File: open_fds
Created attachment 1562538 [details] File: proc_pid_status
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-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 '30'. 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 30 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 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.