at_client_sdk
at_client_sdk copied to clipboard
atsign-foundation
not receiving notifications
I was using @adorabledinosaur and @houseofwaxrural atsigns.
on sending file from @adorabledinosaur to @houseofwaxrural:
- I receive notification with key as "file_shared_key" and not the actual file notification that was sent.
on sending second file to @houseofwaxrural:
- again "file_shared_key" key notification was received followed by the file notification.
Sometimes we get only "file_shared_key" and not the actual file notification.
when trying to send file from @houseofwaxrural to @adorabledinosaur I was not able receive any notification not even "file_shared_key" notification.
@sachins-geekyants this scenario was tested in which environment ?.please attach app/server logs.
on app side I could not capture any logs as I was not getting any notification on receiving end.
logs from prod on receiver end:
5e4834ea-dd0c-5a23-b441-7be000cef4fd_secondary.1.qyvdj909b22k@hornet-09 | INFO|2021-05-07 13:56:27.365792|OutboundClient|notificationRequest : notify:update:messageType:key:notifier:system:ttl:518400000:ttr:-1:ccd:true:@houseofwaxrural:filetransfer-1620395781768415.mospherepro@adorabledinosaur:0LfaEP6eoSrt5PIa1ci0Nm4Z73yvGC2rOESoMyLLbmJKZyf9EcVtBQWBpmDt9lTSrM8QxDyvemNLrRBV9NDkdR/PWps+QO4SMPFEmBQhRcV03L2S+u4Cv2VVjhu+e7Okjw70G6Ilx19A2w2pU9kTuW/KeKK2GeOLv1v/gOSKIplEwFzBtAOpW1vFF9HSDp/4ZUFy5kAHHwgWlqw8aXiMU5z2gljP7TYMBcVCikTf+dUMQnjK4aBa6stYzogwwd4hlYqzFmhtR9QSxY5s/HzG2PBp/eoj3jWPWoBf5GdMRl/vKEqPRYxH2u1iMpfP6Qiylgd8/d8Lpq3K0DEDRw6lkvlDKjFM2CDUKaBTsdrQlk96QH0z5lawa3fBOgc823awCw2kCW+EUPh6S1DTaDcLnY2bSEDh1buZdSVXXxGedbHqhM+D+Mt4IbnhxtTASVkxCDLqD0l3oA31Di38jZ6sb/sayiCXRw+QpcL1bkgUUyYMh9izwl04/D++rOA/UNE99/eiPuvojoWTeO040QQDeZHOPzxrxzvFaFOL/TeSi8Riy0VgoVcZXVA9Fa1XzKtLhHLMe1uRWw0nnoZ0fq9yW3IKzG60uFHNXugfHUc+StpurdbYTIzBNCKyQtOlymYx65K7wcEKxcbDD3lz92RWc7MN7X7+YxQxWoDHz4vs15tuUbBBz5GUW6zsoYlifiKptadC2ivHiaB6uHTFHm/pz6qwDNA5FMiaaZuupsdrE79qBA6a1k7Lgsj1vJzwnPjXooQWQAKTzYcknd1IpvDJrA==
5e4834ea-dd0c-5a23-b441-7be000cef4fd_secondary.1.qyvdj909b22k@hornet-09 |
5e4834ea-dd0c-5a23-b441-7be000cef4fd_secondary.1.qyvdj909b22k@hornet-09 |
5e4834ea-dd0c-5a23-b441-7be000cef4fd_secondary.1.qyvdj909b22k@hornet-09 | INFO|2021-05-07 13:56:27.365869|OutboundClient|waiting for response from outbound connection
5e4834ea-dd0c-5a23-b441-7be000cef4fd_secondary.1.qyvdj909b22k@hornet-09 |
5e4834ea-dd0c-5a23-b441-7be000cef4fd_secondary.1.qyvdj909b22k@hornet-09 | INFO|2021-05-07 13:56:27.518385|OutboundClient|notifyResult result after format: data:success
5e4834ea-dd0c-5a23-b441-7be000cef4fd_secondary.1.qyvdj909b22k@hornet-09 |
5e4834ea-dd0c-5a23-b441-7be000cef4fd_secondary.1.qyvdj909b22k@hornet-09 | INFO|2021-05-07 13:56:27.518469|NotificationResourceManager|notifyResult : data:success
5e4834ea-dd0c-5a23-b441-7be000cef4fd_secondary.1.qyvdj909b22k@hornet-09 |
5e4834ea-dd0c-5a23-b441-7be000cef4fd_secondary.1.qyvdj909b22k@hornet-09 | FINER|2021-05-07 13:56:32.315457|OutboundConnectionImpl|InternetAddress('34.121.142.209', IPv4):1892 Disconnected
5e4834ea-dd0c-5a23-b441-7be000cef4fd_secondary.1.qyvdj909b22k@hornet-09 |
5e4834ea-dd0c-5a23-b441-7be000cef4fd_secondary.1.qyvdj909b22k@hornet-09 | SEVERE|2021-05-07 13:57:53.188348|InboundListener|SocketException: OS Error: Connection reset by peer, errno = 104, address = 0.0.0.0, port = 1936
5e4834ea-dd0c-5a23-b441-7be000cef4fd_secondary.1.qyvdj909b22k@hornet-09 |
5e4834ea-dd0c-5a23-b441-7be000cef4fd_secondary.1.qyvdj909b22k@hornet-09 | Unhandled exception:
5e4834ea-dd0c-5a23-b441-7be000cef4fd_secondary.1.qyvdj909b22k@hornet-09 | SocketException: OS Error: Connection reset by peer, errno = 104, address = 0.0.0.0, port = 1936