Bitfinex Disconnections-Reconnections

[ciottied]

Bitfinex.NET connects and reconnects to Bitfinex at least once per day, sometime many times a day.
I get it because I log the events BitfinexSocketClient.ConnectionLost and BitfinexSocketClient.ConnectionRestored.

Sometimes Bitfinex.NET reconnects but the candle subscription (opened at startup with BitfinexSocketClient.SubscribeToCandleUpdates ) is not restored.

I thought about a timer to detect if data is still arriving and, if not, close-reopen connection from scratch.
Is there a better way to deal with the issue ?

P.S.: my machine is in a datacenter with 99.9 connectivity SLA, so connections/reconnections are probably originated from Bitfinex endpoint and inherent to their service.

[JKorf]

Hi, do you have/can you provide debug logging of when this happens? By design Bitfinex.NET should resubscribe the subscriptions that were running when the disconnect happened. If this doesn't happen (sometimes), then that's a bug.

[ciottied]

Hi Jan. I'm in a short Vacation. I'll send logs when I'll be back. Thanks edc Il giorno lun 11 giu 2018 alle ore 09:27 Jan Korf <notifications@github.com> ha scritto:

…

Hi, do you have/can you provide debug logging of when this happens? By design Bitfinex.NET should resubscribe the subscriptions that were running when the disconnect happened. If this doesn't happen (sometimes), then that's a bug. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEmb5pysGtw5sV8KHLWOmKyL0EIG4_KYks5t7hv1gaJpZM4UedNM> .

[ciottied]

Hi Jan.

In the Activity log You can see a connection/disconnection logged the day 14 at 19:14:25 - 19:14:28 .
In the candle events log You see that the last 60 min candle event received is at 19:00:00 and then no more events were received.

What I suspect is that connection/disconnection causes the loss of candle subscription.
The version I'm testing was compiled on 12/5/2018 with last available Bitfinex.NET library.
Bitfinex.dll properties says version 1.0.0.0

Best regards.

edc

20180614ActivityLog.txt
20180614CandleEvents.txt

[ciottied]

Right Now Another example:

I logged:

20/06/2018 16.40.38.025 
------+++------
Bitfinex Connection Lost
------+++------
20/06/2018 16.40.41.143 
------+++------
Bitfinex Connection Restored
------+++------
20/06/2018 16.41.14.850 
------+++------
Bitfinex Connection Lost
------+++------
20/06/2018 16.41.17.115 
------+++------
Bitfinex Connection Restored
------+++------

And Subscriptions (at least candle subscriptions than in my app fires all the events) are gone.
The 17:00:00 Candle was not logged.

[JKorf]

Hi, I've refactored some of the reconnection handling in the new version (v1.0.13), could you see if this fixes your problems?

[ciottied]

Hi.
I went mad several hours testing some changes that I made and nothing worked.
Then I reverted to 1.012 and everything began to work again.
Apparently 1.013 is broken and candle subscription does not return any data.

[JKorf]

Sorry to hear that, I'll look into it tomorow

[JKorf]

I assume you called the subscribe functions before the Start function in the socket client? I found a bug introduced in version 1.0.13 which caused the subscriptions only to work if called AFTER the start method. This is fixed in 1.0.14, please try that.

[ciottied]

Yes, exactly.
I literally copied your example that makes subscriptions before starting socket.

Thank You.

[JKorf]

Can you confirm that the subscriptions still work after reconnecting?

[ciottied]

Tested.
It works.

Thank You.

[ciottied]

Update:
My system reconnects if it doesn't receive candle updates for 300 secs and, after 3 weeks of 24/7 operation, I can confirm that is working like a charm.
Reconnecting works.

[JKorf]

Great. Do you still have 300s timeouts though? The websocket should reconnect after 15 seconds of not receiving any data, so I would expect that wouldn't be necessary. (server send a heartbeat message every x seconds, which is handled internally in the library)

[ciottied]

Oh Yes.
many connection/disconnections per day, 300 secs timeout and reconnection at least once per day.
See screenshot.