W dniu 30 sierpnia 2008 02:55 użytkownik Bartosz Świątek <[EMAIL PROTECTED]> napisał: > Ostrzegam, że phpMyAdmin 2.11.9-1 mimo, że z release 1 jest popsuty. > Przy wertykalnym klastrze baz, przy próbie połączenia do > któregokolwiek klastra, baza się wykłada. > Tego problemu nie ma przy wersji 2.11.8. > > Proszę o potwierdzenie. >
Aha, tak dołożę dump z /var/log/mysql/error.err 080830 2:51:44 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.1.26-rc-log' socket: '/var/lib/autko//mysqldb/mysql.sock' port: 3307 PLD Linux Distribution MySQL RPM 080830 2:53:17 - 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 = 338288 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x218b600 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... /usr/sbin/mysqld(print_stacktrace+0x1e) [0x6eb0ce] /usr/sbin/mysqld(handle_segfault+0x319) [0x5db5b9] /lib64/libpthread.so.0 [0x7fb2e1e19420] /usr/sbin/mysqld(get_field(st_mem_root*, Field*, String*)+0x56) [0x624706] /usr/sbin/mysqld(store_schema_proc(THD*, st_table*, st_table*, char const*, bool, char const*)+0x707) [0x6c62a7] /usr/sbin/mysqld(fill_schema_proc(THD*, TABLE_LIST*, Item*)+0x1e2) [0x6c6572] /usr/sbin/mysqld(get_schema_tables_result(JOIN*, enum_schema_table_state)+0x1f8) [0x6c00c8] /usr/sbin/mysqld(JOIN::exec()+0x428) [0x6441d8] /usr/sbin/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x16c) [0x6460ec] /usr/sbin/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned long)+0x169) [0x646a69] /usr/sbin/mysqld [0x5e19ff] /usr/sbin/mysqld(mysql_execute_command(THD*)+0x3714) [0x5e7284] /usr/sbin/mysqld(mysql_parse(THD*, char const*, unsigned int, char const**)+0x1b4) [0x5e90c4] /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0xb1e) [0x5e9ffe] /usr/sbin/mysqld(do_command(THD*)+0xca) [0x5ea8aa] /usr/sbin/mysqld(handle_one_connection+0x701) [0x5de161] /lib64/libpthread.so.0 [0x7fb2e1e11070] /lib64/libc.so.6(clone+0x6d) [0x7fb2e1605a3d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x21d4af0 = SELECT SPECIFIC_NAME,ROUTINE_NAME,ROUTINE_TYPE,DTD_IDENTIFIER FROM information_schema.ROUTINES WHERE ROUTINE_SCHEMA= 'ekoha' thd->thread_id=8 thd->killed=NOT_KILLED 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. I to się dzieje tylko w phpMyAdminie. Połączenia via mysql -u itd. są bezproblemowe i można sobie wszystko zmieniać i cudować. Na phpMyAdmin 2.11.8 też jest wszystko w najlepszym porządku. Być może 2.11.9 ma nowy "ficzer" o którym updater pakietu nie przeczytał? Tak tylko zgaduję bo śledztwa jeszcze nie prowadziłem. P.S. Hawk, w zaistniałej sytuacji proszę o wykasowanie phpMyAdmin-2.11.9-1 z FTPów Titanium póki sprawa się nie wyjaśni i nie będzie rozwiązania. _______________________________________________ pld-devel-pl mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-devel-pl
