Failed connection attemps

[hoon-node]

Describe the bug
I subscribed to one of my own nodes that is up and running fine, with the Linux Beta.

Here is the subscribe transaction.

https://www.mintscan.io/sentinel/txs/BEB9FEBAE3D6EA924D52C3217966B9007FBF0DF327FEAACB54BFDE69FF5F1295

And here the node wallet

https://www.mintscan.io/sentinel/account/sent1thh9dcxk22kw4v6vh6kylk48pdx8lht3mnela7

Immediately after subscribing to it and every time I try to connect from now on, I get a "End request" and "Start request" transaction in my wallet and the connection does not get established.
For example

Here
Here
or
Here

The node logs show this (output after the last connection attempt right above):

2022-04-21T13:47:17Z INF Querying account address=sent1vyx7jy2n3efl59xagzj4ct96v33m9suec2f3sl 
2022-04-21T13:47:17Z INF Querying session id=53714 
2022-04-21T13:47:17Z INF Querying subscription id=12182 
2022-04-21T13:47:18Z INF Querying session id=53460 
2022-04-21T13:47:18Z INF Removing the peer from service key=Mt6GpaGX++mFLNJ2Q9ny3ifmJKdgcmuRg+P86lbdwFU= 
2022-04-21T13:47:18Z INF Querying quota address=sent1vyx7jy2n3efl59xagzj4ct96v33m9suec2f3sl id=12182

The value of the first "INF Querying session id=" output in the node logs increases with every connection attempt. All the other values stay the same.

The Linux app then shows "Selected node is temporary unavailable. Please try later or select another node".

Restarting the node does not fix the problem.

To Reproduce
The failed connection happens every time a connection attempt is made.
How to get in this position in the first place is unknown to me.

Expected behavior
It should connect.

Desktop (please complete the following information):

• Linux Beta App Version 1.1.1 under Ubuntu 21.04
• Node Version 0.3.1

[hoon-node]

Update 1

After 2-3 hours when I tried to connect again, I get asked to subscribe again even tho I still should have the initial subscription. When I make the new subscription (2GB worth of data) I get the same faulty connection attempts.

Update 2

Another 19 hours later, I tried to connect again. This time I can connect and use the node successfully with the second subscription of 2 GB data from Update 1.

Wallet transaction of successful connect

Node logs of successful connect:

2022-04-22T11:53:04Z INF Querying account address=sent1vyx7jy2n3efl59xagzj4ct96v33m9suec2f3sl
2022-04-22T11:53:04Z INF Querying session id=54176
2022-04-22T11:53:04Z INF Querying subscription id=12316
2022-04-22T11:53:05Z INF Querying quota address=sent1vyx7jy2n3efl59xagzj4ct96v33m9suec2f3sl id=12316
2022-04-22T11:53:05Z INF Added a new peer count=1 key=UfS7clQjFa7ghSi3M+2AiWhgSg4Eh/5t8nJ86w83yUo=
2022-04-22T11:53:26Z INF Validating the usage of connected peers count=1
2022-04-22T11:55:26Z INF Validating the usage of connected peers count=1
2022-04-22T11:57:26Z INF Validating the usage of connected peers count=1
2022-04-22T11:57:26Z INF Peer quota exceeded key=UfS7clQjFa7ghSi3M+2AiWhgSg4Eh/5t8nJ86w83yUo=
2022-04-22T11:57:26Z INF Removing the peer from service key=UfS7clQjFa7ghSi3M+2AiWhgSg4Eh/5t8nJ86w83yUo=

Update 3

Right after using up the 2 GB from Update 2 I tried to make a new subscription. I get the message "Selected node is temporary unavailable. Please try later or select another node" without getting asked to make a new subscription.

Wallet does this

The node says this:

2022-04-22T12:14:12Z INF Querying account address=sent1vyx7jy2n3efl59xagzj4ct96v33m9suec2f3sl
2022-04-22T12:14:12Z INF Querying session id=54194

[hoon-node]

I compared the output of two nodes with each other. One I could connect to right after I disconnected from it and another one that didn't establish the connection

I Call them S for successful connection and F for failed

Both nodes were connected. When I disconnected node S it did not have any additional logs that would make it obvious that I interacted with it to disconnect.

Here are the logs for S:

2022-05-26T17:52:38Z INF Validating the usage of connected peers count=1
2022-05-26T17:54:38Z INF Validating the usage of connected peers count=1
2022-05-26T17:56:38Z INF Validating the usage of connected peers count=1	<----------- Time of disconnect
2022-05-26T17:58:38Z INF Validating the usage of connected peers count=1
2022-05-26T17:59:42Z INF Querying account address=sent1wsrr3gzl8e488uaem4766vncn3ydw27rj6d8f6   <----Time of reconnection attempt
2022-05-26T17:59:42Z INF Querying session id=80672
2022-05-26T17:59:43Z INF Querying subscription id=40407
2022-05-26T17:59:43Z INF Querying session id=80633
2022-05-26T17:59:43Z INF Removing the peer from service key=+GebpXkRxpUg1GX88+3sI/v9sq24ceVXcZ8pXYcLFm4=
2022-05-26T17:59:43Z INF Querying quota address=sent1wsrr3gzl8e488uaem4766vncn3ydw27rj6d8f6 id=40407
2022-05-26T17:59:43Z INF Added a new peer count=1 key=kgtZ8XpquMuxrXQMS581dUebsTle7yYpfE04mLkuxj8=
2022-05-26T18:00:38Z INF Validating the usage of connected peers count=1
2022-05-26T18:02:38Z INF Validating the usage of connected peers count=1
2022-05-26T18:04:38Z INF Validating the usage of connected peers count=1
2022-05-26T18:06:38Z INF Validating the usage of connected peers count=1

Node F's logs were these

2022-05-26T17:52:53Z INF Validating the usage of connected peers count=1
2022-05-26T17:54:53Z INF Validating the usage of connected peers count=1
2022-05-26T17:56:42Z INF Querying account address=sent1cnd3qhdtf2985mst2vhh07yjzer6608z9d3qvh	<---- Time of disconnect
2022-05-26T17:56:43Z INF Querying session id=80671
2022-05-26T17:56:43Z INF Querying subscription id=43679
2022-05-26T17:56:43Z INF Querying session id=80634
2022-05-26T17:56:43Z INF Removing the peer from service key=a+gVWYzJ/uLLFgky2eXDDx8YuY1CzZ0X/17ekgdmI3c=
2022-05-26T17:56:43Z INF Querying quota address=sent1cnd3qhdtf2985mst2vhh07yjzer6608z9d3qvh id=43679
2022-05-26T17:56:43Z INF Added a new peer count=1 key=d3LV2GYEkd6LaAxSinILQdn7Q37+UkSJLeJQVMgb5kI=
2022-05-26T17:56:53Z INF Validating the usage of connected peers count=1
2022-05-26T17:58:53Z INF Validating the usage of connected peers count=1
2022-05-26T18:00:19Z INF Querying account address=sent1cnd3qhdtf2985mst2vhh07yjzer6608z9d3qvh	<---- Time of reconnection attempt
2022-05-26T18:00:19Z INF Querying session id=80673
2022-05-26T18:00:53Z INF Validating the usage of connected peers count=1
2022-05-26T18:02:53Z INF Validating the usage of connected peers count=1
2022-05-26T18:04:53Z INF Validating the usage of connected peers count=1
2022-05-26T18:06:53Z INF Validating the usage of connected peers count=1

Any furth attempt to connect to node F gives:

2022-05-26T18:09:40Z INF Querying account address=sent1cnd3qhdtf2985mst2vhh07yjzer6608z9d3qvh
2022-05-26T18:09:40Z INF Querying session id=80680

Without the connection getting established.

So for me it seems like nodes don't behave in a consistent manner.