Broken Slave MySQL : How To Fix MySQL Replication (BINLOG) error in the Slave?

Before we start I can give some info about the versions, Ubuntu - 14.04, MySQL - 5.5 I have successfully configured the Master-Slave replication with two EC2 Ubuntu instances. My master is in Ubuntu 14 and slave is in Ubuntu 18. The replication was successful and the slave was replicating data for the last 3-4 days. But, suddenly my slave(Ubuntu 18) stopped replication with a query error. **Error Message :** Last_SQL_Error: Error 'Duplicate entry '11379183' for key 'PRIMARY'' on query. Default database: 'test'. Query: 'INSERT INTO testTable (id,value1,value2,value3,value4,value5,value6) VALUES(22,"5","429438","1592499300","1","8","1")' > Slave_IO_Running: Yes > > Slave_SQL_Running: No I have tried, > STOP SLAVE; > > SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; > > START SLAVE; It has helped me for some time. but the replication is broken again. How can we resolve this kind of replication errors? Is there any automated method for fixing the broken slave? Is GTID based replication possible with MySQL 5.5? I think GTID is available from MySQL version 5.6?