[EnMasse] Disconnect from time to time

[Ulf Lilleengen]

Hi Bob,

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).

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:

kubectl set env statefulset/qdrouterd-$uuid PN_TRACE_FRM=1

Best regards,

Ulf

On Fri, Mar 22, 2019 at 10:55 AM Bob Claerhout <bob.claerhout at aloxy.io>
wrote:

> Hi all,
>
> 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:
>     `2019-03-21 10:30:20.777139 +0000 ROUTER_CORE (info) Link Route
> Deactivated 'ragent-gw-gw-out' on container gw-out`.
>
> 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?
> Can I enable debug logging somewhere? Is it logged somewhere why a link is
> deactivated?
>
> Kind regards,
> Bob
> --
>
> *Bob Claerhout*
> Software developer
> M +32 479 34 84 92
> The Beacon, Sint-Pietersvliet 7, 2000
> Antwerp
> bob.claerhout at aloxy.io | www.aloxy.io
> _______________________________________________
> enmasse mailing list
> enmasse at redhat.com
> https://www.redhat.com/mailman/listinfo/enmasse
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/enmasse/attachments/20190322/8b6375f7/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cmfaafbecndjnoom.png
Type: image/png
Size: 6330 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/enmasse/attachments/20190322/8b6375f7/attachment.png>