Magnus Jeffs Tovslid

I also have this problem in version 3.4.0. Has anyone looked into it?

I have some debug logs now, but it's hard to digest it all. It seems to start with a disconnect: 02:54:55.641 debug connection error: Error: read ECONNRESET 02:54:55.641 debug Error...

Ok, I'll try master :) If it doesn't work out I'll see if I can grab the debug logs.

Stuck again. Not sure if it's the same issue, but it seems to be stuck in a loop trying to connect: 15:03:21.340 debug connecting to: 15:03:21.345 debug Connecting to via...

It doesn't seem to be run. I can't see any empty frames after the issue started.

There are 20-30 days between each time this is happening, so it won't help adding a few random debug statements. There has to be something else going wrong here beside...

Hi again. I added a few more debug statements. What's weird is this: We negotiate a timeout of 120 000 ms: Connected with params { maxFrameSize= 65536 , channelMax= 4999...

@mbroadst forgot to mention you in the previous post

@mbroadst Finally got another error with debug statements on: !!self.connected -> true !!self._transport -> true (Date.now() - self._lastOutgoing) -> 30027 maxTimeBeforeHeartbeat -> 120000 Memory usage is normal.