./automysqlbackup.sh.2.5: Command not found.

To run it in FreeBSD, you need to edit a single line. Automysqlbackup.sh.2.5 is a bash script, and it references the path ‘/bin/sh’. In freebsd, bash is installed at ‘/usr/local/bin/bash.’ If you haven’t already, install bash:

pkg_add -r bash

Then all you have to do is edit automysqlbackup.sh.2.5. Look for

#!/bin/bash

and change it to

#!/usr/local/bin/bash

Now you should be able to launch it properly by running ‘./automysqlbackup.sh.2.5′. creating a symlink would probably work, but i like this better.

I was getting annoyed that when listing my tables in phpmyadmin,  it would show the list of tables in InnoDB (which is what i wanted), but then, when showing the summary at the bottom of the page, said “MyIsam”. I easily got rid of it by adding “default-storage-engine=InnoDB” to my “my.cnf” file.

FreeBSD does not automatically include a default my.cnf for MySQL. Instead, a set of sample configuration files can be found under /usr/local/share/mysql. These configuration files include my-small.cnf, my-medium.cnf, my-large.cnf, my-innodb-heavy-4G, and my-huge.cnf. The appropriate file can be copied and used as a template configuration by performing the following actions:
cd /usr/local/share/mysql/
cp /usr/local/share/mysq/mysql-large.cnf /etc/my.cnf
/usr/local/etc/rc.d/mysql-server restart

thanks to http://www.barik.net/archive/2008/05/26/114616/ for the tip. ]]> http://www.surlyjake.com/mysql/freebsd-mysql-configuration/feed/ 0 http://www.surlyjake.com/mysql/what-not-to-do-in-mysql-and-how-to-pick-up-the-pieces/?utm_source=rss&utm_medium=rss&utm_campaign=what-not-to-do-in-mysql-and-how-to-pick-up-the-pieces http://www.surlyjake.com/mysql/what-not-to-do-in-mysql-and-how-to-pick-up-the-pieces/#comments Wed, 17 Sep 2008 03:31:13 +0000 jacob http://www.surlyjake.com/?p=14 note to self… do NOT kill mysql processes from phpmyadmin’s control panel and force mysql to quit. Bad things happen. In this case, mysql wouldnt start again. InnoDB’s indexes, binary logs, etc. were all out of sync. The 20 page log explaining all the ways the DB couldn’t start is located in the DB’s data dir, which in my case was in /dbdisks/<hostname>.err.

To tell mysql to pick up the messy pieces and throw up whats left of your data, edit or create /etc/my.cnf and add this little line to the “[mysqld]” section:

innodb_force_recovery = 3


The command is talked aboot here the number is btw 1 and 6. bigger the number, the more drastic and desperate it is. I tried 4, and it pulled the tables with no data. 1 gave me nothing. but 3 let me start and mysqldump my database.

mysqldump -u root -p <dbname > /path/to/.sql/file


so once the dump was completed, i moved the db data directory, commented out the “innodb_force_recovery” line, and restarted the computer. At restart the db data dir was re-created by mysql. fresh and clean. this deletes EVERYTHING. even users. re-import the data with

mysql -u root <dbname> < /path/to/.sql/file


go ahead and create the users needed, and set root password again. There you go.