Hi, On Dec 4, 2007 2:58 PM, Rolando Edwards <[EMAIL PROTECTED]> wrote: > 'errno 32 on write' > > That's a broken pipe error (Run 'perror 32' in Linux) > Maybe too much data is being pumped in through the pipe. > > Instead of this : > /usr/bin/mysqldump --all-databases -u root | /usr/bin/gzip -c > /backups/mysql_backup.gz > > Try it this way : > /usr/bin/mysqldump --all-databases -u root > AllData.txt > /usr/bin/gzip -c /backups/mysql_backup.gz < AllData.txt > > > -----Original Message----- > From: FMGreen [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 04, 2007 11:52 AM > To: mysql@lists.mysql.com > Subject: mysqldump (in crontab) failing with 'errno 32' even though it worked > last week > > > I use the mysqldump command (as below) in crontab to do a dump of my database > each night. Up until last week this was working fine. Last week (when I > was out of the office) there was a problem with the db and a colleague of > mine had to do a manual dump. When he tried to run mysqldump (using the > same command as I do) he got 'errno 32 on write'. > I just tried to run the command myself and also got 'errno 32 on write'. My > cronjob has also started failing even though crontab has not been changed. > I am very confused given that this exact command was working up until last > week. Can anyone shed light on what is going on? This is the command I > use, run as super user: > /usr/bin/mysqldump --all-databases -u root | /usr/bin/gzip -c > > /backups/mysql_backup.gz
$ perror 32 OS error code 32: Broken pipe Next question is, why is the pipe broken? My guess is lack of disk space or privileges. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
