Korea FreeBSD Users Group News, Internal, Projects, Home
Software, Support, Documentation

Re: [KFUG] bsd 5.2.1 mysql



[ ³¯Â¥¼ø »öÀÎ ] [ ´ñ±Û¼ø »öÀÎ ] [ ÃÖ»óÀ§ »öÀÎ] [ °Ë»ö]

[ÀÌÀü ±Û] [´ÙÀ½ ±Û] [ÀÌÀü ´ñ±Û] [´ÙÀ½ ´ñ±Û]


4.9에서는 이런 문제가 없군요...
아 제온은 하이퍼쓰레이드 때문 5버전을 사용하고 싶었는데....
할수없이 4버전을 사용해야겠습니다.
 
----- Original Message -----
From: 강기호
Sent: Wednesday, May 19, 2004 8:46 PM
Subject: [KFUG] bsd 5.2.1에서 mysql을 사용할때

안녕하세요
프비에서 mysql을 사용해 볼려고 엄청삽질중입니다.
여러분의 의견과 조언을 바랍니다.
 
사양
제온 2.6 * 2
램 1기가 ( 향후 추가예정)
프비버전 5.2.1 ( smp 성능때문에 5.2.1을 선택하였습니다.)
mysql버전 4.0.18 ( 포트설치 기준이며, 포트를 업을 한 상태입니다.)
 
mysql 설치옵션
make WITH_CHARSET=latin1 WITH_XCHARSET=complex DB_DIR=/db WITH_LINUXTHREADS=yes BUILD_OPTIMIZED=yes BUILD_STATIC=yes install clean
( 이노디비를 사용하기위해 Make...파일에 with-innodb 를 했습니다.)
 
실후 my.cnf파일의 기본으로 하면 실행이 잘됩니다.
그러나 my.cnf파일에 이노디비관련 옵션에서 아래에  ######처리 한 부분의 주석을 풀면 오류 메세지가 생기면서
실행이 되지 않습니다. 또한 mysql데몬이 2개정도 나타나는데 재부팅을 하기전에 죽지 않는 현상이 생깁니다.( mysql이 실행 되지 않은 상태)
 
my.cnf 의 참고 내용
# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /db/
innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend
innodb_log_group_home_dir = /db/
innodb_log_arch_dir = /db/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
###################################################
innodb_buffer_pool_size = 256M
innodb_additional_mem_pool_size = 20M
###################################################
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 100M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50
mysql의 오류내용
#############################################################################################
040518 01:59:11  mysqld started
InnoDB: The first specified data file /db/ibdata1 did not exist:
InnoDB: a new database to be created!
040518  1:59:11  InnoDB: Setting file /db/ibdata1 size to 2000 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100 200 300 400 500 600 700 800 900 1000 1100 1200 1300 1400 1500 1600 1700 1800 1900 2000
040518  1:59:52  InnoDB: Data file /db/ibdata2 did not exist: new to be created
040518  1:59:52  InnoDB: Setting file /db/ibdata2 size to 10 MB
InnoDB: Database physically writes the file full: wait...
040518  1:59:52  InnoDB: Log file /db/ib_logfile0 did not exist: new to be created
InnoDB: Setting log file /db/ib_logfile0 size to 100 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
040518  1:59:54  InnoDB: Log file /db/ib_logfile1 did not exist: new to be created
InnoDB: Setting log file /db/ib_logfile1 size to 100 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
040518  1:59:57  InnoDB: Started
mysqld in malloc(): error: allocation failed
mysqld got signal 6;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
 
key_buffer_size=402653184
read_buffer_size=2093056
max_used_connections=0
max_connections=384
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1964541 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
######################################################################
 
위 my.cnf파일에서 ########### 부분의 2가지 옵션만 주석으로 할경우 메세지
040518 02:03:20  mysqld started
040518  2:03:20  InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 37082
InnoDB: Doing recovery: scanned up to log sequence number 0 43892
040518  2:03:21  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
InnoDB: Apply batch completed
040518  2:03:21  InnoDB: Flushing modified pages from the buffer pool...
040518  2:03:21  InnoDB: Started
/usr/local/libexec/mysqld: ready for connections.
Version: '4.0.18'  socket: '/tmp/mysql.sock'  port: 3306
040518 09:09:47  mysqld started
040518  9:09:47  InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 45879
InnoDB: Doing recovery: scanned up to log sequence number 0 45879
040518  9:09:47  InnoDB: Flushing modified pages from the buffer pool...
040518  9:09:47  InnoDB: Started
/usr/local/libexec/mysqld: ready for connections.
Version: '4.0.18'  socket: '/tmp/mysql.sock'  port: 3306
 


_______________________________________________
한국 FreeBSD 사용자 그룹(KFUG) questions 메일링 리스트
questions at kr.FreeBSD.org
http://www.kr.FreeBSD.org/mailman/listinfo/questions
_______________________________________________
한국 FreeBSD 사용자 그룹(KFUG) questions 메일링 리스트
questions at kr.FreeBSD.org
http://www.kr.FreeBSD.org/mailman/listinfo/questions

[ ³¯Â¥¼ø »öÀÎ ] [ ´ñ±Û¼ø »öÀÎ ] [ ÃÖ»óÀ§ »öÀÎ] [ °Ë»ö]

Copyright © 1998-2005 Korea FreeBSD Users Group.
All rights reserved. webmaster at kr.FreeBSD.org
$Date: 2004/05/21 22:09:42 $
Powered by FreeBSD