Similar Content
-
Activity
-
1
-
1268
-
0
Connection problem
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 -
0
Sanii Switchbot problem
Hi, i got this problem when i enable the bonus saving page on Sanii Switchbot: Insert image from URL Any idea? Thank you in advance! -
4
-
1
-
1268
[40250] Reference Serverfile + Client + Src [15 Available Languages]
You are using vs2019 in the video, but it says vs22 in the rar, I have the same build problem. for client I can't get build even though I do windows.h vs2022 is installed -
5
-
1268
[40250] Reference Serverfile + Client + Src [15 Available Languages]
Okay I repaired the 0xc00007b just by uninstalling python-3.11 x64 (which is weird), but now while trying to launch the Metin2distribute.exe nothing happens, even errorlog.txt is not created.
-
-
Recently Browsing
- No registered users viewing this page.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now