Sequelize connection error

Question

I'm trying to transfer my application to a new machine. It works on the old machine perfectly, and I have been trying to copy the settings as closely as possible, but there is something missing. This is the error I'm getting:

Unhandled rejection SequelizeConnectionError: Handshake inactivity timeout
    at Handshake._callback (/Applications/MAMP/htdocs/dashboard-server/node_modules/sequelize/lib/dialects/mysql/connection-manager.js:63:20)
    at Handshake.Sequence.end (/Applications/MAMP/htdocs/dashboard-server/node_modules/mysql/lib/protocol/sequences/Sequence.js:96:24)
    at /Applications/MAMP/htdocs/dashboard-server/node_modules/mysql/lib/protocol/Protocol.js:393:18
    at Array.forEach (native)
    at /Applications/MAMP/htdocs/dashboard-server/node_modules/mysql/lib/protocol/Protocol.js:392:13
    at doNTCallback0 (node.js:417:9)
    at process._tickCallback (node.js:346:13)

Thoughts?

It seems to be a problem with the node-mysql package, did you try re-downloading the packages? — Jonathan Solorzano
– Jonathan Solorzano, Commented Oct 13, 2015 at 2:39
Why don't you try to increment the value of acquireTimeout of the connection? — Jonathan Solorzano
– Jonathan Solorzano, Commented Oct 13, 2015 at 2:40
Im still trying to find a definitive cause, but as a side-note node 4.2.0 was released under 12 hours ago, very possible that may be the culprit. — Aren
– Aren, Commented Oct 13, 2015 at 4:00
@JonathanS. - Thanks for that suggestion - I tried updating the associated packages, to no avail :( As for the acquireTimeout, I thought about doing that, but the only reason I haven't is because I'm not using pooling, and it's working as is on the other machine. @Aren - that's a good point, maybe I'll try rolling back to a previous version of NodeJS to see if it resolves the issue - I'll post my results soon. — Jonathan
– Jonathan, Commented Oct 13, 2015 at 11:13

Aren · Accepted Answer · 2015-10-13 19:45:10Z

9

Just confirmed the problem is either Sequelize / mysql in conjunction with Node 4.2.0 after manually re-installing 4.1.1 my problems went away.

Downgrade to Node 4.1.x or wait for a patch/fix/etc to solve your issues.

Additional Information

The bug has been reported here on the node-mysql repository issue tracker. Seems someone regressed something in Node 4.2.0 and it wasn't caught. Here's the pull request to fix it which was merged in and is in the candidate for 4.2.1.

Update Oct 13th, 2015

Node 4.2.1 was just released (Changelog) containing the aforementioned fix. Upgrading to 4.2.1 should also fix your problems.

edited Oct 13, 2015 at 19:45

answered Oct 13, 2015 at 4:29

Aren

56.1k9 gold badges71 silver badges101 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Jonathan Over a year ago

This was it! Thank you so much for your help - saved me a lot of headache! I downgraded to 4.1.1 and my application booted right up!

Aren Over a year ago

See This Pull Request It looks like they're rushing out 4.2.1 today or tomorrow because there's 2 regressions that are breaking things everywhere.

Aren Over a year ago

@Jonathan You can now safely update to the latest node version 4.2.1 if you wish.

Jonathan Over a year ago

Thank you - I'll check it out tomorrow!

Collectives™ on Stack Overflow

Sequelize connection error

1 Answer 1

Additional Information

Update Oct 13th, 2015

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Additional Information

Update Oct 13th, 2015

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related