Atomicorp

Posted: **Thu Jun 17, 2010 8:24 am**

1.5 Check mysqld.log for errors and update my.conf accordingly

edit: Might also be considered 0.5 if you know what to change.

Posted: **Thu Jun 17, 2010 8:48 am**

biggles wrote:1.5 Check mysqld.log for errors and update my.conf accordingly

edit: Might also be considered 0.5 if you know what to change.

Well i just looked at my my.cnf and removed the skip-bdb line and from what i've gathered the rest of it looks fine from my limited knowledge.

Code: Select all

[mysqld]
set-variable=local-infile=0
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
wait_timeout=3600
max_user_connections=400
max_connections=400
query_cache_size=128M
log_slow_queries=/var/log/mysqld.slow.log
long_query_time=5
thread_cache_size=6
thread_concurrency=4
key_buffer_size=128M
join_buffer_size=1M
table_cache=18000
tmp_table_size=128M
max_heap_table_size=128M
innodb_buffer_pool_size=16M


[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

Posted: **Thu Jun 17, 2010 12:15 pm**

I think step three and four need to not have the admin password in the command, and it will ask for the password...at least that works on my server...

e.g.
# mysqlcheck -u admin -p --auto-repair --check --optimize --all-databases
# password:

Posted: **Thu Jun 17, 2010 1:22 pm**

You can either do it as

Code: Select all

mysql -u admin -ppassword

Note that the lack of a space in the command is NOT a typo. The drawback here is that anyone can go back in your bash history and get in this way.
Or you can do it as

Code: Select all

mysql -u admin -p

and mysql will prompt you for your password. This syntax extends to all mysql CLI tools (mysql, mysqldump, mysql_upgrade, etc)

mysqlcheck -u <admin> -p <password> --auto-repair --check --optimize --all-databases

I don't think this is necessary. mysql_upgrade will repair tables as needed.

Posted: **Thu Jun 17, 2010 4:03 pm**

regarding the my.cnf...isn't the

tmp_table_size=128M
max_heap_table_size=128M

quite extreme? I have mine at 2-6mb, and the mysqltuner tweaks me up or down in that range consistently. I don' knw, maybe your require all that.

Posted: **Thu Jun 17, 2010 4:08 pm**

mneese77 wrote:regarding the my.cnf...isn't the
tmp_table_size=128M
max_heap_table_size=128M
quite extreme? I have mine at 2-6mb, and the mysqltuner tweaks me up or down in that range consistently. I don' knw, maybe your require all that.

That's what i always thought too but for some reason when the server was setup and the amount of DB's on it with cleints one of our former server admins ran mysqltuner and used something else to come up with that. But since it was'nbt broke or seemed to cause issues that i could see i left it alone.

Posted: **Thu Jun 17, 2010 4:45 pm**

Just tor keep things updated...
the upgrade error that I was repeatedly getting was

RROR 29 (HY000) at line 334: File '/var/log/mysql-slow.log' not found (Errcode: 13)

only permissions concerns...the files that the my.cnf pointed to for error logs required mysql as owner, and permissions set to 644. Now it works for the upgrade with NO errors....

Thanks everyone for chipping in with all this important information....
Love this forum!

Posted: **Fri Jun 18, 2010 2:39 pm**

mneese77 wrote:regarding the my.cnf...isn't the
tmp_table_size=128M
max_heap_table_size=128M
quite extreme? I have mine at 2-6mb, and the mysqltuner tweaks me up or down in that range consistently. I don' knw, maybe your require all that.

Easy way to find out

Code: Select all

#yum install mysqltuner
#mysqltuner

Enter admin and your Plesk password and let it run. It will recommend changes to your my.cnf

Posted: **Tue Jun 22, 2010 7:07 am**

Highland wrote:
mneese77 wrote:regarding the my.cnf...isn't the
tmp_table_size=128M
max_heap_table_size=128M
quite extreme? I have mine at 2-6mb, and the mysqltuner tweaks me up or down in that range consistently. I don' knw, maybe your require all that.
Easy way to find out
Code: Select all
#yum install mysqltuner
#mysqltuner
Enter admin and your Plesk password and let it run. It will recommend changes to your my.cnf

I've been running mysqltuner for a couple years on our boxes and with those settings it never complained about those high settings. i did change my.cnf to the ones you use and seems to made no difference in the report after running mysql tuner.

On a side note, Thanks to those that answered my questions about the upgrade. I did it this morning and had no issues and all seems to be working well.

Posted: **Wed Jun 23, 2010 5:02 am**

mysqlcheck -uadmin -p`cat /etc/psa/.psa.shadow` --auto-repair --check --optimize --all-databases

This is the best if you are under PLESK.

Atomicorp

[atomic] Mysql 5.1.47

Re: [atomic] Mysql 5.1.47

Re: [atomic] Mysql 5.1.47

Re: [atomic] Mysql 5.1.47

Re: [atomic] Mysql 5.1.47

Re: [atomic] Mysql 5.1.47

Re: [atomic] Mysql 5.1.47

Re: [atomic] Mysql 5.1.47

Re: [atomic] Mysql 5.1.47

Re: [atomic] Mysql 5.1.47

Re: [atomic] Mysql 5.1.47