This article brings you relevant knowledge about mysql, which mainly organizes issues related to common error handling during installation, including failure to start processing, error 1053, Winwods installation initialization error, MySQL8 Unable to log in after installation, etc. Let’s take a look at it. I hope it will be helpful to everyone.

Recommended learning: mysql video tutorial
1. Unable to start processing, error 1053
Windows cannot start Mysql service error 1053: The service did not respond to the startup or control request in time
1.1 End the process
Handling method:
1. Type in the command line Enter the tasklist to view the process
2. Kill the process according to the process name
taskkill /f /t /im process name


1.2 Change the location of the network service
Server2012

Other win7 and win10 operating systems
1), Computer->Management->Local User And Group->Group double-click, the effect is as follows:

(2), double-click Administrators, and click Add, then click Advanced
(3), put NETWORK SERVICE added to Administrators group

1.3 Delete service
sc delete mysql57303307

Remember here, just reinstall Mysql and re-execute the 2-step operation (delete the original Mysql files and reinstall them all)
Another pitfall is that if it still cannot be started, remember to enable this service Windows Installer
Windows Installer is a general software distribution method for installing software.
By default, the service is started manually and needs to be opened in service management.
Right-click Start - Run - Enter "services.msc" - Windows Installer - Start


2. Winwods installation initialization error

Beginning configuration step: Writing configuration fileSaving my.ini configuration file... Saved my.ini configuration file. Ended configuration step: Writing configuration fileBeginning configuration step: Updating Windows Firewall rules Adding a Windows Firewall rule for MySQL80 on port 3306. Attempting to add a Windows Firewall rule with command: netsh.exe advfirewall firewall add rule name="Port 3306" protocol=TCP localport=3306 dir=in action=allow 确定。 Successfully added the Windows Firewall rule. Adding a Windows Firewall rule for MySQL80 on port 33060. Attempting to add a Windows Firewall rule with command: netsh.exe advfirewall firewall add rule name="Port 33060" protocol=TCP localport=33060 dir=in action=allow 确定。 Successfully added the Windows Firewall rule. Ended configuration step: Updating Windows Firewall rules Beginning configuration step: Adjusting Windows serviceAttempting to grant Network Service require filesystem permissions. Granted permissions. Adding new serviceNew service added Ended configuration step: Adjusting Windows serviceBeginning configuration step: Initializing database (may take a long time)Attempting to run MySQL Server with --initialize-insecure option... Starting process for MySQL Server 8.0.24... Starting process with command: C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe --defaults-file="C:\ProgramData\MySQL\MySQL Server 8.0\my.ini" --console --initialize-insecure=on --lower-case-table-names=1... Process for mysqld, with ID 2572, was run successfully and exited with code -1073741515. Failed to start process for MySQL Server 8.0.24. Database initialization failed. Ended configuration step: Initializing database (may take a long time)

Install VC_redist.x86 and execute OK

Enter gpedit. msc, open policy management

It works normally after enabling certificate update
Because some system images were built earlier and system updates cannot be performed, system patch packages need to be installed to complete vc Installation
4. Centos environment rpm initialization MySQL error
The openssl version provided by Centos7 by default is 1.0.2. Some php extensions or other software depend on versions 1.1 or above. If you pass If it is low, an error will be reported
libssl.so.1.1: cannot open shared object file: No such file or directory
There are also errors consistent with the above when executing openssl version. This is because the location of the openssl library is incorrect or not installed. Problems with versions 1.1 and above
If you want to upgrade the openssl version, you need to compile it manually. The error solution is very simple, just install it correctly.
Let’s talk about the specific compilation and installation steps using Centos7 as an example
–openssl version confirmation
[root@jeames ~]# openssl version
OpenSSL 1.0.1e-fips 11 Feb 2013
–Compile openssl
tar - xvf openssl-1.1.1g.tar.gz
cd openssl-1.1.1g
./config shared --openssldir=/usr/local/openssl --prefix=/usr/local/openssl
make && make install

–Configuration
After the compilation is completed, use openssl version to check the current openssl version number.
You will find that it is still 1.0.2 , so some additional configuration work needs to be done here.
[root@jeames openssl-1.1.1g]# more /etc/ld.so.conf
include ld.so.conf.d/*.conf
[root@jeames openssl-1.1.1g ]# echo “/usr/local/lib64/” >> /etc/ld.so.conf
[root@jeames openssl-1.1.1g]# ldconfig
Use openssl version again to verify the version ,
If it doesn’t work, you can try the following methods,
Execute them in sequence (first back up the old version, then create a soft connection from the installation location of the new version)
mv /usr/bin/openssl /usr/bin/openssl .old
ln -s /usr/local/openssl/bin/openssl /usr/bin/openssl
ln -s /usr/local/openssl/include/openssl /usr/include/openssl
echo "/usr/local/openssl/lib" >> /etc/ld.so.conf
ldconfig -v
4. Unable to log in after MySQL8 is installed
The first method:
1. Use the command to edit the /etc/my.cnf configuration file, namely: vim /etc/my.cnf or vi /etc/my.cnf
2. In Add skip-grant-tables under [mysqld], then save and exit
3. Restart the mysql service: service mysqld restart
4. Change the root user name
After restarting, execute the mysql command to enter the mysql command line
5. Modify the root user password. Note here that sometimes it will report that modification is not allowed. Just flush privileges first and then execute it.
update mysql.user set authentication_string=password('root') where user='root' ; --5.7 version
flush privileges;
6. Comment out skip-grant-tables in /etc/my.cnf, and then restart mysql, that is: service mysqld restart
Okay, here's the thing You can log in with the new root password!

The second method:
Under the mysql8 system, the following method applies (full path)
G:\mysql-8.0 .23-winx64\bin\mysqld --datadir=G:\mysql-8.0.23-winx64\data80323308 --console --skip-grant-tables --shared-memory

Then open another window and execute the following command
cd G:\mysql-8.0.23-winx64\bin

mysql> select user,host,authentication_string from mysql.user;
mysql> delete from mysql.user where user='root' ;
mysql> flush privileges; --Remember to refresh, If the prompt cannot be created
mysql> create user root@'%' identified with mysql_native_password by 'root';
mysql> grant all on . to root@'%' with grant option;
mysql> flush privileges;
mysql> drop user 'root'@'localhost';
mysql> flush privileges;
mysql> create user root@'localhost' identified with mysql_native_password by 'root';
mysql> grant all on . to root@'localhost' with grant option;
mysql> flush privileges;
Recommended learning: mysql video Tutorial
The above is the detailed content of Handling common errors during MySQL installation (summary sharing). For more information, please follow other related articles on the PHP Chinese website!
Securing MySQL Default Installations and ConfigurationsJul 24, 2025 am 02:06 AMModifying the default root password, deleting anonymous users, banning remote root login, removing test databases, and restricting access ports are key steps in MySQL security hardening. First, use the ALTERUSER command to set a strong password and avoid using the root account to connect to the application; secondly, delete anonymous users'@'localhost' and ''@'your_hostname' through DROPUSER; then check and delete the 'root'@'%' account that allows remote login, or create a restricted dedicated account instead; then delete unnecessary test databases and other irrelevant data; finally restrict port 3306 access through firewall tools, or set bind-addres in the configuration file
Understanding MySQL Indexes for WHERE, ORDER BY, GROUP BYJul 24, 2025 am 02:05 AMMySQL indexes are not as fast as possible, and they need to be used reasonably according to the query scenario. 1. The WHERE condition medium value query (=) has the best effect. The range query must comply with the principle of leftmost prefix. Fuzzy match LIKE'abc%' can be indexed, LIKE'�c' is not available, and functions or expressions are avoided in the condition. 2. ORDERBY needs to use indexes to avoid file sorting. It requires that the sorting columns have indexes and the WHERE and ORDERBY columns are in the same order to form a joint index, but range query may cause the sorting to be invalid. 3. GROUPBY recommends using an existing index structure, which prioritizes indexes covering equivalent conditions. Discontinuous columns or inappropriate order will add additional overhead. In addition, the EXPLAIN tool should be paid attention to the implementation plan
Troubleshooting MySQL Replication Sync IssuesJul 24, 2025 am 02:03 AMCommon solutions to the MySQL master-slave synchronization problem are as follows: 1. Check whether the master-slave connection is normal, check the error information of the Last_IO_Error and Last_SQL_Error fields to ensure that the main library port is open and the slave library account has REPLICATIONSLAVE permission; 2. Check whether there are SQL execution errors, if the table does not exist or the field type does not match, skip the error and continue synchronization if necessary; 3. Fix data inconsistency, resynchronize full amount through mysqldump or PerconaXtraBackup, or use pt-table-checksum to detect and repair differences; 4. Optimize configuration and adjust sync_binlog and slave_parall
Choosing the Right MySQL Storage Engine: InnoDB vs MyISAM RevisitedJul 24, 2025 am 02:02 AMInnoDB is suitable for scenarios where transactions, foreign keys, and row-level locks are required. 2. MyISAM is suitable for scenarios where more reads, less writes, and 3. Modern MySQL recommends using InnoDB by default. InnoDB supports transaction processing, crash recovery, foreign key constraints and row-level locking, and is suitable for scenarios with high data consistency requirements such as financial transactions and order processing, with good concurrency performance and high reliability; MyISAM is simple in design and fast query speed, suitable for scenarios where reading operations are mainly based on log statistics and report analysis, but write operations will lock the entire table, affecting concurrency performance; Since MySQL5.5, InnoDB has become the default engine, and continues to obtain new functions and is more applicable. Unless there are special needs, it is recommended to choose InnoDB to avoid late migration costs.
Troubleshooting MySQL Replication User PrivilegesJul 24, 2025 am 01:58 AMMySQL master-slave replication issues are usually caused by improper configuration of replication user rights. 1. Make sure that the replica user has REPLICATIONSLAVE permissions, which can be checked through SHOWGRANTS and added with the GRANT command; 2. Avoid over-authorization and only grant necessary permissions such as REPLICATIONSLAVE and REPLICATIONCLIENT; 3. Check whether the permissions are effective, confirm that there are no spelling errors, FLUSHPRIVILEGES has been executed, the database modification is correct, and MySQL restart is restarted; 4. If the error "Accessdeniedforuser" is reported, the user name and password host should be confirmed, the user existence, firewall and port connectivity should be confirmed.
Optimizing MySQL for Social Media PlatformsJul 24, 2025 am 01:56 AMTooptimizeMySQLforsocialmediaplatforms,startwithindexingstrategies,schemadesign,queryoptimization,andconnectionhandling.1)Usecompositeandcoveringindexeswiselytospeedupquerieswithoutslowingdownwrites.2)Normalizecoredataforconsistencyanddenormalizesele
Optimizing MySQL for Gaming Leaderboards and Player StatsJul 24, 2025 am 01:44 AMTooptimizeMySQLforgamingleaderboardsandplayerstats,useproperdatatypesandindexing,optimizequerieswithwindowfunctions,implementcaching,andconsiderpartitioningorshardingatscale.First,useINTorBIGINTforscoresandDECIMALforfractionalvalues,andapplycompoundi
Securing MySQL Administrative Interfaces and ToolsJul 24, 2025 am 01:41 AMTo avoid exposing the management interface to the public network, it should be accessed through SSH tunnels or intranets; 2. Use a dedicated account and strictly control permissions, disable root remote login; 3. Enable SSL encryption transmission, set strong password policies and cookie authentication; 4. Regularly update the MySQL version and monitor log audit operations. If the MySQL management interface is not protected properly, it should restrict access methods, strengthen authentication, encrypt communications and continuously monitor security status.


Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Dreamweaver Mac version
Visual web development tools

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

Safe Exam Browser
Safe Exam Browser is a secure browser environment for taking online exams securely. This software turns any computer into a secure workstation. It controls access to any utility and prevents students from using unauthorized resources.

SecLists
SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.








