PROTOCOL_SEQUENCE_TIMEOUT

[StevePavlin]

Hi, I receive this error when my server runs overnight. I have the sql server running on a remote host if that helps.

[dougwilson]

Hi! Are you using the connection pooling or trying to maintain a single connect all night?

[StevePavlin]

Hi, I'm using a connection pool.

[jcq]

For the record, I just upgraded from Node 0.12 and am now getting this error on all of my connections. I've seen a few issues here (#1236, #1240, #1241, etc) that seem to describe the same issue that I'm having, but all seem to indicate that Node 4.2.1 should have fixed the problem. I'm running Node 4.2.2 on two servers and Node 5.0.0 on my local machine, and all are still getting PROTOCOL_SEQUENCE_TIMEOUT errors from code that worked perfectly under Node 0.12.

Is there another suggested solution for those of us already running latest Node?

[dougwilson]

Hi @jcq , the 4.2.1 issue is only specifically about the error "Handshake inactivity timeout"--all other errors have nothing to do with using the buggy Node.js 4.2.0 release. I would be happy to heal either of you two with this issue, but there is just not enough information here for me to be able to determine any kind of answer. Is there any additional information you can provide?

[jcq]

After further investigation, I determined that the issue I encountered was due to the combination of the newer versions of Node including the updated OpenSSL with protections against Logjam attacks (it now rejects handshakes w/ DH parameters shorter than 768 bits).

Unfortunately, the MySQL server to which my code was connecting is managed by others, so I had to roll back to Node 0.12.4 for now until they complete the upgrade to a compatible version of MySQL.

It just happened that the error that I encountered (PROTOCOL_SEQUENCE_TIMEOUT) after upgrading Node on the server in question was the same as those encountered by others after upgrading to Node 4.2.0, so I initially misunderstood the source of the error I encountered.

Anyhoo, feel free to disregard my part of this. :)

[steirico]

Thanks @jcq for your investigations. I can confirm that PROTOCOL_SEQUENCE_TIMEOUT is related to the used cipher.

I got work around by specifying the cipher explicitly. To do so have a look at #1185.

A cipher that works for me with node 4.2.3 is 'AES256-SHA'.

[dougwilson]

Yea, not sure why Node.js decided to just disable it or whatever.