On 10/04/13 13:03, Frank Ch. Eigler wrote:
Ken McDonell <kenj@xxxxxxxxxxxxxxxx> writes:
I'm hoping someone else has seen this, or could suggest where to look.
[...]
I am seeing a bunch of QA failures, and indeed any remote PCP client command
fails the same way. The symptom is
[...]
__pmConnectPMCD(vm03): pmcd connection port=44321 failed: No route to host
pmNewContext(1, vm03) -> -113, curcontext=-1
pmprobe: Cannot connect to PMCD on host "vm03": No route to host
[...]
Firewalling? (iptables -L / firewalld?)
Thanks Frank.
I did have firewall configuration on my vm setup checklist, but somehow
missed it when I set up this host.
Enabling TCP ports 4321, 44321, 44322, 4330-4339 (up to 10 pmloggers)
and 4323 in the firewalld configuration greatly improved the QA results
with more than half the previous failures now passing.
Cheers, Ken.
|