Hi,
I run the mysqltuner at my server as below and i got error like below.
[root@127 /]# ./mysqltuner.pl
>> MySQLTuner 1.0.1 - Major Hayden <major@stripped>
>> Bug reports, feature requests, and downloads at http://mysqltuner.com/
>> Run with '--help' for additional options and output filtering
Please enter your MySQL administrative login: root
Please enter your MySQL administrative password:
[!!] Attempted to use login credentials, but they were invalid.
On some other server this script is running absolutely fine without any change in
mysqltuner.pl.
Please guide me how can i run this script
Thanks & Regards
Jeetendra Ranjan
----- Original Message -----
From: "Bruce Ferrell" <bferrell@stripped>
To: <jeetendra.ranjan@stripped>
Cc: <mysql@stripped>
Sent: Thursday, October 15, 2009 12:20 PM
Subject: Re: Req. suitable .cnf file for Server used by 2000 users daily
>
> Have a look at mysqltuner. It reads the stats from a running mysql
> instances and makes suggestions for what can be changed
>
> http://blog.mysqltuner.com/
>
>
>
> Gavin Towey wrote:
>> Hi,
>>
>> This script might help with some tuning suggestions, run it after you have some
> production traffic running against your database.
>> https://launchpad.net/mysql-tuning-primer
>>
>> Also you should enable the slow query log, so you can capture queries to be
> optimized:
>> http://dev.mysql.com/doc/mysql/en/Slow_query_log.html
>>
>> http://dev.mysql.com/doc/refman/5.0/en/mysql-indexes.html
>>
>>
>> Regards,
>> Gavin Towey
>>
>>
>> -----Original Message-----
>> From: jeetendra.ranjan@stripped [mailto:jeetendra.ranjan@stripped]
>> Sent: Wednesday, October 14, 2009 3:21 AM
>> To: mysql@stripped
>> Subject: Req. suitable .cnf file for Server used by 2000 users daily
>>
>> Hi,
>> Will you plesae guide me ?
>> We are about to launch one website whose database is in MySQL. I am very exited
> about the server setting specially about .cnf file.
>> I have below hardware and .cnf details. Will you please guide me is the .cnf file
> details sufficient to support current hardware.
>> Initially 2000 users will visit this site everyday.
>>
>> Hardware and OS
>> *************
>> Operating System : Red Hat Fedora Core 8
>> Processor : Intel Core 2 Quad - 2.83 GHz,
>> RAM : 4 GB
>> Total Disk Space : 600 GB (300 GB usable)
>> RAID : RAID1
>> Disk Drive(s) : 300 GB (Drive #1), 300 GB (Drive #2)
>> Bandwidth Quota : 500 GB
>> Firewall : PIX 501
>> Version : 5.0.81-community-log
>> Version_comment : MySQL Community Edition (GPL)
>> Version Compile Machine : i686
>> Version Compile OS : pc-linux-gnu
>> my.cnf details
>> ***********
>> [mysqld]
>> 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
>> key_buffer = 16M
>> key_buffer_size=4M
>> sort_buffer_size=2M
>> query_cache_size=64M
>> log-bin
>> log_queries_not_using_indexes=1
>> long_query_time=1
>> log_slow_queries=slowQry.log
>> join_buffer_size=4M
>> max_connections=150
>> max_allowed_packet = 32M
>> table_cache = 256
>> net_buffer_length = 8K
>> read_buffer_size = 2M
>> read_rnd_buffer_size = 2M
>> myisam_sort_buffer_size = 8M
>> thread_stack=5M
>> thread_cache_size=128M
>> connect_timeout=30
>> query_cache_limit=32M
>> log-error
>> # Comment the following if you are using InnoDB tables
>> innodb_data_home_dir = /var/lib/mysql/
>> innodb_data_file_path = ibdata1:10M:autoextend
>> innodb_log_group_home_dir = /var/lib/mysql/
>> # You can set .._buffer_pool_size up to 50 - 80 %
>> # of RAM but beware of setting memory usage too high
>> innodb_buffer_pool_size = 4M
>> innodb_additional_mem_pool_size = 2M
>> # Set .._log_file_size to 25 % of buffer pool size
>> innodb_log_file_size = 16M
>> innodb_log_buffer_size = 8M
>> innodb_flush_log_at_trx_commit = 1
>> innodb_lock_wait_timeout = 50
>> [mysqld_safe]
>> log-error=/var/log/mysqld.log
>> pid-file=/var/run/mysqld/mysqld.pid
>> Thanks in advance
>> Regards
>> Jeetendra Ranjan
>>
>>
>> The information contained in this transmission may contain privileged and
> confidential information. It is intended only for the use of the person(s) named above. If
> you are not the intended recipient, you are hereby notified that any review,
> dissemination, distribution or duplication of this communication is strictly prohibited.
> If you are not the intended recipient, please contact the sender by reply email and
> destroy all copies of the original message.
>>
