On 10/06/2014 06:41 AM, Ken McDonell wrote:
This is a Centos 7 system, with avahi-daemon running
[ ... ]
pmcd is up
[ ... ]
but pmfind -m avahi fails, and so does qa/946
kenj@vm08:~/src/pcp/qa$ pmfind -m avahi
No pmcd servers discovered
No pmproxy servers discovered
No pmwebd servers discovered
I'd appreciate any clues that would help debug or explain this.
First possible problem is that avahi-devel was not available when PCP
was configured/built. Check your configure logs for problems finding the
needed avahi components. However, I would expect pmfind(1) report that
avahi is not supported in this case.
Next place to look is the pmcd log. If it failed to register itself with
avahi-daemon, then there should be some messages in the log.
The next, and most common cause of avahi-related problems is that the
mDNS port, udp 5353, is not open in the firewall. Try
avahi-browse -rt _pmcd._tcp
If that works, then pmfind should also work with avahi. avahi-browse is
part of the avahi-tools package.
I it looks like qa/646 checks that avahi-daemon is ok and checks that
service discovery is supported. We should probably create another
pmconfig(1) category, something like 'service_discovery_avahi' which
could be used to catch the first two problems above. I'm not sure how to
portably check that a port is open in the firewall and I'm not sure that
we can depend on avahi-tools being installed for checeking with
avahi-browse.
I hope this helps,
Dave
|