On 09/03/2014 11:14 AM, Dave Brolley wrote:
Hi,
I'm getting the following while trying to install the latest rpms on
my f19 system:
>> sudo rpm -i pcp-3.9.10-1.x86_64.rpm pcp-conf-3.9.10-1.x86_64.rpm
pcp-debuginfo-3.9.10-1.x86_64.rpm pcp-doc-3.9.10-1.noarch.rpm
pcp-import-collectl2pcp-3.9.10-1.x86_64.rpm
pcp-import-iostat2pcp-3.9.10-1.x86_64.rpm
pcp-import-mrtg2pcp-3.9.10-1.x86_64.rpm
pcp-import-sar2pcp-3.9.10-1.x86_64.rpm pcp-libs-3.9.10-1.x86_64.rpm
pcp-libs-devel-3.9.10-1.x86_64.rpm pcp-manager-3.9.10-1.x86_64.rpm
pcp-pmda-infiniband-3.9.10-1.x86_64.rpm
pcp-testsuite-3.9.10-1.x86_64.rpm pcp-webapi-3.9.10-1.x86_64.rpm
perl-PCP-LogImport-3.9.10-1.x86_64.rpm
perl-PCP-LogSummary-3.9.10-1.x86_64.rpm
perl-PCP-MMV-3.9.10-1.x86_64.rpm perl-PCP-PMDA-3.9.10-1.x86_64.rpm
python-pcp-3.9.10-1.x86_64.rpm
warning: %post(pcp-3.9.10-1.x86_64) scriptlet failed, exit status 4
>> sudo service pcp status
Redirecting to /bin/systemctl status pcp.service
pcp.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
>> uname -a
Linux brolley-t530 3.14.17-100.fc19.x86_64 #1 SMP Thu Aug 14 17:17:26
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Using
sudo setenforce 0
gets me around this, but I'm sure that there is a more suitable setting.
Dave
|