Comment 0 for bug 2060275

In Cockpit's CI we see a lot of pmproxy crashes like [1] in a test which starts/stops/reconfigures pmlogger, pmproxy, and redis. The journal (some examples are [2][3][4]) always shows a similar stack trace:

pmproxy[9832]: segfault at 3 ip 0000767961047e45 sp 00007ffe97e825d0 error 4 in libpcp_web.so.1[767961018000+5c000] likely on CPU 0 (core 0, socket 0)

Stack trace of thread 9832:
#0 0x0000767961047e45 n/a (libpcp_web.so.1 + 0x38e45)
#1 0x0000767961059745 n/a (libpcp_web.so.1 + 0x4a745)
#2 0x0000767961056311 n/a (libpcp_web.so.1 + 0x47311)
#3 0x0000767960f5c52b n/a (libuv.so.1 + 0x2752b)
#4 0x0000767960f5dbdb n/a (libuv.so.1 + 0x28bdb)
#5 0x0000767960f44ce8 uv_run (libuv.so.1 + 0xfce8)
#6 0x00005cae24f55097 n/a (pmproxy + 0xb097)
#7 0x00005cae24f53b6d n/a (pmproxy + 0x9b6d)
#8 0x000076796062a1ca __libc_start_call_main (libc.so.6 + 0x2a1ca)
#9 0x000076796062a28b __libc_start_main_impl (libc.so.6 + 0x2a28b)
#10 0x00005cae24f54135 n/a (pmproxy + 0xa135)

Unfortunately that's not super useful

[1] https://cockpit-logs.us-east-1.linodeobjects.com/pull-20264-13fcc041-20240404-201827-ubuntu-stable-other/log.html#34
[2] https://cockpit-logs.us-east-1.linodeobjects.com/pull-20264-13fcc041-20240404-201827-ubuntu-stable-other/TestHistoryMetrics-testPmProxySettings-ubuntu-stable-127.0.0.2-2201-FAIL.log.gz
[3] https://cockpit-logs.us-east-1.linodeobjects.com/pull-6177-6626b317-20240404-225904-ubuntu-stable-other-cockpit-project-cockpit/TestHistoryMetrics-testPmProxySettings-ubuntu-stable-127.0.0.2-2401-FAIL.log.gz
[4] https://cockpit-logs.us-east-1.linodeobjects.com/pull-20261-d1621935-20240404-105717-ubuntu-stable-other/TestHistoryMetrics-testPmProxySettings-ubuntu-stable-127.0.0.2-2201-FAIL.log.gz