pcp
[Top] [All Lists]

Re: [pcp] FC18 status

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] FC18 status
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Wed, 15 May 2013 11:45:04 +1000
Cc: PCP Mailing List <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <542720185.1247002.1368518261886.JavaMail.root@xxxxxxxxxx>
References: <5191EB20.8020405@xxxxxxxxxxxxxxxx> <542720185.1247002.1368518261886.JavaMail.root@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
On 14/05/13 17:57, Nathan Scott wrote:
Hi Ken,

----- Original Message -----
rpm build working again after putting VM in dumper and re-installing
Fedora 18 from scratch ... no idea what was the problem.

But the first time I installed the rpms, I see this ...

Rebuilding PMNS ...
Starting pmcd ...
Starting pmlogger ...
Performance Co-Pilot starting inference engine(s) ...
Redirecting to /bin/systemctl condrestart  pmwebd.service
Failed to issue method call: Unit pmwebd.service failed to load: No such
file or directory. See system logs and 'systemctl status pmwebd.service'
for details.

Looks like we're somehow (unexpectedly) triggering systemd for this guy
which we don't do for the other daemons.

Performance Co-Pilot starting pmproxy (logfile is
/var/log/pcp/pmproxy/pmproxy.log) ...
kenj@localhost:~/src/pcp$ pcp

Strange indeed that pmproxy is all good - the two are carbon copies of
each other in terms of init scripting fu.

I think this is the same as Jeff's issue on SuSE ... if there is no libmicrohttpd, we don't build pmwebd (correct) but then the packaging/install scripts don't understand that pmwebd may not be in the package ... I think the patch I posted (which I've committed to my local tree but not pushed yet) fixes this as well.

<Prev in Thread] Current Thread [Next in Thread>