<div dir="ltr"><div>Hi Bob,</div><div><br></div><div>Do you happen to have the logs of the qdrouterd and admin pods as well? This seems to indicate one of the ends of router and broker is closing the TCP connection. <br></div><div><br></div><div>Best regards,</div><div><br></div><div>Ulf<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 27, 2019 at 9:26 AM Bob Claerhout <<a href="mailto:bob.claerhout@aloxy.io">bob.claerhout@aloxy.io</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div bgcolor="#FFFFFF"> Hi all,<br> <br> Hereby the logging of the broker of this event.<br> <blockquote>2019-03-21T10:30:20.778Z INFO [ProtonClientConnectionManager] Connection messaging-aloxy/<a href="http://172.30.9.50:56671" target="_blank">172.30.9.50:56671</a> destroyed<br> 2019-03-21T10:30:20.778Z WARN [server] AMQ222061: Client connection failed, clearing up resources for session a4ebe8f7-4676-11e9-bac7-0a580a800051<br> 2019-03-21T10:30:20.988Z WARN [server] AMQ222107: Cleared up resources for session a4ebe8f7-4676-11e9-bac7-0a580a800051<br> 2019-03-21T10:30:20.988Z INFO [amqp] connectionDestroyed for connector address-connector-out<br> 2019-03-21T10:30:25.988Z INFO [amqp] Starting connector address-connector-out<br> 2019-03-21T10:30:25.999Z INFO [amqp] connectionCreated for connector address-connector-out<br> 2019-03-21T10:30:25.999Z INFO [ProtonClientConnectionManager] Connection messaging-aloxy/<a href="http://172.30.9.50:56671" target="_blank">172.30.9.50:56671</a> created<br> <br> </blockquote> The broker has not restarted.<br> <br> Kind regards,<br> Bob<br> <div class="gmail-m_-1624943294603341033moz-signature"> <div class="gmail-m_-1624943294603341033moz-signature"> <table> <tbody> <tr> <td><br> </td> <td><br> </td> </tr> </tbody> </table> <br> </div> </div> <div class="gmail-m_-1624943294603341033moz-cite-prefix">On 3/22/19 6:02 PM, Ulf Lilleengen wrote:<br> </div> <blockquote type="cite"> <div> <div dir="auto">Hi Bob,</div> </div> <div dir="auto"><br> </div> <div dir="auto">Regarding Gordon and Teds reply, do you have the logs from the broker? Alternatively could you also check if it got restarted for some reason?<br> </div> <div dir="auto"><br> </div> <div dir="auto">Best regards,</div> <div dir="auto"><br> </div> <div dir="auto">Ulf </div> <div><br> <div class="gmail_quote"> <div dir="ltr" class="gmail_attr">fre. 22. mar. 2019 kl. 12:19 skrev Bob Claerhout <<a href="mailto:bob.claerhout@aloxy.io" target="_blank">bob.claerhout@aloxy.io</a>>:<br> </div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div bgcolor="#FFFFFF">Hi Ulf,<br> <br> Thanks for the quick response. <br> I've enabled this tracing. I'll come back to this when it occurs again.<br> <br> Enjoy the weekend<br> Kind regards,<br> Bob</div> <div bgcolor="#FFFFFF"><br> <br> On 3/22/19 11:10 AM, Ulf Lilleengen wrote:<br> <blockquote type="cite"> <div dir="ltr"> <div>Hi Bob,</div> <div><br> </div> <div>If your client is based on qpid-proton, turning on frame tracing might give some more info on why it is disconnected. You can do that by setting the environment PN_TRACE_FRM=1 for your client (I think this works with most qpid clients). <br> </div> <div><br> </div> <div>Another alternative is to manually edit the qdrouterd statefulset on your cluster and add this env variable to the router to get more info in the router logs:</div> <div><br> </div> <div>kubectl set env statefulset/qdrouterd-$uuid PN_TRACE_FRM=1</div> <div><br> </div> <div>Best regards,</div> <div><br> </div> <div>Ulf<br> </div> </div> <br> <div class="gmail_quote"> <div dir="ltr" class="gmail_attr">On Fri, Mar 22, 2019 at 10:55 AM Bob Claerhout <<a href="mailto:bob.claerhout@aloxy.io" target="_blank">bob.claerhout@aloxy.io</a>> wrote:<br> </div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div bgcolor="#FFFFFF">Hi all,<br> <br> >From time to time we experience a disconnect from enmasse. I'm trying to figure out what's actually happening. In the logs I'm getting following line: <br> `2019-03-21 10:30:20.777139 +0000 ROUTER_CORE (info) Link Route Deactivated 'ragent-gw-gw-out' on container gw-out`. <br> <br> The address I'm using is called "gw". Can you point me towards somehwere I can find more information about why this link route is deactivated?<br> Can I enable debug logging somewhere? Is it logged somewhere why a link is deactivated?<br> <br> Kind regards,<br> Bob<br> <div class="gmail-m_-1624943294603341033m_6506290693180175315gmail-m_-3441750848713014256moz-signature">-- <br> <br> <div class="gmail-m_-1624943294603341033m_6506290693180175315gmail-m_-3441750848713014256moz-signature"> <table> <tbody> <tr> <td><img src="cid:169be555084f8fc50181" alt="" style="width: 134px; max-width: 100%;"></td> <td><b>Bob Claerhout</b><br> Software developer<br> M +32 479 34 84 92<br> The Beacon, <a href="https://maps.google.com/?q=Sint-Pietersvliet+7&entry=gmail&source=g" target="_blank"> Sint-Pietersvliet 7</a>, 2000<br> Antwerp<br> <a href="mailto:bob.claerhout@aloxy.io" target="_blank">bob.claerhout@aloxy.io</a> | <a href="http://www.aloxy.io" target="_blank">www.aloxy.io</a></td> </tr> </tbody> </table> </div> </div> </div> _______________________________________________<br> enmasse mailing list<br> <a href="mailto:enmasse@redhat.com" target="_blank">enmasse@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/enmasse" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/enmasse</a><br> </blockquote> </div> </blockquote> <br> </div> </blockquote> </div> </div> </blockquote> <br> </div> </blockquote></div>