[Bug 1700827] Re: [MIR] pcp package
Re systemd. Commit a59111b in my upstream tree turns on use of systemd in PCP for all Debian-based platforms that configure thinks they're running a real systemd. This code has been heavily exercised on the non-Debian platforms for a long time, and my testing on Ubuntu 17.04 and 17.10 suggests it works just fine there, as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700827 Title: [MIR] pcp package To manage notifications about this bug go to: https://bugs.launchpad.net/pcp/+bug/1700827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700827] Re: [MIR] pcp package
With the upstream changes mentioned above and a couple of tweaks (everything up to and including commit f09cac4), I've been able to complete a build, package, install and start PCP operation on all the machines in my PCP QA Farm. This means: amd64 FreeBSD 10.2-RELEASE, amd64 OpenBSD 5.8 i386Darwin 10.8.0, FreeBSD 9.3-RELEASE-p30, NetBSD 6.1.5 i686Debian 7.11, Debian 9.1, Fedora 25, Fedora 26, LinuxMint 15, openSUSE 13.2, Ubuntu 17.04 i86pc OpenIndiana Development oi_151.1.8 x86_64 Arch Linux, CentOS6.9, CentOS Linux7.3.1611, CentOS Linux7.3.1611, CentOS Linux7.3.1611, Debian 8.9, Debian 9.1, Fedora 21, Fedora 23, Fedora 25, Fedora 26, Gentoo 2.2, LinuxMint 17.3, MandrivaLinux 2011.0, openSUSE 42.2, openSUSE 42.3, RHEL Server 6.9, RHEL Server 7.3, Slackware "14.2", SUSE SLES12 SP0, Ubuntu 14.04, Ubuntu 15.04, Ubuntu 16.04, Ubuntu 17.04, Ubuntu 17.10 So I think we're clear of any regressions on the non-Debian platforms with these changes. +1 from me, thanks Nathan and Eric. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700827 Title: [MIR] pcp package To manage notifications about this bug go to: https://bugs.launchpad.net/pcp/+bug/1700827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 439572] Re: pmcd assert failure: *** buffer overflow detected ***: /usr/lib/pcp/bin/pmcd terminated
I agree with Eric. Between when this bug was opened and now we've done a lot of work on hardening PCP. There is a very good chance (based on the fact that I wrote much of the related code) that this issue with pmcd was related to PDU handling between pmcd and clients of pmcd. There have been fixes over time in this area and there are no open issues even remotely related to this in the active PCP bug list over at https://github.com/performancecopilot/pcp/issues -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/439572 Title: pmcd assert failure: *** buffer overflow detected ***: /usr/lib/pcp/bin/pmcd terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/439572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700827] Re: [MIR] pcp package
Update. We've written replacements for system() and popen() that use execvp() and do not call /bin/sh -c "some command". These are __pmProcessExec() and __pmProcessPipe() in libpcp. All uses of system() and popen() in the core libpcp library have been converted to the new routines. There are 16 other uses of popen() in C code outside the core libpcp library that will be converted shortly. There is one popen() in some Python code that will need additional thought/review. There are only a handfull of other system() uses that do not involve literal strings ... we'll work through those. And I've made some changes for the x = realloc(x, ...) pattern, but so far all of these are on fatal error paths that lead directly to exit(), so I'll continue to work on these as time permits, but don't view these as a significant risk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700827 Title: [MIR] pcp package To manage notifications about this bug go to: https://bugs.launchpad.net/pcp/+bug/1700827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1700827] Re: [MIR] pcp package
On 29/08/17 10:44, Eric Desrochers wrote: > @Dariusz, Seth, Ken, Frank and anyone else involved in this discussion. > > What would you guys think if we schedule a hangout call between > Canonical & PCP upstream folks to discuss about all this ? Sounds good to me ... we may be a little timezone challenged ... I'm in Melbourne, Frank's in Toronto, ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700827 Title: [MIR] pcp package To manage notifications about this bug go to: https://bugs.launchpad.net/pcp/+bug/1700827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700827] Re: [MIR] pcp package
Apropos the CVE's all of these have been completely addressed in past PCP releases. CVE-2012-5530 - fixed in PCP 3.6.10 (released 19 Nov 2012) CVE-2012-3421, CVE-2012-3420, CVE-2012-3419 and CVE-2012-3418 - all fixed in PCP 3.6.5 (released 16 Aug 2012) CVE-2001-0823 - fixed in PCP 2.2.1 (released 21 Jun 2001) I am in agreement with Frank, that we'd really like to see some specific issues identified that are barriers to inclusion of PCP in main. If we had this list we're more than happy to work through them ... based on 20+ years of experience with PCP development and deployment in many big and ugly environments, I am confident that most of them will turn out to be false positives, others can be fixed. Thanks for the effort so far with the review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700827 Title: [MIR] pcp package To manage notifications about this bug go to: https://bugs.launchpad.net/pcp/+bug/1700827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574437] Re: valgrind vex the `impossible' happened: isZeroU
+1 for getting a fix please (like you're competitor distros have been able to do). This is killing PCP (www.pcp.io) QA on all Ubuntu 16.04 platforms. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574437 Title: valgrind vex the `impossible' happened: isZeroU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1574437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
