[rabbitmq-discuss] Federation/Connection issues

Wed Mar 26 14:29:32 GMT 2014

We see some errors related to users that were deleted in the past (user_does_not_exist).  It appears there were some artifacts in our config from when we changed our fed routing structure to prevent duplicate messages.  Some of our engineers removed those artifacts, but now when we load all the existing federation exchanges (although showing green for their upstreams) don't work unless we set up a new queue with the same routing key in the bindings.  I'm checking the logs to see if we have any new errors related to this.  I've attached some of the errors for you perusal, if I find new ones I'll send those up as well.

=ERROR REPORT==== 24-Mar-2014::09:54:58 ===
** Generic server <0.6301.0> terminating
 ** Last message in was {'$gen_cast',maybe_go}
** When Server state == {not_started,
                         {{upstream,
                           [<<"amqp://shared_federation:shared_federation@localhost:5672/fed">>],
                            <<"e.fed.topic.tofed">>,<<"e.fed.topic.tofed">>,
                           1000,2,1,none,none,false,'on-confirm',none,
                           <<"datamartStage_to_fed">>},
                           {upstream_params,
                           <<"amqp://shared_federation:shared_federation@localhost:5672/fed">>,
                           {amqp_params_network,<<"shared_federation">>,
                             <<"shared_federation">>,<<"fed">>,"localhost",
                            5672,0,0,0,infinity,none,
                            [#Fun<amqp_uri.7.121371571>,
                              #Fun<amqp_uri.7.121371571>],
                            [],[]},
                           {exchange,
                            {resource,<<"fed">>,exchange,
                              <<"e.fed.topic.tofed">>},
                            topic,true,false,false,[],
                            [{federation,[]}],
                            [{vhost,<<"datamartStage">>},
                              {name,<<"federation enabled">>},
                             {pattern,<<"(^|.*\\.)fed($|\\..*)">>},
                             {'apply-to',<<"exchanges">>},
                              {definition,
                              [{<<"federation-upstream-set">>,<<"all">>}]},
                             {priority,60}],
                            {[],[rabbit_federation_exchange]}},
                            <<"amqp://localhost:5672/fed">>,
                           [{<<"uri">>,longstr,
                             <<"amqp://localhost:5672/fed">>},
                             {<<"virtual_host">>,longstr,<<"fed">>},
                            {<<"exchange">>,longstr,<<"e.fed.topic.tofed">>}]},
                           {resource,<<"datamartStage">>,exchange,
                           <<"e.fed.topic.tofed">>}}}
** Reason for termination ==
** {error,user_does_not_exist}

=ERROR REPORT==== 24-Mar-2014::09:54:58 ===
** Generic server <0.6310.0> terminating
** Last message in was {'$gen_cast',maybe_go}
** When Server state == {not_started,
                         {{upstream,
                            [<<"amqp://shared_federation:shared_federation@localhost:5672/fed">>],
                           <<"e.fed.topic">>,<<"e.fed.topic">>,1000,2,1,none,
                            none,false,'on-confirm',none,
                           <<"datamartStage_to_fed">>},
                          {upstream_params,
                           <<"amqp://shared_federation:shared_federation@localhost:5672/fed">>,
                            {amqp_params_network,<<"shared_federation">>,
                            <<"shared_federation">>,<<"fed">>,"localhost",
                             5672,0,0,0,infinity,none,
                            [#Fun<amqp_uri.7.121371571>,
                             #Fun<amqp_uri.7.121371571>],
                            [],[]},
                            {exchange,
                            {resource,<<"fed">>,exchange,<<"e.fed.topic">>},
                            topic,true,false,false,[],
                             [{federation,[]}],
                            [{vhost,<<"datamartStage">>},
                             {name,<<"federation enabled">>},
                             {pattern,<<"(^|.*\\.)fed($|\\..*)">>},
                              {'apply-to',<<"exchanges">>},
                             {definition,
                              [{<<"federation-upstream-set">>,<<"all">>}]},
                              {priority,60}],
                            {[],[rabbit_federation_exchange]}},
                           <<"amqp://localhost:5672/fed">>,
                           [{<<"uri">>,longstr,
                              <<"amqp://localhost:5672/fed">>},
                            {<<"virtual_host">>,longstr,<<"fed">>},
                            {<<"exchange">>,longstr,<<"e.fed.topic">>}]},
                           {resource,<<"datamartStage">>,exchange,
                           <<"e.fed.topic">>}}}
** Reason for termination ==
** {error,user_does_not_exist

Thanks,
Kale

-----Original Message-----
From: rabbitmq-discuss [mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Michael Klishin
Sent: Tuesday, March 25, 2014 3:55 AM
To: Discussions about RabbitMQ
Subject: Re: [rabbitmq-discuss] Federation/Connection issues

 On 25 March 2014 at 12:46:20, Ganann, Kale (kganann at kroll.com) wrote:
> > I’ve attached the output of rabbitmqctl report from one of our
> nodes while the processes were climbing. We’ve currently disabled 
> federation in prod, but we’re looking for a better solution.
> Ideas?

Can you please look at log files to see if there are any error messages, stack traces, etc. There likely will be something.
--
MK  

Software Engineer, Pivotal/RabbitMQ
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
This communication contains information that is confidential,
proprietary in nature, and may also be attorney-client privileged
and/or work product privileged. It is for the exclusive use of the
intended recipient(s). If you are not the intended recipient(s) or
the person responsible for delivering it to the intended
recipient(s), please note that any form of dissemination,
distribution or copying of this communication is strictly
prohibited and may be unlawful. If you have received this
communication in error, please immediately notify the sender by replying
to this message and delete this email immediately. Thank you for your cooperation. 

Please be advised that neither Altegrity, its affiliates, its employees
or agents accept liability for any errors, omissions or damages
caused by delays of receipt or by any virus infection in this
message or its attachments, or which may otherwise arise as a
result of this e-mail transmission.