#mcollective

Hi guys,

I updated choria-mcollective_choria,choria-nats and choria-mcollective to the latest versions. Now I'm unable to run mco commands.

I receive this error in the logs "Received an unknown protocol 'choria:secure:request:1' message, ignoring - MCollective::SecurityValidationFailed"

Any ideas?

hmm

what version is the modules on that mcollectived?

one moment...

this shouldnt happen but if it does its likely a old mcollectived with a new client

when going to latest, as per rel notes, nodes first then the clients

mcollective_agent_filemgr/metadata.json: "version": "1.1.0",

mcollective_agent_package/metadata.json: "version": "4.5.0",

mcollective_agent_puppet/metadata.json: "version": "1.13.1",

mcollective_agent_service/metadata.json: "version": "3.1.5",

mcollective_choria/metadata.json: "version": "0.1.0",

mcollective/metadata.json: "version": "0.0.29",

mcollective_util_actionpolicy/metadata.json: "version": "2.2.0",

sure, but whats on that actual node

nats: version": "0.0.12"

"grep VERSION /opt/puppetlabs/mcollective/plugins/mcollective/util/choria.rb" one the one logging this

update nodes first then client

node is the mcollective server?

mcollectived machines

so typically leave where you run 'mco ....' from for last

hmm You mean with client the nats server? Sorry I don't get it..

'mco ....' thats a client, where you type the CLI commands

I thanks.

servers are the ones you are managing using that command

I get it.. :)

I am running an adhoc command that is taking too long to come back

im tired...

lemme stick a nohup on this and see what happens