----- Original Message ----- > From: "Martin Willemsma" <mwillem...@gmail.com> > To: puppet-users@googlegroups.com > Sent: Saturday, June 9, 2012 4:37:05 AM > Subject: Re: [Puppet Users] MCollective not all nodes answer to commands when > using aes_security plugin > > I currently have two different MQ's running, one activeMQ running on > a node and a rabbitMQ on a different one. > If I switch my mcollective servers from one broker to another and do > a 'mco ping' while the nodes are registering with the other broker I > hit a threshold somewhere.
are you saying you're trying to mix activemq and rabbitmq in the same setup? > > Scenario: > > I start a 'mco ping' from 2 clients simultaneously. Each client > registered to a different broker. Both can successfully do a ping > to > all nodes. > > client 1 - > > 199.49 ms > 238.21 ms > 275.27 ms > 312.39 ms > 350.79 ms > 387.84 ms > [...] > 2624.43 ms > 2993.36 ms > > ---- ping statistics ---- > 50 replies max: 2993.36 min: 199.49 avg: 1030.95 > > client 2 - > > 469.72 ms > 492.41 ms > 516.31 ms > 541.34 ms > 638.03 ms > 664.93 ms > [...] > 4254.50 ms > 4276.60 ms > > ---- ping statistics ---- > 160 replies max: 4276.60 min: 469.72 avg: 2414.46 > > The command does complete and ping times start way lower. I found > some nodes with <512 Mb ram. Could it be possible that these are causing > problem because they are swapping and do not respond quick enough and > somehow that reply gets lost in translation causing the mechanism to > break? they wont cause everything to slow down - unless they are either your client or your broker - those slow machines will just respond slowly > If I do a 'mco rpc service status service=ssh' on both clients > > client 1 - > > Determining the amount of hosts matching filter for 2 seconds .... 50 > > * [ ============================================================> ] > 50 / 50 > > > client 2 - > > Determining the amount of hosts matching filter for 2 seconds .... > warn: Could not decrypt message from client: #<Class:0x7f16ac7ba268>: > execution expired > warn: Ignoring a message that did not pass security validations this might be related to not enough entropy on your machine running the client perhaps? is this still with AES or ...? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
