19:39:06 <barfield> greetings amigos! I have a headnode that I had to swap out to a different chassis. Trying to figure out why rabbitmq0/mdata:execute svc will not start is giving me a splitting headache
19:42:45 <barfield> anyone have any guidance on this? I hate erlang
19:43:28 <barfield> svcs -xv says registrar is not running, but svccfg export mdata:execute says that it depends on registrar WTF
19:43:32 <barfield> They depend on each other lol
19:43:54 <barfield> also there is this
19:43:54 <barfield>    Error: ur client cannot connect to AMQP broker.
19:43:54 <barfield>    Error: Results are only for local (headnode) services.
19:44:37 <barfield> oh weird I just noticed that there are two rabbit mq instances listed in sdcadm check-health
19:44:41 <barfield> one with a UUID of all 0's
19:44:58 <barfield> 00000000-0000-0000-0000-000000000000  rabbitmq               headnode  rabbitmq0     false
19:45:08 <barfield> 35a3d51f-2272-4e32-8bd5-6aea2411dc8c  rabbitmq               headnode  rabbitmq0     false
19:45:24 <barfield> checking sapi records
19:49:58 <barfield> cnapi keeps dying because it can't rabbitmq
20:09:27 <neuroserve> question - which one is the right one?
20:10:40 <bahamat> As with all compute node chassis swaps, the old UUID is not removed from Triton. You have to do that manually.
20:15:04 <barfield> In which place? I deleted it from cnapi and restarted cn-agent
20:15:33 <bahamat> You'll probably need to clean up nics and agents separately.
20:16:36 <barfield> I cleaned up all of the NICS already
20:17:26 <barfield> cmon agent turned out to be the culprit for all of that junk in cnapi under the headnode that I asked you about not long ago. The junk was in the agents.cmon-agent.uuid field
20:17:31 <barfield> I generated a new one and updated it
20:17:41 <barfield> But I am just not sure where else to update
20:18:12 <bahamat> Well sdcadm looks at sapi.