Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

The solution of MySQL error reporting Error_code: 1045

2025-01-18 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)05/31 Report--

The main content of this article is to explain "MySQL error Error_code: 1045 solution", interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Next, let the editor take you to learn "MySQL error reporting Error_code: 1045 solution"!

After restoring the master-slave relationship between the two machines today, execute show slave status on slave, and the results show that

2017-04-21T13:46:15.133435Z 8806 [ERROR] Slave I retry-time O for channel': error connecting to master 'repl@192.168.2.40:3306'-retry-time: 60 retries: 1, Error_code: 1045

First check the error log file of slave, which is the same as the error above

Then use perror to view the error code obtained in the previous one:

[root@iZ2ze5ifr62amhrpcnpn9yZ mysql] # perror 1045

MySQL error code 1045 (ER_ACCESS_DENIED_ERROR): Access denied for user'%-.48s'@'%-.64s'(using password:% s)

There may be a problem with the replication account. First confirm whether the replication user account exists and whether the correct permissions are assigned on MASTER.

Mysql > show grants for repl@192.168.2.41

+-- +

| | Grants for repl@192.168.2.41 |

+-- +

| | GRANT REPLICATION SLAVE ON *. * TO 'repl'@'192.168.2.41' |

+-- +

1 row in set (0.00 sec)

Found that there is no problem, try to use this account from master to connect to slave, and sure enough did not connect

[root@iZ2ze5ifr62amhrpcnpn9yZ] # mysql-urepl-h 192.168.2.40-p-P3306

Enter password:

ERROR 1045 (28000): Access denied for user 'repl'@'192.168.2.40' (using password: YES)

The previous password may not be correct. Change a new password.

Mysql > update mysql.user set authentication_string=PASSWORD ('REPLEREPLASTIONESTRATION 41') where User='repl' and host='192.168.2.41'

Query OK, 1 row affected, 1 warning (0.00 sec)

Rows matched: 1 Changed: 1 Warnings: 1

Mysql > commit

Query OK, 0 rows affected (0.00 sec)

Mysql > flush privileges

Query OK, 0 rows affected (0.00 sec)

Try to rebuild the replication relationship with a new password and the problem is solved.

Mysql > stop slave

Query OK, 0 rows affected (0.01 sec)

Mysql > change master to

-> master_host='192.168.2.40'

-> master_port=3306

-> master_user='repl'

-> mastery passwordkeeper, REPLLATIONPROPERATION, recording 41'

-> master_log_file='bin.000043'

-> master_log_pos=799072709

Query OK, 0 rows affected, 2 warnings (0.05 sec)

Mysql > start slave

Query OK, 0 rows affected (0.01 sec)

Mysql > show slave status\ G

* * 1. Row *

Slave_IO_State: Waiting for master to send event

Master_Host: 192.168.2.40

Master_User: repl

Master_Port: 3306

Connect_Retry: 60

Master_Log_File: bin.000043

Read_Master_Log_Pos: 854716379

Relay_Log_File: relay.000002

Relay_Log_Pos: 1135224

Relay_Master_Log_File: bin.000043

Slave_IO_Running: Yes

Slave_SQL_Running: Yes

Replicate_Do_DB:

Replicate_Ignore_DB: cus_DEMO,cus_DEMO_0413,cus_DEMO_0414,cus_DEMO_0418

Replicate_Do_Table:

Replicate_Ignore_Table:

Replicate_Wild_Do_Table:

Replicate_Wild_Ignore_Table:

Last_Errno: 0

Last_Error:

Skip_Counter: 0

Exec_Master_Log_Pos: 800207619

Relay_Log_Space: 55644221

Until_Condition: None

Until_Log_File:

Until_Log_Pos: 0

Master_SSL_Allowed: No

Master_SSL_CA_File:

Master_SSL_CA_Path:

Master_SSL_Cert:

Master_SSL_Cipher:

Master_SSL_Key:

Seconds_Behind_Master: 18559

Master_SSL_Verify_Server_Cert: No

Last_IO_Errno: 0

Last_IO_Error:

Last_SQL_Errno: 0

Last_SQL_Error:

Replicate_Ignore_Server_Ids:

Master_Server_Id: 40

Master_UUID: 1b00b716-cf6a-11e6-b66e-00163e320583

Master_Info_File: mysql.slave_master_info

SQL_Delay: 0

SQL_Remaining_Delay: NULL

Slave_SQL_Running_State: System lock

Master_Retry_Count: 86400

Master_Bind:

Last_IO_Error_Timestamp:

Last_SQL_Error_Timestamp:

Master_SSL_Crl:

Master_SSL_Crlpath:

Retrieved_Gtid_Set: 1b00b716-cf6a-11e6-b66e-00163e320583:34573831-34680957

Executed_Gtid_Set: 1b00b716-cf6a-11e6-b66e-00163e320583:1-33612321 34573831-34620341

Auto_Position: 0

Replicate_Rewrite_DB:

Channel_Name:

Master_TLS_Version:

1 row in set (0.00 sec)

At this point, I believe you have a deeper understanding of the "MySQL error Error_code: 1045 solution". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report