mysqld 질문입니다
서버가 전원이 나갔다가 다시 들어온 이후로 계속 데몬 수행이 안되는군요 이것저것 검색해서 나오는거 해보았지만 잘 안되는군요
데이터베이스는 잘 안써서 모르는지라.. ㅠㅠ
혹 도움 주실수 있으신분...
데비안 안정버전 2.4.24에 mysql은 3.23.49 입니다...
huro:/usr/mysql/bin# ./mysqld_safe
Starting mysqld daemon with databases from /usr/mysql/database
051107 01:45:01 mysqld endedhuro:/usr/mysql/bin#
051107 01:31:45 mysqld started
mysqld got signal 11;
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=268435456
read_buffer_size=1044480
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 466543
K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.thd=0x845cae8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
frame pointer (ebp) is NULL, did you compile with
-fomit-frame-pointer? Aborting backtrace!
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x61642f6c is invalid pointer
thd->thread_id=11
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
051107 01:31:45 mysqld ended
보통은 권한설정 문제로 알고있습니다.어떤유저가 mysqld를 실행
보통은 권한설정 문제로 알고있습니다.
어떤유저가 mysqld를 실행하는지 보시고 chown 명령어 쓰셔서 데이타 베이스 폴더 권한설정도 다시 해보시길...
페도라 만세
댓글 달기