Rafał Cygnarowski pisze: > Witam! > > Postawiłem wczoraj serwer dla GLPI (*glpi*-project.org > <http://project.org>). Baza tegoż na mysql-u. Instalacja świeża z Th. Z > poziomu GLPI jestem w stanie wysypać mysql-a w następujący sposób: > > 1. Po zalogowaniu wybieram Spis -> Oprogramowanie > 2. Wybieram Dodaj (plusik) > 3. Wybieram "Pusty szablon" > 4. W nazwa wpisuję "nazwa" i klikam Dodaj > 5. Wybieram Spis -> Oprogramowanie > > I w tym momencie już jestem bez mysql-a... Na ekranie komunikat: "MySQL > server has gone away", a w logach: > > --- start log-a --- > 080327 10:06:22 - 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=2 > max_threads=151 > threads_connected=1 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = > 337677 K > bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > thd: 0x8d2bc30 > 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... > Cannot determine thread, fp=0xffffffff, backtrace may not be correct. > Bogus stack limit or frame pointer, fp=0xffffffff, > stack_bottom=0xb4e90000, thread_stack=196608, aborting backtrace. > Trying to get some variables. > Some pointers may be invalid and cause the dump to abort... > thd->query at 0x8d7fb48 = SELECT glpi_software.name AS ITEM_0, > glpi_software.ID AS ITEM_0_2, glpi_dropdown_manufacturer.name AS > ITEM_1, GROUP_CONCAT( DISTINCT glpi_licenses.version SEPARATOR '$$$$') > AS ITEM_2, glpi_dropdown_os.name AS ITEM_3, glpi_software.ID AS ID FROM > glpi_software LEFT JOIN glpi_dropdown_manufacturer ON > (glpi_software.FK_glpi_enterprise = glpi_dropdown_manufacturer.ID) LEFT > JOIN glpi_licenses ON (glpi_software.ID = glpi_licenses.sID) LEFT JOIN > glpi_dropdown_os ON (glpi_software.platform = glpi_dropdown_os.ID) > WHERE glpi_software.deleted='0' AND glpi_software.is_template='0' > AND ( 1 ) GROUP BY glpi_software.ID ORDER BY glpi_software.name ASC > LIMIT 0, 20 thd->thread_id=19 > The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains > information that should help you find out what is causing the crash. > --- koniec log-a --- > > # rpm -q mysql > mysql-5.1.23-2.i686 > > Rzecz jest w 100% powtarzalna. Bardzo byłbym rad, gdyby ktoś mógł > potwierdzić, że u niego też się wysypuje oraz informację od tych, u > których się tak nie dzieje (abym mógł zbudować sobie inną wersję > mysql-a, na którem takie problem nie występuje). > mysql-5.0.51a-4.i686
Działa bez problemów. -- Paweł _______________________________________________ pld-users-pl mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-users-pl
