From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <44ACF487.70309@mail.ru> Date: Thu, 06 Jul 2006 16:31:19 +0500 From: Pavel Stoliarov User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923) X-Accept-Language: ru-ru, ru MIME-Version: 1.0 To: community@lists.altlinux.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit Subject: [Comm] =?koi8-r?b?8MHEwcXUIE15U1FM?= X-BeenThere: community@lists.altlinux.org X-Mailman-Version: 2.1.7 Precedence: list Reply-To: ALT Linux Community List-Id: ALT Linux Community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2006 11:31:35 -0000 Archived-At: List-Archive: List-Post: Система Compact 3.0 Иногда MySQL падает : Version: '5.0.22' socket: '/mysql.sock' port: 3306 ALT Linux MySQL RPM 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=8388600 read_buffer_size=131072 max_used_connections=53 max_connections=100 threads_connected=35 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0xb53a5290 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 0xb3d134b8 is invalid pointer thd->thread_id=2075 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. 2006-Jul-06 00:50:13 :: execution failed 2006-Jul-06 00:50:13 :: shutdown Советы , приведеные в вышеуказаной ссылке по тестированию и оптимизации базы итд, к успеху не привели. Может быть mysql 5.0.x еще сыровата ? Есть смысл откатиться на 4.1.x ? ---------- С уважением Столяров Павел