mcollective port change and ping issue
i am creating a second post (different from https://ask.puppet.com/question/26184...) because there is some data changing between the 2 use cases.
The case is simple
1/ install a PE
2/ dont create a new env : everything is done en production env
3/ add a second puppet agent (the one with the master + a new one)
Those 2 agents are listed in the PE MCollective Classification do a mco ping : all is OK because ActiveMQ listens on default port 61613.
Change the port to 61617 or 2016, or whatever you want :
on PE MCollective classification : on class puppetenterprise::profile::mcollective::agent, set stompport=YOURPORTVALUE
on PE ActiveMQ Broker classification: on class puppetenterprise::profile::amq::broker set stompport=YOURPORTVALUE
Start puppet runs on the both nodes to update the Broker port, and the mcollective for both agents.
In /var/log/puppetlabs/mcollective.log :
[2016-05-18T10:15:56.828924 #15660] INFO -- : activemq.rb:119:in `on_connected' Connected to stomp+ssl://email@example.com:YOURPORTVALUE
=> the connection of the agents to the brokers are OK.
However, the mco ping doesn't responde.
In my use case, the default agent provided with PE is a RedHat agent. The added agent is a Windows 2008 R2 agent.
=> the same non responsive situations appears with windows and linux agents.
Am i doing something wrong while trying to change the port on which the PE ActiveMQ Brokers listens to the connected agents?
Thanks a lot for your answers, Guillaume