[ maroon984 @ 17.02.2016. 13:39 ] @
Pozdrav svima. U prethodnih mjesec dana, desilo mi se da mi mysqld par puta prsne. Posljednji put se to desilo juce, i u logu stoji: Code: 11:45:00 UTC - mysqld got signal 8 ; 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=314572800 read_buffer_size=2097152 max_used_connections=104 max_threads=300 thread_count=100 connection_count=99 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1539424 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x469ea900 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... stack_bottom = 7fd712816e98 thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7c5af5] /usr/sbin/mysqld(handle_fatal_signal+0x403)[0x68e713] /lib64/libpthread.so.0(+0xfd00)[0x7fe1a5305d00] /usr/sbin/mysqld(_ZN12ha_partition21min_rows_for_estimateEv+0x61)[0x957511] /usr/sbin/mysqld[0x75204f] /usr/sbin/mysqld[0x75276e] /usr/sbin/mysqld[0x7529ec] /usr/sbin/mysqld(_ZN10SQL_SELECT17test_quick_selectEP3THD6BitmapILj64EEyyb+0x11ac)[0x75ba4c] /usr/sbin/mysqld[0x5c8764] /usr/sbin/mysqld(_ZN4JOIN8optimizeEv+0x581)[0x5c9931] /usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x171)[0x5cd591] /usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x179)[0x5d33b9] /usr/sbin/mysqld[0x59003d] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x2208)[0x595738] /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x18a)[0x597eea] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1339)[0x599ab9] /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x184)[0x632494] /usr/sbin/mysqld(handle_one_connection+0x54)[0x632504] /lib64/libpthread.so.0(+0x7f05)[0x7fe1a52fdf05] /lib64/libc.so.6(clone+0x6d)[0x7fe1a45a110d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7fd6144fde10): is an invalid pointer Connection ID (thread ID): 823 Status: 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. 160216 12:45:00 mysqld_safe Number of processes running now: 0 160216 12:45:00 mysqld_safe mysqld restarted 160216 12:45:00 [Note] Plugin 'FEDERATED' is disabled. 160216 12:45:00 InnoDB: The InnoDB memory heap is disabled 160216 12:45:00 InnoDB: Mutexes and rw_locks use GCC atomic builtins 160216 12:45:00 InnoDB: Compressed tables use zlib 1.2.3 160216 12:45:00 InnoDB: Using Linux native AIO 160216 12:45:00 InnoDB: Initializing buffer pool, size = 40.0G 160216 12:45:02 InnoDB: Completed initialization of buffer pool 160216 12:45:02 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 4911607582808 160216 12:45:02 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 4911612825600 InnoDB: Doing recovery: scanned up to log sequence number 4911618068480 InnoDB: Doing recovery: scanned up to log sequence number 4911623311360 InnoDB: Doing recovery: scanned up to log sequence number 4911628554240 InnoDB: Doing recovery: scanned up to log sequence number 4911633797120 InnoDB: Doing recovery: scanned up to log sequence number 4911639040000 InnoDB: Doing recovery: scanned up to log sequence number 4911644282880 InnoDB: Doing recovery: scanned up to log sequence number 4911649525760 InnoDB: Doing recovery: scanned up to log sequence number 4911654768640 InnoDB: Doing recovery: scanned up to log sequence number 4911660011520 InnoDB: Doing recovery: scanned up to log sequence number 4911665254400 InnoDB: Doing recovery: scanned up to log sequence number 4911670497280 InnoDB: Doing recovery: scanned up to log sequence number 4911675740160 InnoDB: Doing recovery: scanned up to log sequence number 4911680983040 InnoDB: Doing recovery: scanned up to log sequence number 4911686225920 InnoDB: Doing recovery: scanned up to log sequence number 4911691468800 InnoDB: Doing recovery: scanned up to log sequence number 4911694829397 160216 12:45:05 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 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 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 1980781, file name /var/MYSQL_BINLOG/mysql-bin.004471 160216 12:45:09 InnoDB: Waiting for the background threads to start 160216 12:45:10 InnoDB: 1.1.8 started; log sequence number 4911694829397 160216 12:45:10 [Note] Recovering after a crash using /var/MYSQL_BINLOG/mysql-bin 160216 12:45:10 [Note] Starting crash recovery... 160216 12:45:10 [Note] Crash recovery finished. 160216 12:45:10 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 160216 12:45:10 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 160216 12:45:10 [Note] Server socket created on IP: '0.0.0.0'. 160216 12:45:10 [Warning] 'proxies_priv' entry '@ root@stw-db-bl02' ignored in --skip-name-resolve mode. 160216 12:45:10 [Note] Event Scheduler: Loaded 14 events 160216 12:45:10 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.24-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) 160216 12:45:10 [Note] Event Scheduler: scheduler thread started with id 1 Mysql server je verzija 5.5.24, OS je OpenSUSE 12.1. Server ima 64G RAM-a, i podeseno je swappiness=0 Pratio sam zauzece RAM-a, par sati prije restarta preko free -m free je bilo oko 300M, ali je cached bilo oko 10G Inace, JAVA Aplikacije vrse upis u DB, a php iscitava. Ima li iko ideju zbog cega bi ovo moglo da se desava? Kontao sam da je potrosen sav RAM-a, ali kazem cached je bilo 10G. |