Problem: Once we try to migrate the rds node into the aurora using the snapshot or using the inbuilt option from “RDS –> Actions –> Create Aurora Read Replica“, we may face the below error/issue due to which the rds to aurora migration failed. Failed to migrate from mysql 5.7.12 to aurora-mysql 5.7.12. Reason: Unable to migrate database to Aurora. Some of the tables in this snapshot are corrupted. Please try migrating a different snapshot or dump and load to a new database and try to migrate. Solution Once you will see over the error message then we might think about the snapshot is c ..read more

Problem Error on slave node replication : Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires. Replicate the missing transactions from elsewhere, or provision a new slave from backup. Consider increasing the master's binary log expiration period. The GTID set sent by the slave is '00019832-1111-1111-1111-111111111111:1, 00019832-1111-1111-2222-111111111111:1', and the missing transactions are '00019832-1111-111 ..read more

Here we are going to share a SQL query to find the table name based on the space id logged inside the error log. Suppose We have some below error logged inside the error log file. 2021-01-01 10:32:01 4 [ERROR] InnoDB: page [page id: space=107, page number=47347] (920 records, index id 32519). From above error log, we can find the table name using the “space=107“. select SPACE,NAME from INFORMATION_SCHEMA.INNODB_SYS_TABLESPACES where SPACE='107'; +-------+--------------+ | SPACE | NAME | +-------+--------------+ | 107 | test/schools | +-------+--------------+ 1 row in set (0.00 s ..read more

This issue is the similar issue which is reported here https://github.com/sysown/proxysql/issues/1538. I found some workaround to fix this issue, without initialising or recreate/reconfigure your ProxySQL node. Problem: We have default ProxySQL user “admin” to connect the ProxySQL over the 6032 port. Once we connected and created the “admin” user account inside the mysql_users table and then loaded into the memory and persisted to disk, we are unable to connect the ProxySQL over port 6032 anymore. ERROR 1045 (28000): ProxySQL Error: Access denied for user 'admin'@'' (using password: YES) Sol ..read more

Problem : Here we are describing about one issue which we faced, After new installation of WordPress once we login as wp-admin(administrator) account, We were only able to see the profile section at the left side of dashboard which is generally applicable to the subscriber role user profile whereas we logged in as administrator role account. Solution : — To solve this issue, we will need to manually login to the database and change the user role from the subscriber to the administrator. [Here by default, admin user created with subscriber role instead of the admin role, which needs to be fixed ..read more

Here We have below nodes : Orchestrator Node : FlyWithEdu-Monitor : 172.31.46.134 Source/Master Node : FlyWithEduDB1 : 172.31.18.17 Replica/Slave Node : FlyWithEduDB2 : 172.31.7.71 Pre-requisites — Enabled below parameters on all database nodes of replication topology root@FlyWithEduDB1:~# cat /etc/mysql/percona-server.conf.d/mysqld.cnf |grep -A 7 -i Orchestrator ##Orchestrator report_host=172.31.18.17 report_port=3306 log-slave-updates binlog_format=ROW master_info_repository=TABLE relay_log_info_repository= TABLE read_only=1 root@FlyWithEduDB2:~# cat /etc/mysql/percona-serve ..read more

Here we are going to show, how we enabled the SSL certificate i.e. routed traffic through the https by default, for our WordPress blog site which is hosted in AWS EC2 node. Current details of our WordPress blog site : Hosted in : Amazon Web Services (AWS EC2) Operating System : Ubuntu 18.04.4 LTS (Bionic Beaver) Web Server : Apache Here it is visible that the site is Not Secure ie there is no pad lock sign visible. Before starting to enable the SSL certificate, here we will ensure that we have site config file present under the site-available apache’s directory. root@FlyWithEdu:~# ls -lrth ..read more

— Add/Rename hostname inside “/etc/hosts“ cat /etc/hosts 127.0.0.1 FlyWithEduDB2 — Add/Rename hostname inside “/etc/hostname“ cat /etc/hostname FlyWithEduDB2 — Dynamically update the hostname as well hostname FlyWithEduDB2 — Reboot the system sudo reboot The post Change hostname in Ubuntu appeared first on FlyWithEdu ..read more

Error Received HTTP status 400 on attempt 1 {"__type":"com.amazon.coral.service#UnrecognizedClientException","message":"The security token included in the request is invalid."} ERROR: Failed to call CloudWatch: HTTP 400. Message: The security token included in the request is invalid. For more information, run 'mon-put-instance-data.pl --help' Solution — Verify IAM user account have “CloudWatchFullAccess” policy attached. — Verify “AWSAccessKeyId” and “AWSSecretKey” are correctly placed inside the config file “awscreds.conf“. like below i.e. without any single or double quote. root@FlyWi ..read more