夜行人 » MySQL

查看nginx，apache，mysql，php编译参数

admin — Wed, 26 Oct 2011 04:57:23 +0000

有时候nginx，apache，mysql，php编译完了想看看编译参数可以用以下方法

nginx编译参数：
#/usr/local/nginx/sbin/nginx -V
nginx version: nginx/0.6.32

built by gcc 4.1.2 20071124 (Red Hat 4.1.2-42)

configure arguments: --user=www --group=www --prefix=/usr/local/nginx/ --with-http_stub_status_module --with-openssl=/usr/local/openssl

apache编译参数：
# cat /usr/local/apache2/build/config.nice
#! /bin/sh

# Created by configure

"./configure" \

"--prefix=/usr/local/apache2" \

"--with-included-apr" \

"--enable-so" \

"--enable-deflate=shared" \

"--enable-expires=shared" \

"--enable-rewrite=shared" \

"--enable-static-support" \

"--disable-userdir" \

"$@"

php编译参数：

# /usr/local/php/bin/php -i |grep configure

Configure Command => './configure' '--prefix=/usr/local/php' '--with-apxs2=/usr/local/apache2/bin/apxs' '--with-config-file-path=/usr/local/php/etc' '--with-mysql=/usr/local/mysql' '--with-libxml-dir=/usr/local/libxml2/bin' '--with-gd=/usr/local/gd2' '--with-jpeg-dir' '--with-png-dir' '--with-bz2' '--with-xmlrpc' '--with-freetype-dir' '--with-zlib-dir'

mysql编译参数：

# cat "/usr/local/mysql/bin/mysqlbug"|grep configure

# This is set by configure

CONFIGURE_LINE="./configure '--prefix=/usr/local/mysql' '--localstatedir=/var/lib/mysql' '--with-comment=Source' '--with-server-suffix=-H863' '--with-mysqld-user=mysql' '--without-debug' '--with-big-tables' '--with-charset=gbk' '--with-collation=gbk_chinese_ci' '--with-extra-charsets=all' '--with-pthread' '--enable-static' '--enable-thread-safe-client' '--with-client-ldflags=-all-static' '--with-mysqld-ldflags=-all-static' '--enable-assembler' '--without-isam' '--without-innodb' '--without-ndb-debug'"

转载自：http://hi.baidu.com/xi4oyu/blog/item/8a0e1ed020e81adb562c8452.html

利用rpmbuild制作MySQL的rpm包

admin — Wed, 19 Oct 2011 01:16:08 +0000

1、配置环境
yum -y install rpmbuild
2、下载源代码rpm包
mkdir /root/download
cd /root/download
wget http://www.percona.com/redir/downloads/Percona-Server-5.1/Percona-Server-5.1.58-12.9/source/Percona-Server-51-5.1.58-rel12.9.271.rhel6.src.rpm

3、安装打包MySQL时依赖的包

yum -y install perl readline-devel gcc-c++ ncurses-devel zlib-devel libtool automake autoconf time ccache bison

4、安装percona的源代码
rpm -ivh Percona-Server-51-5.1.58-rel12.9.271.rhel6.src.rpm

安装了2个文件，它们的位置是
/root/rpmbuild/SOURCES/Percona-Server-5.1.58.tar.gz
/root/rpmbuild/SPECS/percona-server.spec

5、修改percona-server.spec
加入我们自己的编译参数
vi percona-server.spec
将
# The --enable-assembler simply does nothing on systems that does not
# support assembler speedups.
和
%if %{YASSL_BUILD}
之间的一段修改成这样

# The --enable-assembler simply does nothing on systems that does not
# support assembler speedups.
sh -c "CFLAGS=\"$CFLAGS\" \
        CXXFLAGS=\"$CXXFLAGS\" \
        AM_CPPFLAGS=\"$AM_CPPFLAGS\" \
        LDFLAGS=\"$LDFLAGS\" \
        ./configure \
            $* \
            --with-comment=MC-DB \
            --with-server-suffix=-MC-DB-Server \
            --with-charset=utf8 \
            --with-plugins=blackhole,csv,innodb_plugin \
            --enable-assembler \
            --enable-local-infile \
            --with-mysqld-user=%{mysqld_user} \
            --with-unix-socket-path=/tmp/mysql.sock \
            --with-pic \
            -prefix=/usr \
            --with-extra-charsets=gbk,gb2312,utf8 \
            --without-debug \
            --with-pthread \
            --enable-thread-safe-client \
            --with-client-ldflags=-all-static \
            --without-ndb-debug \
%if %{YASSL_BUILD}

保存退出

6、定义在打包过程中不进行测试
export MYSQL_RPMBUILD_TEST="no"

7、开始打包
cd /root/rpmbuild/SPECS/
rpmbuild -bb percona-server.spec
等待一段时间就可以看到编译好的软件包
/root/rpmbuild/RPMS/x86_64

Percona-Server-client-51-5.1.58-rel12.9.rhel6.x86_64.rpm
Percona-Server-devel-51-5.1.58-rel12.9.rhel6.x86_64.rpm
Percona-Server-server-51-5.1.58-rel12.9.rhel6.x86_64.rpm
Percona-Server-shared-51-5.1.58-rel12.9.rhel6.x86_64.rpm
Percona-Server-test-51-5.1.58-rel12.9.rhel6.x86_64.rpm

7、安装顺序
先安装这个
Percona-Server-shared-51-5.1.58-rel12.9.rhel6.x86_64.rpm
再安装其他软件包
8、已知问题：
无法打包为一个包
无法将所有问题安装到一个目录，例如我们之前一直安装的目录/usr/local/mysql

9、题外话
一般MySQL源代码包都有包含打包所需要的spec文件，一般存放在support-files/下

自动kill掉超时的mysql show processlist进程

admin — Thu, 23 Sep 2010 13:57:02 +0000

DB_HOST="localhost"
DB_PORT=3306
DB_USER="root"
DB_PASS=""
maxtime=10
sql="SHOW PROCESSLIST"
sss=$(/usr/bin/mysqladmin processlist|sed -e "s/\s//g"|awk -F'|' '{print $2,$7,substr($9,1,6)}'|awk '{if($2>'"$maxtime"' && $3=="SELECT"){print $1}}')
for pid in $(echo "$sss"); do
/usr/bin/mysql -h$DB_HOST -P$DB_PORT -u$DB_USER -p$DB_PASS -e "kill $pid"
done
echo "$sss"
date

转载自：http://home.phpchina.com/space.php?uid=24549&do=blog&id=158758

MySQL报错：my_global.h151615 error new No such file or directory

admin — Mon, 13 Sep 2010 09:42:40 +0000

今天安装MySQL,在make的时候报错，错误信息如下：

In file included from mysys_priv.h:16,
from my_new.cc:21:
../include/my_global.h:1516:15: error: new: No such file or directory
make[1]: *** [my_new.o] Error 1
make[1]: Leaving directory `/opt/mysql-5.1.45-10/mysys'
make: *** [all-recursive] Error 1

检查了操作系统版本等情况，都没问题，configure时也没报错，可以正常产生Makefile

将有问题服(假设是A机)的config.log和另外一台正常服(假设是B机)的config.log做对比

发现A机，有2处比较严重的报错

conftest.c:181:21: error: termcap.h: No such file or directory
conftest.cpp:314:20: error: cxxabi.h: No such file or directory

在B机上
updatedb

for i in `locate termcap.h`; do rpm -qf $i; done |uniq
输出：
libtermcap-devel-2.0.8-46.1
ncurses-devel-5.5-24.20060715
dev86-0.16.17-2.2

for i in `locate cxxabi.h`; do rpm -qf $i; done |uniq
输出：

libstdc++-devel-4.1.2-48.el5
libstdc++44-devel-4.4.0-6.el5
xulrunner-devel-1.9.0.18-1.el5_4

到A机上用rpm -qa查询libtermcap-devel，ncurses-devel，dev86，libstdc++-devel，libstdc++44，xulrunner-devel的安装情况
发现libtermcap-devel，dev86，libstdc++-devel没有安装

yum -y install libtermcap-devel dev86 libstdc++-devel

然后再make，就没有报错了

MySQL调优脚本tuning-primer.sh使用说明

admin — Tue, 07 Sep 2010 08:32:25 +0000

大名鼎鼎的MySQL调优脚本tuning-primer.sh官方下载地址：http://forge.mysql.com/projects/project.php?id=44 -> https://launchpad.net/mysql-tuning-primer, 直接下载地址： http://launchpad.net/mysql-tuning-primer/trunk/1.5-r5/+download/tuning-primer.sh

该脚本使用 “SHOW STATUS LIKE…” 和 “SHOW VARIABLES LIKE…” 命令获得MySQL相关变量和运行状态。然后根据推荐的调优参数对当前的MySQL数据库进行测试。最后根据不同颜色的标识来提醒用户需要注意的各个参数设置。该版本兼容 MySQL 3.23 和更高版本（包含 5.1）

当前版本会处理如下这些推荐的参数：

[Copy to clipboard]View Code

 Slow Query Log （慢查询日志）
 Max Connections （最大连接数）
 Worker Threads （工作线程）
 Key Buffer （Key 缓冲）
 Query Cache （查询缓存）
 Sort Buffer （排序缓存）
 Joins （连接）
 Temp Tables （临时表）
 Table (Open & Definition) Cache （表缓存）
 Table Locking （表锁定）
 Table Scans (read_buffer) （表扫描，读缓冲）
 Innodb Status （Innodb 状态）

tuning-primer.sh 有如下运行参数:

[Copy to clipboard]View Code

Usage: ./tuning-primer.sh [ mode ]
all            运行所有检测(默认值)
prompt         显示提示信息
mem, memory    运行有关内存使用方面的检测
disk, file     运行有关I/O性能和文件处理限制方面的检测
innodb         运行InnoDB检测
misc           其它

脚本支持my.cnf文件，可以把user, password, host, socket等连接参数放在~/.my.cnf文件里，如果使用了自定义的socket文件，请修改tuning-primer.sh文件中关于socket文件位置的变量。

运行 tuning-primer.sh显示说明

SLOW QUERIES	慢查询检查
SLOW QUERIESThe slow query log is enabled.	说明我已经启用了慢查询记录功能。也就是参数 slow_query_log = 1
Current long_query_time = 5.000000 sec.	慢查询的阀值时间。也就是参数 long_query_time = 5
You have 17 out of 638844 that take longer than 5.000000 sec. to complete	说明慢查询日志中记录了17条查询时间超过5秒的语句。 slow_query_log_file=/data/ats_db/mysql-slow.log设置慢查询日志路径。使用mysqldumpslow命令查询慢日志
Your long_query_time seems to be fine	慢查询阀值时间设置得在推荐的范围内

BINARY UPDATE LOG	更新二进制日志文件
The binary update log is enabled	这项说明启用了bin-log日志功能。参数 log-bin = /data/ats_db/mysql-bin
Binlog sync is not enabled, you could loose binlog records during a server crash	没有启用 sync_binlog 选项。也即是将二进制日志实时写入到磁盘通过 sync_binlog=1来指定

WORKER THREADS	工作线程
Current thread_cache_size = 8	当前线程缓存大小。 thread_concurrency = 8
Current threads_cached = 7	Show status like ‘threads_cached’
Current threads_per_sec = 0	脚本先执行Show status like ‘Threads_cached’查看当前的线程创建情况，然后sleep 1后在执行相同的命令，最终后者减去前者的数就是每秒线程创建数。
Historic threads_per_sec = 0	该值是使用Threads_cached /uptime获得的。
Your thread_cache_size is fine

MAX CONNECTIONS	最大连接数
Current max_connections = 1024	当前配置文件中设置的并发连接数
Current threads_connected = 2	当前线程连接诶数。 show status like ‘Threads_connected’
Historic max_used_connections = 4	show status like ‘Max_used_connections’;
The number of used connections is 0% of the configured maximum.	这个值使用 Max_used_connections*100/ max_connections得出。
You are using less than 10% of your configured max_connections. Lowering max_connections could help to avoid an over-allocation of memory See “MEMORY USAGE” section to make sure you are not over-allocating	Max_used_connections的值不足max_connections值的10%。设置合适的max_connections值有助于节省内存。

MEMORY USAGE	内存使用
Max Memory Ever Allocated : 841 M	Max Memory Ever Allocated = max_memory
Configured Max Per-thread Buffers : 28.40 G	Configured Max Per-thread Buffers = per_thread_buffers
Configured Max Global Buffers : 586 M	Configured Max Global Buffers = per_thread_max_buffers
Configured Max Memory Limit : 28.97 G	Configured Max Memory Limit = total_memory 这一项很重要，他是将各个缓存的大小累加，然后同max_connections相乘，从而得出当达到max_connections后需要分配的内存有多少。我这里由于max_connections写得很大，造成了最大内存限制超过了真实内存很多，所以建议不要随意增大max_connections的值。减小 max_connections的值，最终保证最大内存限制在真实内存的90%以下。
Physical Memory : 7.79 G	实际物理内存
Max memory limit exceeds 90% of physical memory
per_thread_buffers (read_buffer_size+read_rnd_buffer_size +sort_buffer_size+thread_stack+ join_buffer_size+binlog_cache_size)max_connectionsper_thread_max_buffers (read_buffer_size+read_rnd_buffer_size +sort_buffer_size+thread_stack +join_buffer_size+binlog_cache_size)max_used_connectionsglobal_buffers innodb_buffer_pool_size+innodb_additional_mem_pool_size+innodb_log_buffer_size+ key_buffer_size+query_cache_sizemax_memory=global_buffers+per_thread_max_buffers total_memory=global_buffers+per_thread_buffers

KEY BUFFER	Key 缓冲
Current MyISAM index space = 222 K	当前数据库MyISAM表中索引占用磁盘空间
Current key_buffer_size = 512 M	MySQL配置文件中key_buffer_size 设置的大小
Key cache miss rate is 1 : 3316	Key_read_requests/ Key_reads 这里说明3316次读取请求中有1次丢失(也就是说1次读取磁盘)
Key buffer free ratio = 81 %	key_blocks_unused * key_cache_block_size / key_buffer_size * 100
Your key_buffer_size seems to be fine

QUERY CACHE	Query 缓存
Query cache is enabled	该项说明我们指定了query_cache_size 的值。如果query_cache_size=0的话这里给出的提示是： Query cache is supported but not enabled Perhaps you should set the query_cache_size
Current query_cache_size = 64 M	当前系统query_cache_size 值大小 [F]
Current query_cache_used = 1 M	query_cache_used =query_cache_size-qcache_free_memory
Current query_cache_limit = 128 M	变量 query_cache_limit 大小
Current Query cache Memory fill ratio = 1.79 %	query_cache_used/query_cache_size *100%
Current query_cache_min_res_unit = 4 K	show variables like ‘query_cache_min_res_unit’;
Your query_cache_size seems to be too high. Perhaps you can use these resources elsewhere	这项给出的结论是query_cache_size的值设置的有些过高。其比对标准是 “Query cache Memory fill ratio”的值如果小于<25%就会给出这个提示。可以将这些资源应用到其他的地方
MySQL won’t cache query results that are larger than query_cache_limit in size	MySQL不会将大于query_cache_limit的查询结果进行缓存
show status like ‘Qcache%’;Qcache_free_blocks 10 Qcache_free_memory 65891984 Qcache_hits 14437 Qcache_inserts 707 Qcache_lowmem_prunes 0 Qcache_not_cached 216 Qcache_queries_in_cache 540 Qcache_total_blocks 1191

SORT OPERATIONS	SORT 选项
Current sort_buffer_size = 6 M	show variables like ’sort_buffer%’;
Current read_rnd_buffer_size = 16 M	show variables like ‘read_rnd_buffer_size%’;
Sort buffer seems to be fine

JOINS	JOINS
Current join_buffer_size = 132.00 K	show variables like ‘join_buffer_size%’;join_buffer_size= join_buffer_size+4kb
You have had 6 queries where a join could not use an index properly	这里的6是通过 show status like ‘Select_full_join’; 获得的
You should enable “log-queries-not-using-indexes” Then look for non indexed joins in the slow query log. If you are unable to optimize your queries you may want to increase your join_buffer_size to accommodate larger joins in one pass.Note! This script will still suggest raising the join_buffer_size when ANY joins not using indexes are found.	你需要启用 “log-queries-not-using-indexes” 然后在慢查询日志中看是否有取消索引的joins语句。如果不优化查询语句的话，则需要增大join_buffer_size。

OPEN FILES LIMIT	文件打开数限制
Current open_files_limit = 1234 files	show variables like ‘open_files_limit%’;
The open_files_limit should typically be set to at least 2x-3xthat of table_cache if you have heavy MyISAM usage.	如果系统中有很多的MyISAM类型的表，则建议将open_files_limit 设置为2X~3X的table_open_cache show status like ‘Open_files’;open_files_ratio= open_files100/open_files_limit 如果open_files_ratio* 超过75% 则需要加大open_files_limit
Your open_files_limit value seems to be fine

TABLE CACHE	TABLE 缓存
Current table_open_cache = 512 tables	show variables like ‘table_open_cache’;
Current table_definition_cache = 256 tables	show variables like ‘ table_definition_cache ‘;
You have a total of 368 tables	SELECTCOUNT(*) FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE=’BASE TABLE’
You have 371 open tables.	show status like ‘Open_tables’;
The table_cache value seems to be fine	Open_tables /*table_open_cache100%** < 95%
You should probably increase your table_definition_cache value.	table_cache_hit_rate =open_tables*100/opened_tables

TEMP TABLES	临时表
Current max_heap_table_size = 16 M	show variables like ‘max_heap_table_size’;
Current tmp_table_size = 16 M	show variables like ‘tmp_table_size’;
Of 285 temp tables, 11% were created on disk	Created_tmp_tables=285created_tmp_disk_tables*100/ (created_tmp_tables+created_tmp_disk_tables)=11%
Created disk tmp tables ratio seems fine

TABLE SCANS	扫描表
Current read_buffer_size = 6 M	show variables like ‘read_buffer_size’;
Current table scan ratio = 9 : 1	read_rnd_next =show global status like ‘Handler_read_rnd_next’; com_select= show global status like ‘Com_select’; full_table_scans=read_rnd_next/com_select Current table scan ratio = full_table_scans : 1″ 如果表扫描率超过4000，说明进行了太多表扫描，很有可能索引没有建好，增加read_buffer_size值会有一些好处，但最好不要超过8MB。
read_buffer_size seems to be fine

TABLE LOCKING	TABLE LOCKING
Current Lock Wait ratio = 0 : 5617	show global status like’Table_locks_waited’; show global status like‘Questions’; 如果 Table_locks_waited=0 Current Lock Wait ratio = 0: Questions
Your table locking seems to be fine

转载自：http://blog.chinaunix.net/u3/117634/showart_2291084.html

MySQL：how to ignore errors loading a dump

admin — Mon, 09 Aug 2010 05:29:27 +0000

When we load a dump sql file using the following command:
mysql -uroot -pdbpassword test < /data/mysql.sql
the procedure will stop as it detects an error.
How to make procedure ignore the errors and continue anyway?
There are two kinds of methond can do that.

The first one:use "-f" option
mysql -uroot -pdbpassword -f test < /data/mysql.sql

The second one:access into mysql,and use the "source" command.
mysql -uroot -pdbpassword test
source /data/mysql.sql
exit

References:

http://forums.mysql.com/read.php?28,78316,78316

使用mysqldump線上備份InnoDB

admin — Fri, 05 Mar 2010 03:08:20 +0000

用 mysqldump 做線上即時備份，通常 InnoDB 的資料只有出現1~2筆，如果要儘可能把完整的資料匯出，可以加上 --single-transaction，備份前 mysqldump 會先執行 BEGIN ，取得 READ LOCK 後，便能確定資料在執行 mysqldump 的過程中不會受到其它連線對 InnoDB 存取的干擾，也能 Dump 出較完整的資料。(使用此參數需有 READ LOCK 權限)

mysqldump --single-transaction --all-databases > all_db.sql

注意:
1.表單較大時可以加上 --quick
2.MySQL Cluster 不支援 --single-transaction

然而使用 --single-transaction 時最好搭配 --flush-logs 及 --master-data 來維持 Binary Log 的完整性。(使用這二個參數皆需有 RELOAD 權限)

mysqldump --single-transaction --flush-logs --master-data --all-databases > all_db.sql

Binary Log 採用的是遞增備份，--flush-logs 便是把目前的 Binary Log 給 flush 出來 (若目前 MASTER_LOG_FILE 已經到 mysql-bin.000005，產生出來的檔案便是 mysql-bin.000006)，完成之後才進行 Dump 的作業。

而 --master-data (預設值為1) 則是在 Dump 出來的 SQL 語法中加入下面這一行，以記錄目前 Dump 的時間點。

CHANGE MASTER TO MASTER_LOG_FILE=mysql-bin.000006',MASTER_LOG_POS=4;

如果在未來執行匯入時 SQL 語法時， MySQL 便能很清楚的知道這次 Dump 出來的 SQL 在 Binary Log 中是屬於哪個位置。

註: 若不需理會 Binary Log 的位置時 (例如進行完整備份作業)，只要將 --master-data 設為 2 便會將 CHANGE MASTER 給註解起來純供參考用。

转载自：http://www.neo.com.tw/archives/1122

MySQL – Got a packet bigger than ‘max_allowed_packet’

admin — Mon, 25 Jan 2010 02:40:54 +0000

The default maximum allowed packget size is 1MB, so if you store some large binaries in your database you might get some problems. All you need to do is re-set the maximum size to a larger number.

Macintosh:trunk jennyfong$ mysql -uroot database_name < database_backup.sql

ERROR 1153 (08S01) at line 2365: Got a packet bigger than 'max_allowed_packet' bytes
Macintosh:trunk jennyfong$ mysql -uroot
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 25
Server version: 5.0.86 MySQL Community Server (GPL)

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> set global net_buffer_length=10000000;
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> set global max_allowed_packet=1000000000;
Query OK, 0 rows affected (0.00 sec)

mysql> exit
Bye
Macintosh:trunk jennyfong$ mysql -uroot database_name < database_backup.sql

show variables like 'max_allowed_packet';

install_xtrabackup-1.0_on_CentOS_5.4

admin — Wed, 06 Jan 2010 13:11:10 +0000

wget http://www.percona.com/mysql/xtrabackup/1.0/source/xtrabackup-1.0-56.rhel5.src.rpm
mkdir -p /usr/src/redhat/SOURCES/
rpm -i xtrabackup-1.0-56.rhel5.src.rpm
cd /usr/src/redhat/SOURCES/
tar xf xtrabackup-1.0.tar.gz
cd xtrabackup-1.0
./configure
make
cd innobase/xtrabackup/
make
make install

/usr/bin/innobackupex-1.5.1 --help

Got error 28 from storage engine 解决方法

admin — Tue, 08 Dec 2009 11:10:25 +0000

今天碰到数据库出错

Got error 28 from storage engine

查了一下，数据库文件所在的盘应该没事，应该是数据库用的临时目录空间不够

引用
磁盘临时空间不够导致。
解决办法：
清空/tmp目录，或者修改my.cnf中的tmpdir参数，指向具有足够空间目录

上面的说法应该比较清楚，还有一个类似的：

引用
mysql报以下错的解决方法

ERROR 1030 (HY000): Got error 28 from storage engine

出现此问题的原因：临时空间不够，无法执行此SQL语句

解决方法：将tmpdir指向一个硬盘空间很大的目录即可

原创内容如转载请注明：来自阿权的书房
本帖地址：http://www.aslibra.com/blog/read.php/794.htm