Cannot connect from Sequalize.js, can connect from MySQL client
I've got two docker services, one running a simple node server and the other a mysql (mariadb actually) database server.
All instances of a socket file mentioned anywhere in /etc/mysql/ say
/var/run/mysqld/mysqld.sock
This will be important soon.
My node server is running some Sequelize code that is trying to connect to the MySQL server.
Whenever I try and connect via Sequelize, I get:
{"statusCode":500,"error":"Internal Server Error","message":"connect ENOENT /var/run/mysqld/mysqld.sock"}
However, if I log into the Node docker container I can successfully connect to MySQL on the other docker container using the mysql CLI client.
I think I understand that the mysql client is using a tcp connection, while Sequelize is using a socket connection. But, when Sequelize is throwing that error, it is showing the correct socket path, as far as I know. Here is my Sequelize config:
const options = {
host: "mysql",
dialect: "mysql",
dialectOptions: {
socketPath: "/var/run/mysqld/mysqld.sock"
}
};
let sequelize = new Sequelize("ibbr_dev", "devuser", "password", options);
mysql docker sequelize.js
asked Nov 24 '18 at 4:05
sethseth
528
add a comment |
I've got two docker services, one running a simple node server and the other a mysql (mariadb actually) database server.
All instances of a socket file mentioned anywhere in /etc/mysql/ say
/var/run/mysqld/mysqld.sock
This will be important soon.
My node server is running some Sequelize code that is trying to connect to the MySQL server.
Whenever I try and connect via Sequelize, I get:
{"statusCode":500,"error":"Internal Server Error","message":"connect ENOENT /var/run/mysqld/mysqld.sock"}
However, if I log into the Node docker container I can successfully connect to MySQL on the other docker container using the mysql CLI client.
I think I understand that the mysql client is using a tcp connection, while Sequelize is using a socket connection. But, when Sequelize is throwing that error, it is showing the correct socket path, as far as I know. Here is my Sequelize config:
const options = {
host: "mysql",
dialect: "mysql",
dialectOptions: {
socketPath: "/var/run/mysqld/mysqld.sock"
}
};
let sequelize = new Sequelize("ibbr_dev", "devuser", "password", options);
mysql docker sequelize.js
asked Nov 24 '18 at 4:05
sethseth
528
add a comment |
I've got two docker services, one running a simple node server and the other a mysql (mariadb actually) database server.
All instances of a socket file mentioned anywhere in /etc/mysql/ say
/var/run/mysqld/mysqld.sock
This will be important soon.
My node server is running some Sequelize code that is trying to connect to the MySQL server.
Whenever I try and connect via Sequelize, I get:
{"statusCode":500,"error":"Internal Server Error","message":"connect ENOENT /var/run/mysqld/mysqld.sock"}
However, if I log into the Node docker container I can successfully connect to MySQL on the other docker container using the mysql CLI client.
I think I understand that the mysql client is using a tcp connection, while Sequelize is using a socket connection. But, when Sequelize is throwing that error, it is showing the correct socket path, as far as I know. Here is my Sequelize config:
const options = {
host: "mysql",
dialect: "mysql",
dialectOptions: {
socketPath: "/var/run/mysqld/mysqld.sock"
}
};
let sequelize = new Sequelize("ibbr_dev", "devuser", "password", options);
mysql docker sequelize.js
asked Nov 24 '18 at 4:05
sethseth
528
I've got two docker services, one running a simple node server and the other a mysql (mariadb actually) database server.
All instances of a socket file mentioned anywhere in /etc/mysql/ say
/var/run/mysqld/mysqld.sock
This will be important soon.
My node server is running some Sequelize code that is trying to connect to the MySQL server.
Whenever I try and connect via Sequelize, I get:
{"statusCode":500,"error":"Internal Server Error","message":"connect ENOENT /var/run/mysqld/mysqld.sock"}
However, if I log into the Node docker container I can successfully connect to MySQL on the other docker container using the mysql CLI client.
I think I understand that the mysql client is using a tcp connection, while Sequelize is using a socket connection. But, when Sequelize is throwing that error, it is showing the correct socket path, as far as I know. Here is my Sequelize config:
const options = {
host: "mysql",
dialect: "mysql",
dialectOptions: {
socketPath: "/var/run/mysqld/mysqld.sock"
}
};
let sequelize = new Sequelize("ibbr_dev", "devuser", "password", options);
mysql docker sequelize.js
mysql docker sequelize.js
asked Nov 24 '18 at 4:05
sethseth
528
asked Nov 24 '18 at 4:05
sethseth
528
asked Nov 24 '18 at 4:05
sethseth
528
asked Nov 24 '18 at 4:05
sethseth
528
asked Nov 24 '18 at 4:05
sethseth
528
528
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The MySQL socket file is not available in your Node container, it is only available in the MySQL container as it is a file. Rather than setting up unix socket based connection, you should use a TCP connection (skipping the dialectOptions).
answered Nov 25 '18 at 19:16
Uku LoskitUku Loskit
30.3k86879
Yes! Thank you . I removed the dialectOptions and things are working again. I'll try and remember this next time I'm moving something from an environment that uses a socket connection to Docker.
– seth
Nov 28 '18 at 17:59
Just a note, unix socket connections are faster than TCP connections.
– indospace.io
Dec 20 '18 at 13:23
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53455056%2fcannot-connect-from-sequalize-js-can-connect-from-mysql-client%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The MySQL socket file is not available in your Node container, it is only available in the MySQL container as it is a file. Rather than setting up unix socket based connection, you should use a TCP connection (skipping the dialectOptions).
answered Nov 25 '18 at 19:16
Uku LoskitUku Loskit
30.3k86879
Yes! Thank you . I removed the dialectOptions and things are working again. I'll try and remember this next time I'm moving something from an environment that uses a socket connection to Docker.
– seth
Nov 28 '18 at 17:59
Just a note, unix socket connections are faster than TCP connections.
– indospace.io
Dec 20 '18 at 13:23
add a comment |
The MySQL socket file is not available in your Node container, it is only available in the MySQL container as it is a file. Rather than setting up unix socket based connection, you should use a TCP connection (skipping the dialectOptions).
answered Nov 25 '18 at 19:16
Uku LoskitUku Loskit
30.3k86879
Yes! Thank you . I removed the dialectOptions and things are working again. I'll try and remember this next time I'm moving something from an environment that uses a socket connection to Docker.
– seth
Nov 28 '18 at 17:59
Just a note, unix socket connections are faster than TCP connections.
– indospace.io
Dec 20 '18 at 13:23
add a comment |
The MySQL socket file is not available in your Node container, it is only available in the MySQL container as it is a file. Rather than setting up unix socket based connection, you should use a TCP connection (skipping the dialectOptions).
answered Nov 25 '18 at 19:16
Uku LoskitUku Loskit
30.3k86879
The MySQL socket file is not available in your Node container, it is only available in the MySQL container as it is a file. Rather than setting up unix socket based connection, you should use a TCP connection (skipping the dialectOptions).
answered Nov 25 '18 at 19:16
Uku LoskitUku Loskit
30.3k86879
answered Nov 25 '18 at 19:16
Uku LoskitUku Loskit
30.3k86879
answered Nov 25 '18 at 19:16
Uku LoskitUku Loskit
30.3k86879
answered Nov 25 '18 at 19:16
Uku LoskitUku Loskit
30.3k86879
30.3k86879
Yes! Thank you . I removed the dialectOptions and things are working again. I'll try and remember this next time I'm moving something from an environment that uses a socket connection to Docker.
– seth
Nov 28 '18 at 17:59
Just a note, unix socket connections are faster than TCP connections.
– indospace.io
Dec 20 '18 at 13:23
add a comment |
Yes! Thank you . I removed the dialectOptions and things are working again. I'll try and remember this next time I'm moving something from an environment that uses a socket connection to Docker.
– seth
Nov 28 '18 at 17:59
Just a note, unix socket connections are faster than TCP connections.
– indospace.io
Dec 20 '18 at 13:23
Yes! Thank you . I removed the dialectOptions and things are working again. I'll try and remember this next time I'm moving something from an environment that uses a socket connection to Docker.
– seth
Nov 28 '18 at 17:59
Yes! Thank you . I removed the dialectOptions and things are working again. I'll try and remember this next time I'm moving something from an environment that uses a socket connection to Docker.
– seth
Nov 28 '18 at 17:59
Just a note, unix socket connections are faster than TCP connections.
– indospace.io
Dec 20 '18 at 13:23
Just a note, unix socket connections are faster than TCP connections.
– indospace.io
Dec 20 '18 at 13:23
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53455056%2fcannot-connect-from-sequalize-js-can-connect-from-mysql-client%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
