Connection problem

[Vegaz 3]

Hello I have a problem with the connection.
Mysql is starting without any problem.
The only errors I have in mysql is this:

230610 00:20:28 mysqld_safe Logging to '/var/db/mysql/xxx.my.domain.err'.
230610 00:20:29 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2023-06-10 00:20:29 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-06-10 00:20:29 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.51) starting as process 10283 ...
2023-06-10 00:20:29 10283 [Note] Plugin 'FEDERATED' is disabled.
2023-06-10 00:20:29 10283 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-06-10 00:20:29 10283 [Note] InnoDB: The InnoDB memory heap is disabled
2023-06-10 00:20:29 10283 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-06-10 00:20:29 10283 [Note] InnoDB: Memory barrier is not used
2023-06-10 00:20:29 10283 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-06-10 00:20:29 10283 [Note] InnoDB: Using CPU crc32 instructions
2023-06-10 00:20:29 10283 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-06-10 00:20:29 10283 [Note] InnoDB: Completed initialization of buffer pool
2023-06-10 00:20:29 10283 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2023-06-10 00:20:29 10283 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2023-06-10 00:20:29 10283 [Note] InnoDB: Retrying to lock the first data file
2023-06-10 00:20:30 10283 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2023-06-10 00:20:30 10283 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2023-06-10 00:20:31 10283 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2023-06-10 00:20:31 10283 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2023-06-10 00:20:32 10283 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2023-06-10 00:20:32 10283 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2023-06-10 00:20:33 10283 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2023-06-10 00:20:33 10283 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2023-06-10 00:20:34 10283 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2023-06-10 00:20:34 10283 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2023-06-10 00:20:35 10283 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2023-06-10 00:20:35 10283 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

I don't know how to fix it... could someone help me?

 

This topic didn't help me but mysql is already running, it doesn't crash but I still can't connect to Client

 

Edited June 9, 2023 by Vegaz

[TMP4 10564]

Did you install your database correctly? By using .sql or tar.gz/tgz via tar -xf. People get such error when they unzip on windows and upload files individually via winscp.

Anyway check that ibdata1 files's permission, owner and group.

Edited June 10, 2023 by Metin2 Dev International
Core X - External 2 Internal

[Vegaz 3]

1 minute ago, TMP4 said:

Did you install your database correctly? By using .sql or tar.gz/tgz via tar -xf. People get such error when they unzip on windows and upload files individually via winscp.

Anyway check that ibdata1 files's permission, owner and group.

I tried many ways i.e. first I transferred database.tar.gz and typed cd /var/db then tar zxvf database.tar.gz and it extracted and same problem then I tried to create a new database via navicat and import via sql but I got errors that the whole player.sql could not be transferred.

And finally I manually moved then using the command:

chown -R mysql /var/db/mysql && chgrp -R mysql /var/db/mysql && chmod -R 777 /var/db/mysql

(I used the command in all these ways).

[Vegaz 3]

@ TMP4

I did as you wrote to move the base using the tar -xf command and now I have such errors:

230610 16:27:40 mysqld_safe mysqld from pid file /var/db/mysql/vps38992.my.domain.pid ended
230610 16:28:28 mysqld_safe Logging to '/var/db/mysql/xxx.my.domain.err'.
230610 16:28:28 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2023-06-10 16:28:29 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-06-10 16:28:29 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.51) starting as process 862 ...
2023-06-10 16:28:29 862 [Note] Plugin 'FEDERATED' is disabled.
2023-06-10 16:28:29 862 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-06-10 16:28:29 862 [Note] InnoDB: The InnoDB memory heap is disabled
2023-06-10 16:28:29 862 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-06-10 16:28:29 862 [Note] InnoDB: Memory barrier is not used
2023-06-10 16:28:29 862 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-06-10 16:28:29 862 [Note] InnoDB: Using CPU crc32 instructions
2023-06-10 16:28:29 862 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-06-10 16:28:29 862 [Note] InnoDB: Completed initialization of buffer pool
2023-06-10 16:28:29 862 [Note] InnoDB: Highest supported file format is Barracuda.
2023-06-10 16:28:29 862 [Note] InnoDB: 128 rollback segment(s) are active.
2023-06-10 16:28:29 862 [Note] InnoDB: Waiting for purge to start
2023-06-10 16:28:29 862 [Note] InnoDB: 5.6.51 started; log sequence number 1601096
2023-06-10 16:28:29 862 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2023-06-10 16:28:29 862 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2023-06-10 16:28:29 862 [Note] Server hostname (bind-address): '*'; port: 3306
2023-06-10 16:28:29 862 [Note] IPv6 is available.
2023-06-10 16:28:29 862 [Note]   - '::' resolves to '::';
2023-06-10 16:28:29 862 [Note] Server socket created on IP: '::'.
2023-06-10 16:28:29 862 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
2023-06-10 16:28:29 862 [Note] Event Scheduler: Loaded 0 events
2023-06-10 16:28:29 862 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.6.51'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
  

I apologize in advance for another post but I don't have an edit option and I wanted to let you know.

Edited June 10, 2023 by Vegaz
edit err

[TMP4 10564]

1 hour ago, Vegaz said:

@ TMP4

I did as you wrote to move the base using the tar -xf command and now I have such errors:

230610 16:27:40 mysqld_safe mysqld from pid file /var/db/mysql/vps38992.my.domain.pid ended
230610 16:28:28 mysqld_safe Logging to '/var/db/mysql/xxx.my.domain.err'.
230610 16:28:28 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2023-06-10 16:28:29 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-06-10 16:28:29 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.51) starting as process 862 ...
2023-06-10 16:28:29 862 [Note] Plugin 'FEDERATED' is disabled.
2023-06-10 16:28:29 862 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-06-10 16:28:29 862 [Note] InnoDB: The InnoDB memory heap is disabled
2023-06-10 16:28:29 862 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-06-10 16:28:29 862 [Note] InnoDB: Memory barrier is not used
2023-06-10 16:28:29 862 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-06-10 16:28:29 862 [Note] InnoDB: Using CPU crc32 instructions
2023-06-10 16:28:29 862 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-06-10 16:28:29 862 [Note] InnoDB: Completed initialization of buffer pool
2023-06-10 16:28:29 862 [Note] InnoDB: Highest supported file format is Barracuda.
2023-06-10 16:28:29 862 [Note] InnoDB: 128 rollback segment(s) are active.
2023-06-10 16:28:29 862 [Note] InnoDB: Waiting for purge to start
2023-06-10 16:28:29 862 [Note] InnoDB: 5.6.51 started; log sequence number 1601096
2023-06-10 16:28:29 862 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2023-06-10 16:28:29 862 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2023-06-10 16:28:29 862 [Note] Server hostname (bind-address): '*'; port: 3306
2023-06-10 16:28:29 862 [Note] IPv6 is available.
2023-06-10 16:28:29 862 [Note]   - '::' resolves to '::';
2023-06-10 16:28:29 862 [Note] Server socket created on IP: '::'.
2023-06-10 16:28:29 862 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
2023-06-10 16:28:29 862 [Note] Event Scheduler: Loaded 0 events
2023-06-10 16:28:29 862 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.6.51'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
  

I apologize in advance for another post but I don't have an edit option and I wanted to let you know.

There's no error there. That's fine. What's your problem actually? Can't connect to the Metin2 server? If mysql woring and you can conenct via navicat/heidisql etc then check the metin2 server's db and game cores.