pcp
[Top] [All Lists]

Re: [pcp] FC18 status

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] FC18 status
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue, 14 May 2013 03:57:41 -0400 (EDT)
Cc: PCP Mailing List <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5191EB20.8020405@xxxxxxxxxxxxxxxx>
References: <5191EB20.8020405@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: UxXkbP+4Htt6DAClEO8kchHDQFmokQ==
Thread-topic: FC18 status
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.

BTW, 3.8.0 was tagged and platform builds began ~1hour ago, so this is
now minor-point-release fix fodder.

cheers.

--
Nathan

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