Repair slave in MySQL GTID replication, after fatal error 1236 (master has purged binary logs)

For repairing a broken slave after fatal error 1236.

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.'

slave# reset master;

slave# source /pathto/dump.sql;

slave# start slave for channel 'mymaster';

slave# show slave status for channel 'mymaster'\G

Here is another useful tutorial, if the problem persists

https://www.percona.com/blog/2013/02/08/how-to-createrestore-a-slave-using-gtid-replication-in-mysql-5-6/

Demo of OpenAI GPT-3

Incredible demos of OpenAI GPT-3, watch this video!

https://www.youtube.com/watch?v=8psgEDhT1MM

Mind-blowing conversations with OpenAI GPT-3

https://medium.com/@kirkouimet/my-mind-blowing-conversations-openais-latest-ai-gpt-3-235ba5fb9453

Folding@Home contro il COVID-19

Folding@Home contro il COVID-19: una potenza mai vista per il calcolo distribuito. Contribuiamo tutti col nostro PC 💪💪

#uniticontroilcoronavirus

https://foldingathome.org

Partecipare al progetto Folding@home è semplicissimo. Basta recarsi sul sito ufficiale, scaricare il client (funziona su Windows, Mac e Linux) e, in automatico, parte della potenza del nostro PC verrà dedicata alla ricerca. L’unione fa la forza.

Repair slave in MySQL GTID replication

Run these commands on MySQL shell, to find "where" replication failed and was broken.

Stop the slave.
SET GTID_NEXT="AUTOMATIC";
stop slave;

Find the point where replication broke.
show slave status\G;

Now find "Executed_Gtid_Set". Example value:
Executed_Gtid_Set: 44d966cc-d84d-11e8-be8d-20677cd3f384:1-2872

Increase of one step to 2873
SET GTID_NEXT="44d966cc-d84d-11e8-be8d-20677cd3f384:2873";

Now start the slave.
start slave;
show slave status\G;


Here is another useful tutorial, if the problem persists
https://www.percona.com/blog/2013/02/08/how-to-createrestore-a-slave-using-gtid-replication-in-mysql-5-6/

Continue the loop until no error occurs. Enjoy

Choosing a visual to represent data

How do you choose a visual to represent data?

Here is a handy diagram that can be used to determine the right chart type to use in your data visualization.

How To Secure MySQL Replication Using SSH

https://www.digitalocean.com/community/tutorials/how-to-secure-mysql-replication-using-ssh-on-a-vps

http://makandracards.com/makandra/573-mysql-replication-how-to

http://www.somacon.com/p567.php


Bi-directional SSH tunnel

local$: ssh -N -R 33061:localhost:3306 remote_host_ip

remote$: ssh -p 33061 localhost


Create/restore a slave using GTID replication
https://www.percona.com/blog/2013/02/08/how-to-createrestore-a-slave-using-gtid-replication-in-mysql-5-6/


MySQL Multi-Source Replication
http://www.xenialab.it/meo/web/white/oracle/myrepl_multi.htm

If we have a chain of slaves, it's important to enable slave update logging, on config file:
log-slave-updates = 1

Unable to install Certbot

Error on installing Certbot for Lets Encrypt

# apt-get install -t jessie-backports certbot python-certbot-apache Reading package lists... Done E: The value 'jessie-backports' is invalid for APT::Default-Release as such a release is not available in the sources

Solution:
You should first enable backports, see https://backports.debian.org/Instructions
http://guide.debianizzati.org/index.php/Il_repository_Backports