Hi Sean. Thanks for your reply. I don't think the control-C was likely because I was running the mysqldump as part of a shell script I wrote to clone a staging server. This was on a shared hosting service, so I guess it is possible without my knowledge that the system administrator decided to kill the process? I did the command manually a minute later and it worked, and when I re-run the shell script with the mysqldump in it, there were no errors.
If I wasn't reviewing the execution of the shell script, I could have easily missed the error message. Maybe it would be a good idea to check on the exit status of mysqldump to make sure it exists properly? Because the script didn't terminate on this error message. David Roth On Mon, Sep 12, 2011 at 12:30 PM, Sean Hull <[email protected]> wrote: > > Hi David, > > Is it possible you hit ctrl-C during the session? Alternatively could > someone else have run a "kill -HUP" on the mysqldump process, or used the > kill command from within mysql shell? > > -Sean > > > +1-917-442-3939 > Get My Monthly Newsletter: http://eepurl.com/qPF1 > >> >> Date: Mon, 12 Sep 2011 07:52:46 -0400 >> From: David Roth <[email protected]> >> To: MySQL SIG <[email protected]> >> Subject: [mysql] Query execution was interrupted (1317) ? >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes >> >> I was doing a mysqldump and say this error message at the command >> line, "Query execution was interrupted (1317)". I repeated the command >> to reproduce this and it worked fine and without error. >> >> Anyone know what this message means? Is there cause for concern? Thanks! >> >> David Roth >> > > _______________________________________________ New York PHP Community MySQL SIG http://lists.nyphp.org/mailman/listinfo/mysql NYPHPCon 2006 Presentations Online http://www.nyphpcon.com Show Your Participation in New York PHP http://www.nyphp.org/show_participation.php
