TMySQL57 connection failed and log not found

5 posts / 0 new
Last post
F6GOX
TMySQL57 connection failed and log not found

Hello,

I could not open yet CQRLOG even after restart computer. "Server connect failed"
More, after saved yesterday the log on hamQTH, no log yet when tried "repaire data base" ?

Messages for mysqlerrors are below. Tnx for help.

2019-08-06T11:05:17.314080Z 0 [Warning] The syntax '--log_warnings/-W' is deprecated and will be removed in a future release. Please use '--log_error_verbosity' instead.
2019-08-06T11:05:17.314134Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-08-06T11:05:17.315070Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-0ubuntu0.18.04.1) starting as process 6574 ...
2019-08-06T11:05:17.317548Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-08-06T11:05:17.317566Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-08-06T11:05:17.317571Z 0 [Note] InnoDB: Uses event mutexes
2019-08-06T11:05:17.317575Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-08-06T11:05:17.317579Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-08-06T11:05:17.317584Z 0 [Note] InnoDB: Using Linux native AIO
2019-08-06T11:05:17.317763Z 0 [Note] InnoDB: Number of pools: 1
2019-08-06T11:05:17.317832Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-08-06T11:05:17.318803Z 0 [Note] InnoDB: Initializing buffer pool, total size = 80M, instances = 1, chunk size = 80M
2019-08-06T11:05:17.322443Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-08-06T11:05:17.323671Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-08-06T11:05:17.334997Z 0 [ERROR] InnoDB: Only one log file found.
2019-08-06T11:05:17.335025Z 0 [ERROR] InnoDB: Plugin initialization aborted with error not found
2019-08-06T11:05:17.935591Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2019-08-06T11:05:17.935619Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-08-06T11:05:17.935631Z 0 [ERROR] Failed to initialize builtin plugins.
2019-08-06T11:05:17.935638Z 0 [ERROR] Aborting

2019-08-06T11:05:17.935648Z 0 [Note] Binlog end
2019-08-06T11:05:17.935679Z 0 [Note] Shutting down plugin 'CSV'
2019-08-06T11:05:17.935994Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

F6GOX
I uninstall and reinstall

I uninstall and reinstall gain Cqrlog from last repository on.
always the same error essage when open the sofware.
Any idea ?
Tnx es 73 Laurent

Last 20 lines :
2019-08-30T11:13:06.436120Z 0 [Warning] The syntax '--log_warnings/-W' is deprecated and will be removed in a future release. Please use '--log_error_verbosity' instead.
2019-08-30T11:13:06.436175Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-08-30T11:13:06.437127Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-0ubuntu0.18.04.1) starting as process 12798 ...
2019-08-30T11:13:06.439639Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-08-30T11:13:06.439658Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-08-30T11:13:06.439663Z 0 [Note] InnoDB: Uses event mutexes
2019-08-30T11:13:06.439667Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-08-30T11:13:06.439672Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-08-30T11:13:06.439676Z 0 [Note] InnoDB: Using Linux native AIO
2019-08-30T11:13:06.439856Z 0 [Note] InnoDB: Number of pools: 1
2019-08-30T11:13:06.439925Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-08-30T11:13:06.440899Z 0 [Note] InnoDB: Initializing buffer pool, total size = 80M, instances = 1, chunk size = 80M
2019-08-30T11:13:06.444338Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-08-30T11:13:06.445353Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-08-30T11:13:06.456304Z 0 [ERROR] InnoDB: Only one log file found.
2019-08-30T11:13:06.456323Z 0 [ERROR] InnoDB: Plugin initialization aborted with error not found
2019-08-30T11:13:07.057115Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2019-08-30T11:13:07.057146Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-08-30T11:13:07.057159Z 0 [ERROR] Failed to initialize builtin plugins.
2019-08-30T11:13:07.057167Z 0 [ERROR] Aborting

2019-08-30T11:13:07.057177Z 0 [Note] Binlog end
2019-08-30T11:13:07.057212Z 0 [Note] Shutting down plugin 'CSV'
2019-08-30T11:13:07.057529Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

73 Laurent F6GOX

oh1kh
I uninstall and reinstall

Hi Laurent!

Check your ~/.config/cqrlog/database folder. One error line says: InnoDB: Only one log file found.

You should see there :
ib_logfile0
ib_logfile1

Perhaps you have only one file there and get error because of that. If you have only one file left then you can delete also it. (Best way is to rename it to some other name)

This idea is based to article: https://spin.atomicobject.com/2011/05/09/mysql-failed-registration-of-in...
chapter "Failed Registration of InnoDB as a Storage Engine"

I am not sure if it helps, but it is easy to try.

Reinstalling cqrlog does not touch folder ~/.config/cqrlog so if there is something wrong it would not be fixed by uninstall/reinstall procedure.

--
Saku
OH1KH

F6GOX
Hi Saku,

Hi Saku,

Exactly the good point !
only one file : ib_logfile0

Delete this file, close cqrlog and open it again, then can load file again without error.
Now data base is ok and there are two files 0 & 1

Many thanks

73 Laurent F6GOX

cabalowen (not verified)
TMySQL57 connection failed and log not found - Full Guide

mysql + homebrew
Basically you will have to perform some actions manually, however- your database data won't be deleted like in solution below

Go to my.cnf file and in section [mysqld] add line:

default-authentication-plugin=mysql_native_password

Login to mysql server from terminal: run mysql -u root -p, then inside shell execute this command (replacing [password] with your actual password):

ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY '[password]';

exit from mysql shell with exit and run brew services restart mysql.

Should work.

Quick fix (destructive method)
Quick fix for non-homebrew installs:

Apple Logo > System Preferences > MySQL > Initialize Database, then type your new password and select 'Use legacy password'

After restart you should be able to connect. Do it only on fresh installs, because you may lost your db tables otherwise.

my.cnf
The my.cnf file is located in /etc/my.cnf on Unix/Linux

Alternatives
For those who is still struggling with Sequel Pro problems: Sequel Pro was a great product, but with tons of unresolved issues and last release being dated to 2016 perhaps it's a good idea to look for some alternatives. There is a fork of SequelPro called SequelAce that seems to be pretty stable and up-to-date, it keeps similar functionality, similar look and feel, yet at the same time it is devoid of old Sequel Pro problems. Basically I have faced the same while working on ios app development agency (https://enterprise.affle.com/ios-app-development) .Before troubleshooting the error, we recommend taking a WordPress site backup. Many of the recommendations below involve manipulating information in your database, so you don’t want to make things worse. You should always backup before trying to fix things on your WordPress site, no matter how tech-savvy you think you are.

You can use a popular WordPress backup plugin such as VaultPress or WP Time Capsule to backup your files and database.

If you are a Kinsta user, you can take advantage of our one-click backup feature. Click into your WordPress site in MyKinsta, click on “Backups” and then on “Back up now.”
Hope this will help everyone.

Database Name
// ** MySQL settings ** //

/** The name of the database for WordPress */

define('DB_NAME', 'xxxxxx');
MySQL database username
/** MySQL database username */

define('DB_USER', 'xxxxxx');
MySQL database password
/** MySQL database password */

define('DB_PASSWORD', 'xxxxxxxxx');
MySQL hostname (server)
/** MySQL hostname */

define('DB_HOST', 'localhost');
To access your wp-config.php file, you can connect to your site via SFTP and browse to the root of your site. Or, if you are using cPanel, you can click on “File Manager,” browse to the root of your site, and right-click to edit the file.

You can also verify this is the correct database by ensuring it contains your WordPress site’s URL. To do this, click on the database and then click into the wp_options table (this might be slightly different for security purposes, such as wpxx_options). At the top of the table, you will see values for your site’s URL and name. If these match your current site, you can rest assured you are in the right place.