[Bug 1850281] Re: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1
Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: pcp (Ubuntu Eoan) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
>From the logwatch report: Packages Updated: cockpit-pcp-226-1.fc32.armv7hl -> cockpit-pcp-227-1.fc32.armv7hl **Unmatched Entries** Sep 9 04:11:30 ERROR Error in POSTIN scriptlet in rpm package cockpit-pcp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
> systemctl list-dependencies | grep pmlogger_check Empty result. > systemctl disable pmlogger_check.path Removed /etc/systemd/system/pmlogger.service.requires/pmlogger_check.path. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
(In reply to Кощеев from comment #50) > pcp version 5.2.0 > > $ find /usr/lib/systemd/system /etc/systemd/system -type f | xargs grep > pmlogger_check.path > grep: /usr/lib/systemd/system/system-systemdx2dcryptsetup.slice: Нет такого > файла или каталога well that didnt find anything, but we only looked for files, not syslinks. How about: systemctl list-dependencies | grep pmlogger_check Maybe we have an upgrade issue where deprecated units or dependencies aren't being cleaned up properly. To remove stale dependencies: systemctl disable pmlogger_check.path thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
Hi all, The current release of PCP for f32 is pcp-5.2.0-1.fc32.x86_64.rpm https://dl.fedoraproject.org/pub/fedora/linux/updates/32/Everything/x86_64/Packages/p/pcp-5.2.0-1.fc32.x86_64.rpm contains all of the PCP service units and none of them reference pmlogger_check.path. So exactly what version of PCP are you running? Have you done a 'systemctl daemon-reload' after upgrading? What is still referencing pmlogger_check.path? find /usr/lib/systemd/system /etc/systemd/system -type f | xargs grep pmlogger_check.path thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
pcp version 5.2.0 $ find /usr/lib/systemd/system /etc/systemd/system -type f | xargs grep pmlogger_check.path grep: /usr/lib/systemd/system/system-systemdx2dcryptsetup.slice: Нет такого файла или каталога -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
I get this when I run that command: [root@MAGGIE ~]# rpm -ql pcp | grep pmlogger_check /usr/lib/systemd/system/pmlogger_check.path /usr/lib/systemd/system/pmlogger_check.service /usr/lib/systemd/system/pmlogger_check.timer /usr/libexec/pcp/bin/pmlogger_check Are you telling me now that this doesn't completely re-install PCP? systemctl stop pmcd pmie pmlogger pmproxy redis > /dev/null 2>&1 dnf remove --noautoremove -y pcp\* rm -rf /etc/pcp* /var/lib/pcp/ /var/log/pcp/ /var/lib/dnf/yumdb/p /var/cache/dnf/pcp* systemctl daemon-reload dnf install -y pcp cockpit-pcp systemctl daemon-reload systemctl stop pmcd pmie pmlogger pmproxy systemctl start pmcd pmie pmlogger pmproxy If that is wrong, how I completely reinstall it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
Fernando,
the logs you sent me indicate pmlogger is starting but exiting very soon
after (and then being repeatedly restarted by systemd). I don't see any
evidence of a systemd unit configuration problem. The PCP archives are
being created, but have a corrupted label record and I can't read any of
them. e.g. here's what I get with some debugging enabled trying to
examine one of your recent faulty archives :
$ pminfo -Dlog,logmeta -a 20200504.11.16-00
__pmLogOpen: inspect file "./20200504.11.16-00.0"
__pmLogOpen: inspect file "./20200504.11.16-00.index"
__pmFopen("./20200504.11.16-00.index", "r"): no decompress
__pmLogOpen: inspect file "./20200504.11.16-00.meta"
__pmFopen("./20200504.11.16-00.meta", "r"): no decompress
__pmFopen("./20200504.11.16-00.0", "r"): no decompress
__pmLogChkLabel: fd=3 vol=0 trailer read -> 4 (expect 4) or bad trailer
len=8650752 (expected 132)
pminfo: Cannot open archive "20200504.11.16-00": Illegal label record at start
of a PCP archive log file
This may indicate a bug in pmlogger / libpcp. Can you please try running
pmlogger manually, e.g.
$ pmlogger -c config.default -h local: -l- -s 5 -t 1 /tmp/testlog
Please send me the output of the above command (-l- will print messages
to stdout) and also /var/lib/pcp/config/pmlogger/config.default and also
/tmp/testlog.*
If the above command fails, please: rm
/var/lib/pcp/config/pmlogger/config.default and then systemctl restart
pmlogger (this will regenerate a new config.default since yours may be
corrupted somehow). After restarting the pmlogger service, please also
send me the output of: systemctl status pmlogger; journalctl -xe -u
pmlogger.service
Also, back in Comment #20, you said you have systemd.i686
241-12.git323cdf4.fc30 installed. Are you running a 32bit machine?
Regards
--
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850281
Title:
package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp
package post-installation script subprocess returned error exit status
1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
Hi Mark, I've rebooted at least 3 times since I did the update and it's still the same, but I tried those commands and got this: [root@MAGGIE ~]# systemctl restart pmlogger Job for pmlogger.service failed because the service did not take the steps required by its unit configuration. See "systemctl status pmlogger.service" and "journalctl -xe" for details. The details are: May 04 13:14:26 MAGGIE.mydomain.com systemd[1]: Failed to start Performance Metrics Archive Logger. -- Subject: A start job for unit pmlogger.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit pmlogger.service has finished with a failure. -- -- The job identifier is 13372 and the job result is failed. May 04 13:14:26 MAGGIE.mydomain.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:> May 04 13:14:26 MAGGIE.mydomain.com systemd[1]: Starting Check pmlogger instances are running... -- Subject: A start job for unit pmlogger_check.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit pmlogger_check.service has begun execution. -- -- The job identifier is 13479. May 04 13:14:27 MAGGIE.mydomain.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:> May 04 13:14:27 MAGGIE.mydomain.com audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s> May 04 13:14:27 MAGGIE.mydomain.com systemd[1]: pmlogger.service: Scheduled restart job, restart counter is at 4. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit pmlogger.service has been scheduled, as the result for -- the configured Restart= setting for the unit. May 04 13:14:27 MAGGIE.mydomain.com systemd[1]: Stopped Performance Metrics Archive Logger. -- Subject: A stop job for unit pmlogger.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit pmlogger.service has finished. -- -- The job identifier is 13582 and the job result is done. May 04 13:14:27 MAGGIE.mydomain.com systemd[1]: Starting Performance Metrics Archive Logger... -- Subject: A start job for unit pmlogger.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit pmlogger.service has begun execution. -- -- The job identifier is 13582. I have gathered all the files into archive and will email you them separately - hope that's ok. Cheers, Fernando -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
I'm now on 5.1.0-1.fc31 and this problem still exists and just fills up the log with these messages constantly. Is this ever going to be fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
Fedora 32 armv7l, Fedora 32 x86_64: Unit pmlogger_check.path not found. $ rpm -ql pcp | grep pmlogger_check /usr/lib/systemd/system/pmlogger_check.service /usr/lib/systemd/system/pmlogger_check.timer /usr/libexec/pcp/bin/pmlogger_check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
You installation of PCP is broken - this: pmie_check.service: Failed at step EXEC spawning /usr/libexec/pcp/bin/pmie_check: No such file or directory says you are missing critical files that are part of PCP: $ rpm -ql pcp | grep pmlogger_check /usr/lib/systemd/system/pmlogger_check.path /usr/lib/systemd/system/pmlogger_check.service /usr/lib/systemd/system/pmlogger_check.timer /usr/libexec/pcp/bin/pmlogger_check ... which is unrelated to the issue in this BZ. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
Hi Mark, Ran the command Last login: Mon May 4 13:10:44 2020 from 192.168.1.19 [root@MAGGIE ~]# pmlogger -c config.default -h local: -l- -s 5 -t 1 /tmp/testlog Log for pmlogger on MAGGIE.star-one.co.uk started Tue May 5 07:32:37 2020 preprocessor cmd: /usr/libexec/pcp/bin/pmcpp -rs /var/lib/pcp/config/pmlogger/config.default -I /var/lib/pcp/config/pmlogger Config parsed Starting logger for host "MAGGIE.mydomain.com" via "local:" Archive basename: /tmp/testlog pmlogger: Sample limit reached, exiting Log finished Tue May 5 07:32:40 2020 Will send you the rest via email in due course. As for #20, no 64bit even at the time of the comment, but it looks right now. [root@MAGGIE ~]# dnf list systemd* Last metadata expiration check: 2:09:43 ago on Tue 05 May 2020 05:26:48 CEST. Installed Packages systemd.x86_64 243.8-1.fc31 @updates systemd-bootchart.x86_64233-5.fc31 @fedora systemd-libs.x86_64 243.8-1.fc31 @updates systemd-pam.x86_64 243.8-1.fc31 @updates systemd-rpm-macros.noarch 243.8-1.fc31 @updates systemd-udev.x86_64 243.8-1.fc31 @updates243.8-1.fc31 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
(In reply to Fernando Viñan-Cano from comment #40) > I'm now on 5.1.0-1.fc31 and this problem still exists and just fills up the > log with these messages constantly. > > Is this ever going to be fixed? Hi Fernando, it should be fixed now. Perhaps after your upgrade you need to run systemctl daemon-reload and then systemctl restart pmlogger ? If that doesn't work, please send your logs and a tarball of /etc/pcp. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
I am still getting these problems even though I am now upgraded to Fedora 32, and I used the uninstall/cleanup script from once before to try and sort out the PCP package. What is going on? June 29, 2020 8:19 AM Failed to start pmie_check.service. systemd 8:19 AM pmie_check.service: Failed at step EXEC spawning /usr/libexec/pcp/bin/pmie_check: No such file or directory systemd 8:19 AM pmie_check.service: Failed to execute command: No such file or directory systemd 8:19 AM Failed to start pmlogger_check.service. systemd 8:19 AM pmlogger_check.service: Failed at step EXEC spawning /usr/libexec/pcp/bin/pmlogger_check: No such file or directory systemd 8:19 AM pmlogger_check.service: Failed to execute command: No such file or directory systemd 8:19 AM pmlogger_daily-poll.timer: Unit to trigger vanished. systemd 8:19 AM pmie_daily.timer: Unit to trigger vanished. systemd 8:19 AM pmlogger_daily.timer: Unit to trigger vanished. systemd 8:19 AM pmie_check.timer: Unit to trigger vanished. systemd 8:19 AM pmlogger_check.timer: Unit to trigger vanished. systemd 8:15 AM Failed to start Performance Metrics Archive Logger. systemd 2 8:15 AM pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log root 8:15 AM Failed to start Performance Metrics Archive Logger. systemd 8:15 AM pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log root 8:14 AM Failed to start Performance Metrics Archive Logger. systemd 8:14 AM pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log root 8:14 AM Failed to start Performance Metrics Archive Logger. systemd 8:14 AM pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log root 8:14 AM Failed to start Performance Metrics Archive Logger. systemd 8:14 AM pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log root 8:06 AM Failed to start Check pmlogger instances are running. systemd 8:06 AM Failed to start Performance Metrics Archive Logger. systemd 8:06 AM Failed to start Check pmlogger instances are running. systemd 8:06 AM Failed to start Performance Metrics Archive Logger. systemd 8:06 AM pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log root 8:06 AM Failed to start Performance Metrics Archive Logger. systemd 8:06 AM pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log root 8:06 AM Failed to start Performance Metrics Archive Logger. systemd 8:06 AM pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log root 8:06 AM Failed to start Performance Metrics Archive Logger. systemd 8:06 AM pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log root 8:06 AM Failed to start Performance Metrics Archive Logger. systemd 8:06 AM pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log root 8:06 AM Failed to start Performance Metrics Archive Logger. systemd 8:06 AM pmlogger_daily failed - see /var/log/pcp/pmlogger/pmlogger_daily-K.log root 8:05 AM pam_systemd(crond:session): Failed to get user record: Connection timed out crond [root@MAGGIE ~]# cat /var/log/pcp/pmlogger/pmlogger_daily-K.log cat: /var/log/pcp/pmlogger/pmlogger_daily-K.log: No such file or directory Installed Packages pcp.x86_64 5.1.1-1.fc32 @updates pcp-conf.x86_64 5.1.1-1.fc32 @updates pcp-libs.x86_64 5.1.1-1.fc32 @updates pcp-selinux.x86_64 5.1.1-1.fc32 @updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
In Fedora 31 for ARMv7 this error still exists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281] Re: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1
** Changed in: pcp (Fedora) Status: In Progress => Fix Released ** Bug watch added: github.com/performancecopilot/pcp/issues #798 https://github.com/performancecopilot/pcp/issues/798 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
Closed as per the fix from Comment #30 and verified with Marko's recipe from Comment #21. The additional work for changing the pmlogger service to use type=notify is a separate issue being tracked in upstream issue https://github.com/performancecopilot/pcp/issues/798 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
@Mark happy to test, just tell me how. I'm not a Linux admin, this server is just a hobby thing I use to run a few things, so no idea how to "test a build from current master branch" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
I would also support a new PCP upstream release to address this or at least a new updated build for the affected distributions with selected fixes included (instead of waiting over a month for the next scheduled PCP release). Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
@Mark, thanks, once I see it pushed to my machine when I check for updates I'll check what happens on my system and let you know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
(In reply to Marko Myllynen from comment #32) > I would also support a new PCP upstream release to address this or at least > a new updated build for the affected distributions with selected fixes > included (instead of waiting over a month for the next scheduled PCP > release). Thanks. agree we should ship an early update to fix the install issue - a month is a long time. However, I think it would first be a good idea to ask Fernando to test a build from current master branch to if the issues he's seeing still persist. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
Committed an upstream patch that fixes the service timeout reproducer test posted by Marko in Comment#21, along with a bunch of QA updates. commit 0f3a1fa7d0d7a898acf2ee4a6f23b626d4fb7362 Author: Mark Goodwin Date: Wed Nov 13 09:50:57 2019 +1100 logutil: fix pmlogger service timeout on virgin install RHBZ#1721223 - pmlogger.service: Failed with result 'timeout' PCP GH#792 Do not invoke pmlogger_daily -K to compress archives from pmlogger_check on a virgin install - it confuses systemd's Type=forking exit status checks, resulting in the pmlogger service timing out. There is nothing to compress anyway! This fixes the installation issues reported by Marko in BZ#1721223 but does not update the service configs - they are still Type=forking and so there will still be some (benign) complaints from systemd as reported in the BZ. Related QA updates are following. The above has been pushed to the current master branch (5.0.2 devel), but has not been built or pushed to any Fedora or Deb/Ubuntu repos. @Fernando and others, after building and installing latest master branch with this patch if you're still seeing issues with the pmlogger service or pmlogger_daily and pmlogger_check scripts failing and/or the pmie service failing to start then we need to examine your system and installation. It Works For Me (and Marko tested it too). Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
Hi Fernando, I can repro this issue on a virgin install (beginning with no PCP installed at all). This fails to start the pmlogger service with a timeout - as reported. If I then: systemctl restart pmlogger.service it seems to work OK and we end up with the pmlogger service running. Are you seeing that too? Also, can you please try and start the pmie service after a virgin install? The pmie systemd config is very similar to the pmlogger service and the rc scripts are also basically the same (just different service name and paths etc). This works for both a virgin install and for a restart. Can you please check that too? systemctl start pmie.service Thanks -- Mark -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281]
nfo/systemd-devel -- -- Automatic restarting of the unit pmlogger.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Nov 08 08:03:21 MAGGIE systemd[1]: Stopped Performance Metrics Archive Logger. -- Subject: A stop job for unit pmlogger.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit pmlogger.service has finished. -- -- The job identifier is 393750 and the job result is done. Nov 08 08:03:21 MAGGIE audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='> Nov 08 08:03:21 MAGGIE audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='u> Nov 08 08:03:21 MAGGIE systemd[1]: Starting Performance Metrics Archive Logger... -- Subject: A start job for unit pmlogger.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit pmlogger.service has begun execution. -- -- The job identifier is 393750. Nov 08 08:03:21 MAGGIE pmlogger[96400]: Starting pmlogger ... Nov 08 08:03:21 MAGGIE systemd[1]: pmlogger.service: Can't open PID file /run/pcp/pmlogger.pid (yet?) after start: No such file > [root@MAGGIE ~]# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281] Re: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1
Launchpad has imported 28 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1721223. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-06-17T15:33:00+00:00 paul.destefano-redhat2 wrote: Description of problem: Everyday, I get these messages: Jun 17 00:10:13 systemd[1]: pmlogger.service: New main PID 4059499 does not belong to service, and PID file is not owned by root. Refusing. Jun 17 00:10:13 systemd[1]: pmlogger.service: New main PID 4059499 does not belong to service, and PID file is not owned by root. Refusing. Jun 17 00:11:38 systemd[1]: pmlogger.service: Start operation timed out. Terminating. Jun 17 00:11:38 systemd[1]: pmlogger.service: Failed with result 'timeout'. Jun 17 00:11:38 systemd[1]: Failed to start Performance Metrics Archive Logger. Jun 17 00:11:46 systemd[1]: pmlogger.service: Supervising process 4066656 which is not our child. We'll most likely not notice when it exits. How can I fix the service so that it doesn't give errors every day? Version-Release number of selected component (if applicable): pcp-4.3.2-1.fc30.x86_64 How reproducible: Happens every day. Steps to Reproduce: 1. No action is required to produce this error. I guess you need to have PCP services enabled and running, though. Actual results: errors and warnings Expected results: no errors or warnings Additional info: PCP data is being collected. I don't really know if there is anything wrong with the data, but I assume it is fine. Reply at: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/comments/0 On 2019-07-02T13:27:54+00:00 ferd352+000143 wrote: I can report the same issue, it was happening when my old box was running Fedora 29, then when upgraded to Fedora 30 it continued. Now with my brand new Fedora 30 machine the issue continues. SELinux is not reporting any blocks, and then I had this disabled with F29 so it wasn't that. What it does effect is the server is unable to store any more than a day of performance data. Same version of pcp. Reply at: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/comments/1 On 2019-07-15T05:28:29+00:00 mgoodwin wrote: This issue seems to be similar to BZ #1583159 - "Sample service file vncserver@.service is out of date with systemd changes", which was caused by an update to systemd in response to an upstream issue stating that PID run files should be owned by root, not an unprivileged user (such as 'pcp' in our case). The upstream systemd RFE requesting this is https://github.com/systemd/systemd/issues/6632 and the change that introduced the PID ownership check is https://github.com/systemd/systemd/commit/db256aab13d8a89d583ecd2bacf0aca87c66effc. The change subsequently resulted in a spate of issues with various service daemons unable to start correctly because their PID file was not owned by root (e.g. xinetd and other services, see for example https://github.com/systemd/systemd/issues/8085). As a result, systemd was subsequently updated to not follow symlinks, which apparently circumvented the original issue. The end result is that /run/PID files should be owned by root and symlinks should not be used. An example of an updated service file to comply with the new systemd is BZ #1583159. So I guess for PCP we're going to need to update the service unit files for all our services to be compatible with the newer versions of systemd. Exactly what changes to make is yet to be determined. Reply at: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/comments/2 On 2019-07-15T05:34:52+00:00 mgoodwin wrote: (In reply to Fernando Viñan-Cano from comment #1) > I can report the same issue, it was happening when my old box was running > Fedora 29, then when upgraded to Fedora 30 it continued. Now with my brand > new Fedora 30 machine the issue continues. > > SELinux is not reporting any blocks, and then I had this disabled with F29 > so it wasn't that. > > What it does effect is the server is unable to store any more than a day of > performance data. Same version of pcp. Fernando, can you provide any more details about your system not being able to store more than one day of data? e.g. compressed tarball of your logs below /var/log/pcp/pmlogger and journalctl -b -u pmlogger. If you don't want to attach them to this BZ, could you mail them to me? This might be a separate issue not related to the systemd service issue reported in this BZ becau
[Bug 1850281] Re: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1
We see this in our Cockpit test image creation as well. ** Bug watch added: Red Hat Bugzilla #1721223 https://bugzilla.redhat.com/show_bug.cgi?id=1721223 ** Also affects: pcp (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1721223 Importance: Unknown Status: Unknown ** Also affects: pcp (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: pcp (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: pcp (Ubuntu Eoan) Status: New => Confirmed ** Changed in: pcp (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850281] [NEW] package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1
Public bug reported: Tried to install pcp package but got error. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: pcp 4.3.4-1build1 ProcVersionSignature: Ubuntu 5.3.0-20.21-generic 5.3.7 Uname: Linux 5.3.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Tue Oct 29 11:04:58 2019 ErrorMessage: installed pcp package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-10-15 (378 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: pcp Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pcp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850281 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1850281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
