#StackBounty: #mysql #replication #mysql-5.6 #linux #master-slave-replication Replication doesn't resume once it fails to connect

Bounty: 50

We have MySQL replication running for our application. Right now the slave fails to resume if it fails to connect to the server for some time.

We get the error below:

[ERROR] Slave I/O: error connecting to master 'replication-user@master-ip:3306' - retry-time: 60  retries: 186, Error_code: 1045

The above is possible because of power failure or network problems. Once the issue is fixed and it is able to connect to the master server it tries to resume but most of the times it fails with the error below:

[ERROR] Slave SQL: 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. Error_code: 1594

I followed this question and solved this problem by resetting the slave to last read relay-bin file and position. The problem is that the connection failure has become very frequent and we need to do the same thing pretty often.

What could be the possible reason of this occurring over and over again? Is there a way to overcome this problem?

Note: We are using MySQL 5.6.30.


Get this bounty!!!

#StackBounty: #mysql #replication #mysql-5.6 #linux #master-slave-replication Replication doesn't resume once it fails to connect

Bounty: 50

We have MySQL replication running for our application. Right now the slave fails to resume if it fails to connect to the server for some time.

We get the error below:

[ERROR] Slave I/O: error connecting to master 'replication-user@master-ip:3306' - retry-time: 60  retries: 186, Error_code: 1045

The above is possible because of power failure or network problems. Once the issue is fixed and it is able to connect to the master server it tries to resume but most of the times it fails with the error below:

[ERROR] Slave SQL: 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. Error_code: 1594

I followed this question and solved this problem by resetting the slave to last read relay-bin file and position. The problem is that the connection failure has become very frequent and we need to do the same thing pretty often.

What could be the possible reason of this occurring over and over again? Is there a way to overcome this problem?

Note: We are using MySQL 5.6.30.


Get this bounty!!!

#StackBounty: #mysql #replication #mysql-5.6 #linux #master-slave-replication Replication doesn't resume once it fails to connect

Bounty: 50

We have MySQL replication running for our application. Right now the slave fails to resume if it fails to connect to the server for some time.

We get the error below:

[ERROR] Slave I/O: error connecting to master 'replication-user@master-ip:3306' - retry-time: 60  retries: 186, Error_code: 1045

The above is possible because of power failure or network problems. Once the issue is fixed and it is able to connect to the master server it tries to resume but most of the times it fails with the error below:

[ERROR] Slave SQL: 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. Error_code: 1594

I followed this question and solved this problem by resetting the slave to last read relay-bin file and position. The problem is that the connection failure has become very frequent and we need to do the same thing pretty often.

What could be the possible reason of this occurring over and over again? Is there a way to overcome this problem?

Note: We are using MySQL 5.6.30.


Get this bounty!!!

#StackBounty: #mysql #replication #mysql-5.6 #linux #master-slave-replication Replication doesn't resume once it fails to connect

Bounty: 50

We have MySQL replication running for our application. Right now the slave fails to resume if it fails to connect to the server for some time.

We get the error below:

[ERROR] Slave I/O: error connecting to master 'replication-user@master-ip:3306' - retry-time: 60  retries: 186, Error_code: 1045

The above is possible because of power failure or network problems. Once the issue is fixed and it is able to connect to the master server it tries to resume but most of the times it fails with the error below:

[ERROR] Slave SQL: 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. Error_code: 1594

I followed this question and solved this problem by resetting the slave to last read relay-bin file and position. The problem is that the connection failure has become very frequent and we need to do the same thing pretty often.

What could be the possible reason of this occurring over and over again? Is there a way to overcome this problem?

Note: We are using MySQL 5.6.30.


Get this bounty!!!

#StackBounty: #linux #ubuntu #grub GRUB can't see what os-prober found

Bounty: 100

There is an HDD and an SSD.

During Lubuntu installation on my HDD, it installed GRUB on HDD and os-prober made a menu entry for the SSD’s Windows partition.

But GRUB can’t see it on boot:

Error: no such device: 5CD2C8C949DA73C

The menu entry is:

menuentry 'Windows 8 (loader) (on /dev/sdb1)' --class windows    --class os $menuentry_id_option 'osprober-chain-5CD2C8C949DA73C' {
insmod part_msdos
insmod ntfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1    --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  5CD2C8C949DA73C
else
  search --no-floppy --fs-uuid --set=root 5CD2C8C949DA73C
fi
parttool ${root} hidden-
drivemap -s (hd0) ${root}
chainloader +1
}

Factors to consider:

  1. This is an MBR system.
  2. The SSD is inside a caddy.
  3. BIOS recognizes the SSD on POST as my secondary drive:
    Fixed Disk 0: HITACHI HTS.........300
    Fixed Disk 1: Samsung SSD 850 Evo 120GB
    
  4. Every OS and bootable utility including GRUB’s os-prober can see the SSD.
  5. BIOS does not show the SSD in boot options(We’re not planning to boot from it.).

Note: Workarounds like “Making the SSD boot-drive” or “Putting the SSD in the primary slot” are not acceptable for various reasons.

UPDATE: Asked about the “various reasons” in the comments: This is a ThinkPad E15. “Making the SSD boot-drive” is simply impossible due to the fact that “BIOS does not show the SSD in boot options” (It’s one of the ThinkPads with lack of ultra-bay support, and perhaps because of that, it’s designed for not booting a secondary HDD, so despite detecting it on POST as a Fixed Disk, does not show it in boot options. It only trys booting it as a CD-ROM and that doesn’t work. Also, one reason for not “Putting the SSD in the primary slot” is, I want shock protection for my HDD but again, this ThinkPad does not support it for a secondary drive according to this site.


Get this bounty!!!

#StackBounty: #linux #ubuntu #grub GRUB can't see what os-prober found

Bounty: 100

There is an HDD and an SSD.

During Lubuntu installation on my HDD, it installed GRUB on HDD and os-prober made a menu entry for the SSD’s Windows partition.

But GRUB can’t see it on boot:

Error: no such device: 5CD2C8C949DA73C

The menu entry is:

menuentry 'Windows 8 (loader) (on /dev/sdb1)' --class windows    --class os $menuentry_id_option 'osprober-chain-5CD2C8C949DA73C' {
insmod part_msdos
insmod ntfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1    --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  5CD2C8C949DA73C
else
  search --no-floppy --fs-uuid --set=root 5CD2C8C949DA73C
fi
parttool ${root} hidden-
drivemap -s (hd0) ${root}
chainloader +1
}

Factors to consider:

  1. This is an MBR system.
  2. The SSD is inside a caddy.
  3. BIOS recognizes the SSD on POST as my secondary drive:
    Fixed Disk 0: HITACHI HTS.........300
    Fixed Disk 1: Samsung SSD 850 Evo 120GB
    
  4. Every OS and bootable utility including GRUB’s os-prober can see the SSD.
  5. BIOS does not show the SSD in boot options(We’re not planning to boot from it.).

Note: Workarounds like “Making the SSD boot-drive” or “Putting the SSD in the primary slot” are not acceptable for various reasons.

UPDATE: Asked about the “various reasons” in the comments: This is a ThinkPad E15. “Making the SSD boot-drive” is simply impossible due to the fact that “BIOS does not show the SSD in boot options” (It’s one of the ThinkPads with lack of ultra-bay support, and perhaps because of that, it’s designed for not booting a secondary HDD, so despite detecting it on POST as a Fixed Disk, does not show it in boot options. It only trys booting it as a CD-ROM and that doesn’t work. Also, one reason for not “Putting the SSD in the primary slot” is, I want shock protection for my HDD but again, this ThinkPad does not support it for a secondary drive according to this site.


Get this bounty!!!

#StackBounty: #mysql #replication #mysql-5.6 #linux #master-slave-replication Replication doesn't resume once it fails to connect

Bounty: 50

We have MySQL replication running for our application. Right now the slave fails to resume if it fails to connect to the server for some time.

We get the error below:

[ERROR] Slave I/O: error connecting to master 'replication-user@master-ip:3306' - retry-time: 60  retries: 186, Error_code: 1045

The above is possible because of power failure or network problems. Once the issue is fixed and it is able to connect to the master server it tries to resume but most of the times it fails with the error below:

[ERROR] Slave SQL: 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. Error_code: 1594

I followed this question and solved this problem by resetting the slave to last read relay-bin file and position. The problem is that the connection failure has become very frequent and we need to do the same thing pretty often.

What could be the possible reason of this occurring over and over again? Is there a way to overcome this problem?

Note: We are using MySQL 5.6.30.


Get this bounty!!!

#StackBounty: #mysql #replication #mysql-5.6 #linux #master-slave-replication Replication doesn't resume once it fails to connect

Bounty: 50

We have MySQL replication running for our application. Right now the slave fails to resume if it fails to connect to the server for some time.

We get the error below:

[ERROR] Slave I/O: error connecting to master 'replication-user@master-ip:3306' - retry-time: 60  retries: 186, Error_code: 1045

The above is possible because of power failure or network problems. Once the issue is fixed and it is able to connect to the master server it tries to resume but most of the times it fails with the error below:

[ERROR] Slave SQL: 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. Error_code: 1594

I followed this question and solved this problem by resetting the slave to last read relay-bin file and position. The problem is that the connection failure has become very frequent and we need to do the same thing pretty often.

What could be the possible reason of this occurring over and over again? Is there a way to overcome this problem?

Note: We are using MySQL 5.6.30.


Get this bounty!!!

#StackBounty: #mysql #replication #mysql-5.6 #linux #master-slave-replication Replication doesn't resume once it fails to connect

Bounty: 50

We have MySQL replication running for our application. Right now the slave fails to resume if it fails to connect to the server for some time.

We get the error below:

[ERROR] Slave I/O: error connecting to master 'replication-user@master-ip:3306' - retry-time: 60  retries: 186, Error_code: 1045

The above is possible because of power failure or network problems. Once the issue is fixed and it is able to connect to the master server it tries to resume but most of the times it fails with the error below:

[ERROR] Slave SQL: 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. Error_code: 1594

I followed this question and solved this problem by resetting the slave to last read relay-bin file and position. The problem is that the connection failure has become very frequent and we need to do the same thing pretty often.

What could be the possible reason of this occurring over and over again? Is there a way to overcome this problem?

Note: We are using MySQL 5.6.30.


Get this bounty!!!

#StackBounty: #linux #ubuntu #grub GRUB can't see what os-prober found

Bounty: 100

There is an HDD and an SSD.

During Lubuntu installation on my HDD, it installed GRUB on HDD and os-prober made a menu entry for the SSD’s Windows partition.

But GRUB can’t see it on boot:

Error: no such device: 5CD2C8C949DA73C

The menu entry is:

menuentry 'Windows 8 (loader) (on /dev/sdb1)' --class windows    --class os $menuentry_id_option 'osprober-chain-5CD2C8C949DA73C' {
insmod part_msdos
insmod ntfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1    --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  5CD2C8C949DA73C
else
  search --no-floppy --fs-uuid --set=root 5CD2C8C949DA73C
fi
parttool ${root} hidden-
drivemap -s (hd0) ${root}
chainloader +1
}

Factors to consider:

  1. This is an MBR system.
  2. The SSD is inside a caddy.
  3. BIOS recognizes the SSD on POST as my secondary drive:
    Fixed Disk 0: HITACHI HTS.........300
    Fixed Disk 1: Samsung SSD 850 Evo 120GB
    
  4. Every OS and bootable utility including GRUB’s os-prober can see the SSD.
  5. BIOS does not show the SSD in boot options(We’re not planning to boot from it.).

Note: Workarounds like “Making the SSD boot-drive” or “Putting the SSD in the primary slot” are not acceptable for various reasons.

UPDATE: Asked about the “various reasons” in the comments: This is a ThinkPad E15. “Making the SSD boot-drive” is simply impossible due to the fact that “BIOS does not show the SSD in boot options” (It’s one of the ThinkPads with lack of ultra-bay support, and perhaps because of that, it’s designed for not booting a secondary HDD, so despite detecting it on POST as a Fixed Disk, does not show it in boot options. It only trys booting it as a CD-ROM and that doesn’t work. Also, one reason for not “Putting the SSD in the primary slot” is, I want shock protection for my HDD but again, this ThinkPad does not support it for a secondary drive according to this site.


Get this bounty!!!