Sysbk mysql part fails in Debian 3.1

P

PauGasol

Verified User
Joined
Feb 3, 2004
Messages
125
Hi,

Performing MySQL backup
Stage 1 MySQL backup:MySQL could not be shutdown, aborting...

All semms ok :

if [ "$OS" = "debian" ]; then
MYSQL_PATH="/home/mysql"
MYSQL_INIT="/etc/init.d/mysqld"
MYSQL_PID="$MYSQL_PATH/`hostname -s`.pid"
MYSQL_DUMP="/usr/local/mysql/bin/mysqldump"
MYSQL_MYICHK="/usr/local/mysql/bin/myisamchk"


The rest of sysbk ok. Any ideas ?

Thanks
 
MySQL sometimes has problems shutting down. I believe the cause is heavy use. Can you change yor sysbk to run at a different time?

Jeff
 
No , same error , the load average is less than 0.5 .

The log is very short and undescriptive , only "Performing MySQL backup
Stage 1 MySQL backup:MySQL could not be shutdown, aborting...
"

any ideas? thanks
 
The best way to troubleshoot this would be to, at approximately the same time you want to run sysbk, log in as root and run the following commands:

# ps waux | grep mysql

and then look to see how many instances are running...

then (I'm presuming a Red Hat linux distribution; if not, then do it the way your distribution does it:

# service mysqld stop

and watch to see if it stops fully or if the stop aborts...

then...

# ps waux | grep mysql

should show at least some instances have stopped.

Keep repeating that "service mysqld stop" command to see how long it takes.

Note this WILL shut down mysqld, and could affect your users.

Personally, I think that MySQL not wanting to shutdown nicely and stop when sent the proper signal is something that the MySQL development team should be able to fix.

It's NOT a sysbk or a DA issue, but unfortunately we're stuck with it.

I've been able to come up times for my servers that they do manage backups most of the time, when scheduled.

Jeff
 
Filin said:
Have same problem. Any ideas?
Click to expand...

I had two boxes with Debian 3.1 . One fails, the other works ok . The solution is easy, the mysql files are in /home/mysql/.... by that you will have a copy of the databases in the original format.

I didnt find other solution. Hope this help
 
Yes but if MySQL isn't stopped when you're backing up the files, they may very well be an inconsistent state, so they may be useless for a restore.

You can change the number of seconds sysbk waits for MySQL to stop in:

/usr/local/sysbk/mod/mysql.bk

in line 10; change the number after sleep to the number of seconds you want to wait.

Jeff
 
You must log in or register to reply here.
Back
Top