SequelizeConnectionError in Node.js application - javascript
I have strange problem and don't know in what place is the problem. I will be grateful for any help.
I have Node.js application which works fine in local windows 10 computer. I run this application successfully in Docker which is in CentOS server. This application works with remote MySQL and PostgreSQL databases. It worked correctly several days but yestoday I notice that I have error. Application can't connect to remote MySQL database anymore. In the same time I can connect to that remote MySQL database without any problem if I run application in my local computer or connect by DBeaver/dbForge tool.
MySQL.js:
const Sequelize = require('sequelize');
const sequelize = new Sequelize('database_name', 'username', 'password', {
host: 'host',
dialect: 'mysql'
});
sequelize.authenticate().then(() => {
console.log('Connection to database has been established successfully.');
}).catch(err => {
console.error('Unable to connect to database:', err);
});
module.exports = sequelize;
routes.js:
const express = require('express');
const router = express.Router();
const sequelize = require('../configurations/MySQL');
const Sequelize = require('sequelize');
const passport = require('passport');
require('../configurations/password')(passport);
router.post('/search_by_name', passport.authenticate('jwt', {session: false}, null), function(req, res) {
const token = getToken(req.headers);
if (token) {
sequelize.query("LONG SQL QUERY", {
replacements: {
name: req.body.name,
},
type: Sequelize.QueryTypes.SELECT
}).then((locations) => {
res.status(200).send(locations)
}).catch((error) => {
res.status(400).send(error);
});
} else {
return res.status(401).send({
status: false,
description: "Unauthorized"
});
}
});
As you can see I use sequelize library to connect application to remote MySQL database. The same library I use to connect to remote PostgreSQL database. As I said before error happens only when I try to connect to remote MySQL database in Docker. There is no error with PostgreSQL connection in Docker. Is it possible that problem inside Docker/network?
Dependencies:
"sequelize": "^4.42.0"
"mysql2": "^1.6.4"
I also thought that the reason of the problem can be because of much pools/connections and sequelize library don't close them automatically. For thats why I restarted docker сontainer several times hoping to confirm the theory. Unfortunately the error do not disappear.
How do you think, what happens?
Error:
Unable to connect to the database: { SequelizeConnectionError: connect ETIMEDOUT
at Utils.Promise.tap.then.catch.err (/node_modules/sequelize/lib/dialects/mysql/connection-manager.js:149:19)
at tryCatcher (/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromise0 (/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/node_modules/bluebird/js/release/promise.js:690:18)
at _drainQueueStep (/node_modules/bluebird/js/release/async.js:138:12)
at _drainQueue (/node_modules/bluebird/js/release/async.js:131:9)
at Async._drainQueues (/node_modules/bluebird/js/release/async.js:147:5)
at Immediate.Async.drainQueues [as _onImmediate] (/node_modules/bluebird/js/release/async.js:17:14)
at processImmediate (timers.js:632:19)
name: 'SequelizeConnectionError',
parent:
{ Error: connect ETIMEDOUT
at Connection._handleTimeoutError (/node_modules/mysql2/lib/connection.js:173:17)
at listOnTimeout (timers.js:324:15)
at processTimers (timers.js:268:5)
errorno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect',
fatal: true },
original:
{ Error: connect ETIMEDOUT
at Connection._handleTimeoutError (/node_modules/mysql2/lib/connection.js:173:17)
at listOnTimeout (timers.js:324:15)
at processTimers (timers.js:268:5)
errorno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect',
fatal: true }}
Try to add pool option when new Sequelize. Reference document
Sequelize will setup a connection pool on initialization so you should
ideally only ever create one instance per database if you're
connecting to the DB from a single process. If you're connecting to
the DB from multiple processes, you'll have to create one instance per
process, but each instance should have a maximum connection pool size
of "max connection pool size divided by number of instances". So, if
you wanted a max connection pool size of 90 and you had 3 worker
processes, each process's instance should have a max connection pool
size of 30.
const Sequelize = require('sequelize');
const sequelize = new Sequelize('database_name', 'username', 'password', {
host: 'host',
dialect: 'mysql',
pool: {
max: 15,
min: 5,
idle: 20000,
evict: 15000,
acquire: 30000
},
});
module.exports = sequelize;
Also, you can check more option at here
options.pool sequelize connection pool configuration
options.pool.max default: 5 Maximum number of connection in pool
options.pool.min default: 0 Minimum number of connection in pool
options.pool.idle default: 10000 The maximum time, in milliseconds,
that a connection can be idle before being released. Use with
combination of evict for proper working, for more details read
https://github.com/coopernurse/node-pool/issues/178#issuecomment-327110870
options.pool.acquire default: 10000 The maximum time, in milliseconds,
that pool will try to get connection before throwing error
options.pool.evict default: 10000 The time interval, in milliseconds,
for evicting stale connections. Set it to 0 to disable this feature.
options.pool.handleDisconnects default: true Controls if pool should
handle connection disconnect automatically without throwing errors
options.pool.validate A function that validates a connection. Called
with client. The default function checks that client is an object, and
that its state is not disconnected
In the simple terms i want to say that these type of error comes when your some configuration wrong entered. these are :
DB Name
Username
Password
so please cross verify your these things in your congif.json file
I would recommend to check the Database Hostname. Please try to resolve the hostname, if it is given IP address instead of domain. This would resolve the issue.
Related
Using ssl with node mysql and Cleardb
I have a free ClearDB account that I got through Heroku (as a resource) It gives me the CA certificate Client cert Client Key These are all in .pem format const fs = require('fs'); const ssl = { ca: fs.readFileSync('cleardb-ca.pem', "utf-8"), key: fs.readFileSync('cleardb-key.pem', "utf-8"), cert: fs.readFileSync('cleardb-cert.pem', "utf-8") }; const cleardb = mysql.createConnection({ host:"HOST", user: "USER", password: "PWD", database: "DB", ssl: ssl }); cleardb.connect((err) => { if (err) throw err; console.log('connected!'); }); This keeps throwing Error: 22928:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol:c:\ws\deps\openssl\openssl\ssl\statem\statem_lib.c:1929: and then the error stacktrace shows an Object like library: 'SSL routines', function: 'ssl_choose_client_version', reason: 'unsupported protocol', code: 'HANDSHAKE_SSL_ERROR', fatal: true The SSL routines:ssl_choose_client_version:unsupported error is the same exact error I get when I try connecting to this DB through the MySQL CLI. I.e. mysql --host=HOST --ssl-capath=. --ssl-cert=cleardb-cert.pem --ssl-key=cleardb-key.pem --user=USER I'm able to connect through both Node and the CLI if I do not use SSL. Any idea what's going on here? Should I really worry that much about using SSL? I've read that if the option for transport security exists, that you should elect to use it.
Connection cannot be established to FTP server using nodejs
I´m currently trying to connect to a FTP server using the nodeJS lib basic-ftp. It seems that a connection was established, but I cannot perform a single operation or even output a log statement after trying to access the server. The code then runs into an timeout.. I can ping the server from my local environment using Windows CMD ping command.. const ftp = require("basic-ftp") example() async function example() { const client = new ftp.Client(timeout = 30000) client.ftp.verbose = true try { await client.access({ host: "10.xxx.xx.xx", port: 2222, user: "xxx", pass: "xxxx", secure: true }) console.log("CONNECTED"); console.log(await client.ensureDir("/PATH/")); console.log(await client.list('/PATH/')); } catch (err) { console.log(err) } client.close() } Output: Connected to 10.xxx.xx.xxx:2222 (No encryption) < SSH-2.0-WS_FTP-SSH_8.5.0 Error: Timeout (control socket) at Socket.<anonymous> (C:\Users\xxx\dev\nodejs\ftpTest\node_modules\basic-ftp\dist\FtpContext.js:316:58) at Object.onceWrapper (events.js:299:28) at Socket.emit (events.js:210:5) at Socket._onTimeout (net.js:469:8) at listOnTimeout (internal/timers.js:531:17) at processTimers (internal/timers.js:475:7) There is almost no output that helps me to identify the issue. I can establish a connection using WinSCP. Does someone have an idea what could cause the problem and which steps are required to identify what could cause this issue? Thanks a lot! EDIT: Could it be that there is some kind of key exchange missing? I had to click yes when using WinSCP!
Error: read ECONNRESET when connected to a mysql server with Node.js
I'm trying to establish a simple connection to my database with the mysql npm package. At first glance, everything works fine and I can get the information I need, however, if I leave the server running for some time I get the following error: Error: read ECONNRESET at TCP.onStreamRead const express = require('express'); const app = express();` const mysql = require('mysql'); const db = mysql.createConnection({ host: 'XXXX.mysql.database.azure.com', user: 'XXXXX', password: 'XXXXX', database: 'XXXXX' }) db.connect((err)=>{ if(err){ console.log(err.message); } else { console.log('Connected to the database'); } }) As far as I understand the problem stems from the database connection being in idle mode. Do I need to configure the Azure server or is there something else I need to do?
Couple of things to try: You can try creating connection pool instead of **createConnection** mysql.createPool({}); Modify your package.json like below: "dependencies": { "mysql": "git://github.com/mysqljs/mysql#e3e123e9af7c0829a6c1417d911572a75b4a5f95" }, It is described in detail here: Bad handshake or ECONNRESET Azure Mysql Nodejs https://social.msdn.microsoft.com/Forums/en-US/c8fedbcc-909d-41ce-8c72-0374f76fdf82/cannot-connect-from-nodejs?forum=AzureDatabaseforMySQL Hope it helps.
node.js - Can't connect to MYSQL database with Sequelize
I'm starting at Node.js and i'm trying to make a simple connection with Sequelize based on its documentation (http://docs.sequelizejs.com/manual/installation/getting-started.html#installation). Here my db.js file : const Sequelize = require('sequelize') const db = new Sequelize('chat','root','root',{ host: 'localhost', port: 3306, dialect: 'mysql' }); db .authenticate() .then(() => { console.log('Connection has been established successfully.'); }) .catch(err => { console.error('Unable to connect to the database:', err); }); When executing this code, I have no success nor error message, just a message indicating 'String base operators deprecated' but nothing important i think. I tried changing localhost to 127.0.0.1, remove port number and multiples thread but i'm stucked here...
Tested your code and all seemed to work fine, it connected successfully to the database instance I have running. You might want to ensure mysql2 package is installed. Also check that the database chat has been created in MySQL workbench, and ensure the password is correct.
Connecting to MySQL on Node.js not initialized
I can't connect to the MySQL-database. I've googled some solutions, but none seems to work, or perhaps I haven't understood them. This is the setup: let express = require("express"); let mysql = require("mysql"); let http = require("http"); let app = express(); http.createServer(app).listen(8000, function() { console.log("Listening on http://localhost:" + port) }); var connection = mysql.createConnection({ host: "127.0.0.1", user: "root", password: process.env.DB_PASSWORD, database: "users", port: 8000 }); connection.connect(); connection.query("SELECT * FROM user", function(err, rows, fields) { if (err) { console.error("error connecting: " + err.stack); return; } console.log(rows[0]); }); connection.end(); Tried to setup the connection with "socketPath" and with another port, but they both returned error: Error: connect ECONNREFUSED 127.0.0.1:3306 at Object.exports._errnoException (util.js:1034:11) at exports._exceptionWithHostPort (util.js:1057:20) at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1099:14) -------------------- at Protocol._enqueue (/vagrant/node_modules/mysql/lib/protocol/Protocol.js:141:48) at Protocol.handshake (/vagrant/node_modules/mysql/lib/protocol/Protocol.js:52:41) at Connection.connect (/vagrant/node_modules/mysql/lib/Connection.js:130:18) at Object.<anonymous> (/vagrant/app.js:12:12) at Module._compile (module.js:571:32) at Object.Module._extensions..js (module.js:580:10) at Module.load (module.js:488:32) at tryModuleLoad (module.js:447:12) at Function.Module._load (module.js:439:3) at Module.runMain (module.js:605:10) When the connection and listen listens on same port, it doesn't return any errors, but the connection doesn't seem to initialize. console.log(connection.connect()); // -> undefined I'm very new to using MySQL to node so I'm probably doing this all wrong, but can't figure out what the problem is
For MAC users using MAMP var con = mysql.createConnection({ host: "localhost", user: "root", password: "root", database: "databasename", socketPath: '/Applications/MAMP/tmp/mysql/mysql.sock' }); socketPath points to MAMP "mysql.sock" to permit the NodeJS/Mysql connection. NOTE: the above connection also solves "Error: connect ECONNREFUSED 127.0.0.1:3306". I hope this helps someone.
Change your connection.connect() to connection.connect(function(err) { if (err) { console.error('error connecting: ' + err.stack); return; } console.log('connected as id ' + connection.threadId); }); so you can see errors. EDIT: Check bind-address and port in mysql config file (/etc/mysql/my.cnf). If your mysql server is running on host environment and node is running in guest (any virtualization like docker), set mysql server to listen on your local ip (eth0 like 192.168.0.x) and use same address in node config
As it turns out, I was a bit stupid. I was running the application on a Vagrant-server(virtual server), and I was trying to connect to my local-server. As soon as I tried to connect to the vagrant-server, everything worked properly. I also didn't have mysql-server properly installed to my vagrant machine.
if you don't set the port or set it to mysql default port i.e 3306 it works fine. var connection = mysql.createConnection({ host: "127.0.0.1", user: "mysqluser", password: 'password', database: "yourdatabase" }); I don't know the exact cause(although i tried with different ports), why it's not running on different ports but here is a link that shows how to use different port number for connecting mysql. FYI: You are setting your app to run on 8000 and again the port mysql using in your app is 8000.You must change it to something else.
You have to set socketPath and before you run your script make sure your MAMP is running or not. var con = mysql.createConnection({ host: "localhost", user: "root", password: "root", socketPath: '/Applications/MAMP/tmp/mysql/mysql.sock' });
Remove your port key value(port: 8000) and socketPath if you added, from sql configuration, and try. var connection = mysql.createConnection({ host: "127.0.0.1", user: "root", password: "root", database: "users" }); Actually you occupied 8000 port by node server so you can't assign same port to different process. Second mysql is running on port 3306. so you could not connect mysql through different port. You can use different port for mysql but by some proxy pass mechanism or by running mysql itself on specific port.
Please follow simple steps to start (Worked on windows Machine): Download and install MySQL from following link click here. Configure downloaded file (I had kept default config parameters). Please check this video link for reference Make sure MySQL server status is on. Now you can check connection status by using below node code. const mysql = require('mysql'); const connection = mysql.createConnection({ host: 'localhost', user: 'root', password: 'password', port: 3306 }); connection.connect((err) => { if (err) throw err; console.log('Connected to MySQL Server'); })
Start Your Mysql Server from your Xampp Control panel