Got fatal error 1236 from master when reading data from binary log

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-1111-2222-111111111111:10′.’

Can’t auth ProxySQL with admin to 6032 when created user ‘admin’ under mysql_users table

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 […]

Profile section is only visible on dashboard after new WordPress installation

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.

Relay log read failure

Last_Errno: 1594
Last_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master’s binary log is corrupted (you can check this by running ‘mysqlbinlog’ on the binary log), the slave’s relay log is corrupted (you can check this by running ‘mysqlbinlog’ on the relay log), a network problem, or a bug in the master’s or slave’s MySQL code. If you want to check the master’s binary log or slave’s relay log, you will be able to know their names by issuing ‘SHOW SLAVE STATUS’ on this slave.