mysqlx | Staticly typed MySQL Connector for NodeJS | Runtime Evironment library

This error line Error: listen EADDRINUSE: address already in use :::3000 and the localhost:3000 response, suggest that the server.js is up and running at PORT:3000.

npm start is the same as running node server.js ( i don't see it at package.json at scripts but i guess it's there).

So... try one or the other. It's like trying to access the same port with 2 different scripts.

I hope i get it right.

Actually, why you declare in 2 places new Sequelize(...) instance. Also why your config has sqlite and not mysql2? Maybe i misunderstand

Can you check your database connection in config/database.php file.

There you might be seeing something like 'default' => env('DB_CONNECTION', 'mysql'), change this to

You can do it in two steps:

As far as I can tell, XAMPP is now based on MariaDB and not MySQL. The MySQL X DevAPI Connectors use the X Protocol (port 33060, by default, on a MySQL server instance) which isn't available on MariaDB.

MariaDB supports the classic MySQL protocol (port 3306), but you can't use X DevAPI clients over that protocol.

So either you find a way to use MySQL 8.x server or you will need a classic protocol connector.

Disclaimer: I'm the lead developer of the MySQL X DevAPI Connector for Node.js

You should try to restart MySQL service after performing each step to check if the error is solved. But first, take a full backup of MySQL data directory /var/lib/mysql/ before you make any changes to MySQL service.

1. Connect to your server via SSH as root user and restart MySQL manually. Sometimes restarting the MySQL server may fix this issue. You can use either of the following command to restart MySQL server.

/etc/init.d/mysql restart

or

service mysql restart

1. You need to check whether the MySQL service is already running. If MySQL service is already running, you will have to kill them and start again. Use the following command to check if there is a MySQL service running already.

ps -aux | grep -i mysql

If MySQL service is already running, you will get list of MySQL processes with PIDs. The PID is the process ID of the MySQL processes. You will have to kill those processes.

kill -9 PID

PID – Process ID of the MySQL process.

1. Check the ownership of MySQL data directory /var/lib/mysql/. Use the following command to check ownership of MySQL service

ll -aF /var/lib/mysql/

If it’s owner is root, you should change the ownership to MySQL or your user by using the following command.

chown -R mysql /var/lib/mysql/

1. Take a backup of mysql.sock file and remove it. To achieve this, use the following commands:

cp /var/lib/mysql.sock /var/lib/mysql.sock_bkp rm -rf /var/lib/mysql.sock

1. Remove MySQL configuration file /etc/my.cnf or just back it up for now and restart:

mv /etc/my.cnf /etc/my.cnf.bak

1. Remove the log file named ib_logfile in the MySQL data directory /var/lib/mysql/ or just back it up now and restart the MySQL service. Sometimes MySQL service fails to start when it faces difficulty in updating the log files. The log files will be created automatically once you restart the MySQL service. Use the following command to remove the log files and back it up.

Change the present working directory to MySQL data directory.

cd /var/lib/mysql

Backup and remove the log files by renaming them.

mv ib_logfile0 ib_logfile0.bak mv ib_logfile1 ib_logfile1.bak

Move the backups to a temporary location.

mv /var/lib/mysql/ib_logfile* /tmp/folder/

1. Find the log files with suffix “.err” in the MySQL data directory /var/lib/mysql/. These files contain the actual error message. You can use any editor or command like cat, less to read the error message from the log files.

cat /var/lib/mysql/yourservername.err

In many cases, MySQL will run soon after removing this error files.

rm -rf /var/lib/mysql/yourservername.err

OK. It was about the environment variables. Here is the latest working docker-compose.yaml:

You have two problems here.

First, you're invoking values twice instead of once, and both times you're doing it with the wrong [number of] arguments. You're supposed to provide values() once per row, each time providing a value for each field in that row (ref).

Second, a std::set is ordered, meaning that for different inputs than 1, 2, & 3 your values could be stored in a different order to what you intended.

I suggest a std::vector instead.

This is a bug and I encourage you to report it at https://bugs.mysql.com/ using the Connector for Node.js category.

The only workaround that comes to mind is re-creating the pool if the getSession() method returns a rejected Promise (with or without a specific error). For instance, something like: