@sujith@vivek I'm getting this error after it runs for few minutes and web socket gets disconnected . Is there any issue today ? That can I do to resolve the issue ?
dropping connection to peer tcp4:35.154.10.12:443 with abort=True: None 2018-02-28 11:32:00+0530 [-] will retry in 2 seconds 2018-02-28 11:32:00+0530 [-] Stopping factory
@sujith@vivek I've just moved the code to google cloud and facing the issue there ... I've updated the kite connect using
Pip install kiteconnect --upgrade --pre
Below is there error that gets stored in log
2018-02-28 12:40: log: WARNING: closed connection on error: 1006 connection was closed uncleanly (None)
2018-02-28 12:40: log: WARNING: closed connection on close: 1006 connection was closed uncleanly (None)
@zartimus when there's any error , we can predefine some actions , right ? I'm thinking to restart the websocket in that function .. how can I do that ?
@nickmanan, You don't need to do anything, pykiteconnect has a reconnection logic written already and it is enabled by default. You can check out here.
will retry in 2 seconds
2018-02-28 11:32:00+0530 [-] Stopping factory
Pip install kiteconnect --upgrade --pre
Below is there error that gets stored in log
2018-02-28 12:40: log: WARNING: closed connection on error: 1006 connection was closed uncleanly (None)
2018-02-28 12:40: log: WARNING: closed connection on close: 1006 connection was closed uncleanly (None)
KiteTickerClientProtocol (TLSMemoryBIOProtocol),client] will retry in 2 seconds
2018-03-01 09:49:06+0530 [-] Stopping factory
2018-03-01 09:49:09+0530 [-] Starting factory
You don't need to do anything, pykiteconnect has a reconnection logic written already and it is enabled by default.
You can check out here.
You need to be connected then only you can subscribe to tokens.