Issues with linux mco discovery and report backs...
Within the last month, our CentOS 6 machines revved to 2.8.1 of MCollective. The Puppet Master is able to MCO ping our windows machines in MCollective and itself, however, the CentOS machines we have are not responding back to MCO ping.
We have a reboot process which involves "mco rpc --agent=reboot --action=reboot -I /^[Ee][Ss]/"
Where it is to reboot the CentOS machines with names starting in 'es'.
However, it is not seen by those machines. If we do the command but put in '-I es-1 -I es-2'... the machines see the request, however, do not return back to the caller that it is doing so, so we get no response and have to check it some other means.
When we send out the command "mco rpc rpcutil get_fact fact=operatingsystem -I /^[Ee][Ss]/" we don't get a response back from those systems, it times out
With debugging, we do see:
warn 2015/04/03 11:24:06: client.rb:251:in `start_receiver' Could not receive all responses. Expected : 1. Received : 0
We are using ActiveMQ connector and earlier in March, we saw a lot of our CentOS machines bomb out of mCollective as it could not find the Activemq.ddl until I made a symbolic link to the connectors to the location was searching.
I am at a loss to the issue we are having now and wondering if anyone else has ideas why mcollective broke for linux. We do see our windows mcollective with no issue however.