Hi!
Since AppServer 3.12 upgrade we noticed that we are missing some frames from these log windows. It’s hard to track in logs but here is an example:
Application Server logs:
time="2020-09-11T13:21:51Z" level=warning msg="[write] error writing websocket message: write tcp 10.24.7.47:8080->10.24.1.6:59930: i/o timeout"
time="2020-09-11T13:21:51Z" level=info msg="downlink tx acknowledged by gateway" dev_eui=b2f413070206321c
time="2020-09-11T13:21:51Z" level=info msg="finished streaming call with code OK" grpc.code=OK grpc.method=StreamFrameLogs grpc.service=api.DeviceService grpc.start_time="2020-09-11T13:18:05Z" grpc.time_ms=226547.45 peer.address="127.0.0.1:39238" span.kind=server system=grpc
time="2020-09-11T13:21:51Z" level=info msg="finished unary call with code OK" ctx_id=46d41e74-078b-4a24-b44f-9263aae89377 grpc.code=OK grpc.method=HandleTxAck grpc.service=as.ApplicationServerService grpc.start_time="2020-09-11T13:21:51Z" grpc.time_ms=3.631 peer.address="10.24.6.8:49892" span.kind=server system=grpc
time="2020-09-11T13:21:51Z" level=info msg="integration/logger: logging event" ctx_id=46d41e74-078b-4a24-b44f-9263aae89377 dev_eui=b2f413070206321c type=txack
time="2020-09-11T13:21:51Z" level=warning msg="[write] error writing websocket message: write tcp 10.24.7.47:8080->10.24.1.6:59924: i/o timeout"
Network Server logs:
time="2020-09-11T13:21:51Z" level=info msg="gateway/mqtt: publishing gateway command" command=down downlink_id=af6ea8c7-f3ae-4592-b158-a7539a539724 gateway_id=60c5a8fffe7615a2 qos=0 topic=gateway/60c5a8fffe7615a2/command/down
time="2020-09-11T13:21:51Z" level=info msg="device-session saved" ctx_id=af6ea8c7-f3ae-4592-b158-a7539a539724 dev_addr=c01dfa74 dev_eui=b2f413070206321c
time="2020-09-11T13:21:51Z" level=info msg="storage: downlink-frame saved" ctx_id=af6ea8c7-f3ae-4592-b158-a7539a539724 token=44910
time="2020-09-11T13:21:51Z" level=info msg="backend/gateway: downlink tx acknowledgement received" downlink_id=af6ea8c7-f3ae-4592-b158-a7539a539724 gateway_id=60c5a8fffe7615a2
time="2020-09-11T13:21:51Z" level=info msg="sent downlink meta-data to network-controller" ctx_id=af6ea8c7-f3ae-4592-b158-a7539a539724
time="2020-09-11T13:21:51Z" level=info msg="finished streaming call with code OK" grpc.code=OK grpc.method=StreamFrameLogsForDevice grpc.service=ns.NetworkServerService grpc.start_time="2020-09-11T13:18:05Z" grpc.time_ms=226543.92 peer.address="10.24.7.47:47710" span.kind=server system=grpc
time="2020-09-11T13:21:51Z" level=info msg="finished client unary call" ctx_id=af6ea8c7-f3ae-4592-b158-a7539a539724 grpc.code=OK grpc.ctx_id=46d41e74-078b-4a24-b44f-9263aae89377 grpc.duration=4.709814ms grpc.method=HandleTxAck grpc.service=as.ApplicationServerService span.kind=client system=grpc
time="2020-09-11T13:21:51Z" level=info msg="sent tx ack to application-server" ctx_id=af6ea8c7-f3ae-4592-b158-a7539a539724
Lorawan Frames window:
There are some error writing websocket messages. Our instances are behine a NGINX ingress controller. Does someone have the same scenario?
Thanks!