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
