I have a Start Up Problem, Could do with some help

I have a problem when I try to start Node 2 in a cluster, Node 1 starts fine, here is the error reported in two phases, Firstly when I start up there are many of these.

Currently running 6.12.17, but was the same yesterday running 6.2.26.

2019-06-11 09:31:27.901 +0000 [WARN|0082e|org.apache.activemq] :: Failed to connect to [tcp://172.31.15.112:61616, tcp://172.31.26.230:61616] after: 650 attempt(s) continuing to retry.
2019-06-11 09:46:28.367 +0000 [WARN|0082e|org.apache.activemq] :: Failed to connect to [tcp://172.31.15.112:61616, tcp://172.31.26.230:61616] after: 660 attempt(s) continuing to retry.
2019-06-11 10:01:28.833 +0000 [WARN|0082e|org.apache.activemq] :: Failed to connect to [tcp://172.31.15.112:61616, tcp://172.31.26.230:61616] after: 670 attempt(s) continuing to retry.
2019-06-11 10:16:29.409 +0000 [WARN|0082e|org.apache.activemq] :: Failed to connect to [tcp://172.31.15.112:61616, tcp://172.31.26.230:61616] after: 680 attempt(s) continuing to retry.
2019-06-11 10:31:29.913 +0000 [WARN|0082e|org.apache.activemq] :: Failed to connect to [tcp://172.31.15.112:61616, tcp://172.31.26.230:61616] after: 690 attempt(s) continuing to retry.
2019-06-11 10:46:30.252 +0000 [WARN|0082e|org.apache.activemq] :: Failed to connect to [tcp://172.31.15.112:61616, tcp://172.31.26.230:61616] after: 700 attempt(s) continuing to retry.
2019-06-11 11:01:30.475 +0000 [WARN|0082e|org.apache.activemq] :: Failed to connect to [tcp://172.31.15.112:61616, tcp://172.31.26.230:61616] after: 710 attempt(s) continuing to retry.
2019-06-11 11:16:31.016 +0000 [WARN|0082e|org.apache.activemq] :: Failed to connect to [tcp://172.31.15.112:61616, tcp://172.31.26.230:61616] after: 720 attempt(s) continuing to retry.
2019-06-11 11:31:31.419 +0000 [WARN|0082e|org.apache.activemq] :: Failed to connect to [tcp://172.31.15.112:61616, tcp://172.31.26.230:61616] after: 730 attempt(s) continuing to retry.

Then Further down there is an error thrown, that leaves this trace :
2019-06-11 11:33:49.075 +0000 [ERROR|007d0|main] :: Error starting Looker: Unknown error (SystemCallError) -
org/jruby/RubyIO.java:1474:in write' org/jruby/RubyIO.java:1445:inwrite’
org/jruby/RubyIO.java:2636:in write' org/jruby/RubyIO.java:2503:inputs’
org/jruby/RubyKernel.java:536:in puts' uri:classloader:/helltool-component-build/lib/helltool/runner.class:280:instart’
uri:classloader:/helltool-component-build/lib/helltool/cli.class:87:in start' uri:classloader:/gems/thor-0.15.4/lib/thor/task.rb:27:inrun’
uri:classloader:/gems/thor-0.15.4/lib/thor/invocation.rb:120:in invoke_task' uri:classloader:/gems/thor-0.15.4/lib/thor.rb:275:indispatch’
uri:classloader:/gems/thor-0.15.4/lib/thor/base.rb:425:in start' uri:classloader:/helltool-component-build/bin/helltool:29:in
org/jruby/RubyKernel.java:974:in load' uri:classloader:/META-INF/main.rb:1:in
org/jruby/RubyKernel.java:956:in require' uri:classloader:/META-INF/main.rb:1:in(root)’
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `’

Any and all help would be appreciated.

Paul

Lemme preface any speculation by saying you should probably reach out to looker support via chat or help.looker.com since this is likely going to be in depth… The cluster sounds kinda borked.

This is getting out of my wheelhouse, but I think this is because not all brokers are communicating with one another properly, possible because you have multiple master broker nodes. I’d reach out to Looker support directly and they can help you get un-stuck.