mysqldump: Got errno 32 on write

The message Got errno 32 on write means Broken pipe and happens when you are piping the mysqldump output to another command (for example, Gzip). This means the program who is receiving the output terminated prior to mysqldump. For example, if Gzip is the program you are piping to, it can happen that the disk space full or it surpassed any max CPU/time usage your host may have in place.

How to fix it?

First of all, check the disk space and make sure you don't have any CPU/time limitation in place from your host. If the problem still persists, try to maually execute the command you are piping to in order to see what error message is returning. For example, if you are piping to Gzip, try to run Gzip on a dump file and check the error returned.