Hello Nathan, Nathan Scott [2024-04-09 16:19 +1000]: > Is any of this getting through... ? Just checked the Ubuntu tracker > URL, and looks like every response Ken or I sent has been dropped on > the ground.
Right, I didn't get any response either (not a surprise, as it's *first* Launchpad receiving replies, and then it sends out notifications). I did do bug replies via email in the past, but these days it may get caught in some spam prevention measures? Probably better to just post them on the web ui? I CC my reply to the LP bug if you don't mind -- first of all to test this, and also to keep a more permanent record of our discussion. > Long and short of it is, we've not been able to reproduce and debian > dbgsym on sub-packages is still broken for unknown reasons... > https://github.com/performancecopilot/pcp/pull/1948 It's not really unknown, it's "just" a file conflict: | dpkg: error processing archive build/deb/pcp-pmda-infiniband-dbgsym_6.2.1-0.20240409.f312285_amd64.deb (--install): | trying to overwrite '/usr/lib/debug/.build-id/57/02df011cfaf166b948e1fefde236eaf3a6ee65.debug', which is also in package pcp-dbgsym 6.2.1-0.20240409.f312285 | | dpkg: error processing archive build/deb/pcp-testsuite-dbgsym_6.2.1-0.20240409.f312285_amd64.deb (--install): | trying to overwrite '/usr/lib/debug/.build-id/17/6edc7e590f766a2ea87b5decaeb994d7c48d24.debug', which is also in package pcp-dbgsym 6.2.1-0.20240409.f312285 I.e. these are shipped in two different packages. [1] https://github.com/performancecopilot/pcp/actions/runs/8610492722/job/23596103839?pr=1948#step:9:149 > This is not a known bug - do you know if this is specific to pcp-6.2.0 > (latest PCP) or are earlier versions affected? One change that may > be related here is we enabled v3 PCP archives by default in 6.2.0. We see this only in noble (i.e. upcoming 24.04). I.e. 6.0.5 in 23.10 was still ok, and 6.2.0 occasionally crashes. > The limited stack we have suggests we're in pmproxy log discovery > code, in an inotify/libuv event, which does have v3-specific code. > > For those who can reproduce this, it'd be worth experimenting and > setting the following field back to 2 ... (requires pmlogger restart). > > $ grep PCP_ARCHIVE_VERSION /etc/pcp.conf > PCP_ARCHIVE_VERSION=3 > > If that clears the issue, it'll help us triangulate on a possible cause. OK -- I'll do some experimentation and report back here. Thanks! Martin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060275 Title: pmproxy crash at startup in libpcp_web.so.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/2060275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
