- Beranda
- Programmer Forum
Mysql Sering crash/Shutdown Sendiri
...
TS
sanseru
Mysql Sering crash/Shutdown Sendiri
Code:
Misi gan di sini mungkin ada yang bisa memecahkan pemasalahan ane, di sini ane memiliki masalah dimana database mysql ane sering down terus sehari bisa lebih dari 5 kali.ini hasil lognya
Spoiler for log:
Timestamp, Thread, Type, Details
2018-02-26T06:11:16, 0, ERROR, InnoDB: Operating system error number 995 in a file operation.
2018-02-26T06:11:16, 0, ERROR, InnoDB: The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
, , , 2018-02-26 13:11:16 0x1f94 InnoDB: Assertion failure in thread 8084 in file fil0fil.cc line 5789
, , , InnoDB: Failing assertion: err == DB_SUCCESS
, , , InnoDB: We intentionally generate a memory trap.
, , , InnoDB: Submit a detailed bug report to [url]http://bugs.mysql.com.[/url]
, , , InnoDB: If you get repeated assertion failures or crashes, even
, , , InnoDB: immediately after the mysqld startup, there may be
, , , InnoDB: corruption in the InnoDB tablespace. Please refer to
, , , InnoDB: http://dev.mysql.com/doc/refman/5.7/...-recovery.html
, , , InnoDB: about forcing recovery.
, , , 06:11:16 UTC - mysqld got exception 0x80000003 ;
, , , 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.
, , , Attempting to collect some information that could help diagnose the problem.
, , , As this is a crash and something is definitely wrong, the information
, , , collection process might fail.
, , , key_buffer_size=8388608
, , , read_buffer_size=65536
, , , max_used_connections=21
, , , max_threads=151
, , , thread_count=5
, , , connection_count=5
, , , It is possible that mysqld could use up to
, , , key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58345 K bytes of memory
, , , Hope that's ok; if not, decrease some variables in the equation.
, , , Thread pointer: 0x0
, , , 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...
, , , 7f68cb05ea2 mysqld.exe!my_errno()
, , , 7f68cea9919 mysqld.exe!my_wildcmp_mb()
, , , 7f68cea8810 mysqld.exe!my_wildcmp_mb()
, , , 7f68cc05ac8 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
, , , 7f68cc2c49a mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
, , , 7f68cbc4e94 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
, , , 7fefff81842 KERNEL32.DLL!BaseThreadInitThunk()
, , , 7ff012ac3f1 ntdll.dll!RtlUserThreadStart()
, , , The manual page at http://dev.mysql.com/doc/mysql/en/crashing.htmlcontains
, , , information that should help you find out what is causing the crash.
2018-02-26T06:11:28, 0, Note, C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe (mysqld 5.7.11-log) starting as process 9328 ...
2018-02-26T06:11:28, 0, Note, InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-02-26T06:11:28, 0, Note, InnoDB: Uses event mutexes
2018-02-26T06:11:28, 0, Note, InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-02-26T06:11:28, 0, Note, InnoDB: Compressed tables use zlib 1.2.3
2018-02-26T06:11:28, 0, Note, InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB
2018-02-26T06:11:28, 0, Note, InnoDB: Number of pools: 1
2018-02-26T06:11:28, 0, Note, InnoDB: Not using CPU crc32 instructions
2018-02-26T06:11:28, 0, Note, InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-02-26T06:11:28, 0, Note, InnoDB: Completed initialization of buffer pool
2018-02-26T06:11:28, 0, Note, InnoDB: Highest supported file format is Barracuda.
2018-02-26T06:11:28, 0, Note, InnoDB: Log scan progressed past the checkpoint lsn 100848333099
2018-02-26T06:11:28, 0, Note, InnoDB: Doing recovery: scanned up to log sequence number 100848336312
2018-02-26T06:11:28, 0, Note, InnoDB: Doing recovery: scanned up to log sequence number 100848336312
2018-02-26T06:11:28, 0, Note, InnoDB: Database was not shutdown normally!
2018-02-26T06:11:28, 0, Note, InnoDB: Starting crash recovery.
2018-02-26T06:11:28, 0, Note, InnoDB: Starting an apply batch of log records to the database...
, , , InnoDB: Progress in percent: 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 8 [truncated, 315 bytes total]
2018-02-26T06:11:29, 0, Note, InnoDB: Apply batch completed
2018-02-26T06:11:30, 0, Note, InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-02-26T06:11:30, 0, Note, InnoDB: Creating shared tablespace for temporary tables
2018-02-26T06:11:30, 0, Note, InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-02-26T06:11:31, 0, Note, InnoDB: File '.\ibtmp1' size is now 12 MB.
2018-02-26T06:11:31, 0, Note, InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2018-02-26T06:11:31, 0, Note, InnoDB: 32 non-redo rollback segment(s) are active.
2018-02-26T06:11:31, 0, Note, InnoDB: Waiting for purge to start
2018-02-26T06:11:31, 0, Note, InnoDB: 5.7.11 started; log sequence number 100848336312
2018-02-26T06:11:31, 0, Note, InnoDB: Loading buffer pool(s) from C:\ProgramData\MySQL\MySQL Server 5.7\Data\ib_buffer_pool
2018-02-26T06:11:31, 0, Note, Plugin 'FEDERATED' is disabled.
2018-02-26T06:11:31, 0, Warning, Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2018-02-26T06:11:31, 0, Note, Server hostname (bind-address): '*'; port: 3306
2018-02-26T06:11:31, 0, Note, IPv6 is available.
2018-02-26T06:11:31, 0, Note, - '::' resolves to '::';
2018-02-26T06:11:31, 0, Note, Server socket created on IP: '::'.
2018-02-26T06:11:32, 0, Note, Event Scheduler: Loaded 0 events
2018-02-26T06:11:32, 0, Note, C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe: ready for connections.
, , , Version: '5.7.11-log' socket: '' port: 3306 MySQL Community Server (GPL)
2018-02-26T06:11:35, 0, Note, InnoDB: Buffer pool(s) load completed at 180226 13:11:35
2018-02-26T06:11:16, 0, ERROR, InnoDB: Operating system error number 995 in a file operation.
2018-02-26T06:11:16, 0, ERROR, InnoDB: The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
, , , 2018-02-26 13:11:16 0x1f94 InnoDB: Assertion failure in thread 8084 in file fil0fil.cc line 5789
, , , InnoDB: Failing assertion: err == DB_SUCCESS
, , , InnoDB: We intentionally generate a memory trap.
, , , InnoDB: Submit a detailed bug report to [url]http://bugs.mysql.com.[/url]
, , , InnoDB: If you get repeated assertion failures or crashes, even
, , , InnoDB: immediately after the mysqld startup, there may be
, , , InnoDB: corruption in the InnoDB tablespace. Please refer to
, , , InnoDB: http://dev.mysql.com/doc/refman/5.7/...-recovery.html
, , , InnoDB: about forcing recovery.
, , , 06:11:16 UTC - mysqld got exception 0x80000003 ;
, , , 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.
, , , Attempting to collect some information that could help diagnose the problem.
, , , As this is a crash and something is definitely wrong, the information
, , , collection process might fail.
, , , key_buffer_size=8388608
, , , read_buffer_size=65536
, , , max_used_connections=21
, , , max_threads=151
, , , thread_count=5
, , , connection_count=5
, , , It is possible that mysqld could use up to
, , , key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58345 K bytes of memory
, , , Hope that's ok; if not, decrease some variables in the equation.
, , , Thread pointer: 0x0
, , , 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...
, , , 7f68cb05ea2 mysqld.exe!my_errno()
, , , 7f68cea9919 mysqld.exe!my_wildcmp_mb()
, , , 7f68cea8810 mysqld.exe!my_wildcmp_mb()
, , , 7f68cc05ac8 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
, , , 7f68cc2c49a mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
, , , 7f68cbc4e94 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
, , , 7fefff81842 KERNEL32.DLL!BaseThreadInitThunk()
, , , 7ff012ac3f1 ntdll.dll!RtlUserThreadStart()
, , , The manual page at http://dev.mysql.com/doc/mysql/en/crashing.htmlcontains
, , , information that should help you find out what is causing the crash.
2018-02-26T06:11:28, 0, Note, C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe (mysqld 5.7.11-log) starting as process 9328 ...
2018-02-26T06:11:28, 0, Note, InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-02-26T06:11:28, 0, Note, InnoDB: Uses event mutexes
2018-02-26T06:11:28, 0, Note, InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-02-26T06:11:28, 0, Note, InnoDB: Compressed tables use zlib 1.2.3
2018-02-26T06:11:28, 0, Note, InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB
2018-02-26T06:11:28, 0, Note, InnoDB: Number of pools: 1
2018-02-26T06:11:28, 0, Note, InnoDB: Not using CPU crc32 instructions
2018-02-26T06:11:28, 0, Note, InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-02-26T06:11:28, 0, Note, InnoDB: Completed initialization of buffer pool
2018-02-26T06:11:28, 0, Note, InnoDB: Highest supported file format is Barracuda.
2018-02-26T06:11:28, 0, Note, InnoDB: Log scan progressed past the checkpoint lsn 100848333099
2018-02-26T06:11:28, 0, Note, InnoDB: Doing recovery: scanned up to log sequence number 100848336312
2018-02-26T06:11:28, 0, Note, InnoDB: Doing recovery: scanned up to log sequence number 100848336312
2018-02-26T06:11:28, 0, Note, InnoDB: Database was not shutdown normally!
2018-02-26T06:11:28, 0, Note, InnoDB: Starting crash recovery.
2018-02-26T06:11:28, 0, Note, InnoDB: Starting an apply batch of log records to the database...
, , , InnoDB: Progress in percent: 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 8 [truncated, 315 bytes total]
2018-02-26T06:11:29, 0, Note, InnoDB: Apply batch completed
2018-02-26T06:11:30, 0, Note, InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-02-26T06:11:30, 0, Note, InnoDB: Creating shared tablespace for temporary tables
2018-02-26T06:11:30, 0, Note, InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-02-26T06:11:31, 0, Note, InnoDB: File '.\ibtmp1' size is now 12 MB.
2018-02-26T06:11:31, 0, Note, InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2018-02-26T06:11:31, 0, Note, InnoDB: 32 non-redo rollback segment(s) are active.
2018-02-26T06:11:31, 0, Note, InnoDB: Waiting for purge to start
2018-02-26T06:11:31, 0, Note, InnoDB: 5.7.11 started; log sequence number 100848336312
2018-02-26T06:11:31, 0, Note, InnoDB: Loading buffer pool(s) from C:\ProgramData\MySQL\MySQL Server 5.7\Data\ib_buffer_pool
2018-02-26T06:11:31, 0, Note, Plugin 'FEDERATED' is disabled.
2018-02-26T06:11:31, 0, Warning, Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2018-02-26T06:11:31, 0, Note, Server hostname (bind-address): '*'; port: 3306
2018-02-26T06:11:31, 0, Note, IPv6 is available.
2018-02-26T06:11:31, 0, Note, - '::' resolves to '::';
2018-02-26T06:11:31, 0, Note, Server socket created on IP: '::'.
2018-02-26T06:11:32, 0, Note, Event Scheduler: Loaded 0 events
2018-02-26T06:11:32, 0, Note, C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe: ready for connections.
, , , Version: '5.7.11-log' socket: '' port: 3306 MySQL Community Server (GPL)
2018-02-26T06:11:35, 0, Note, InnoDB: Buffer pool(s) load completed at 180226 13:11:35
Mungkin disini ada yang bisa memcahkan masalah saya? saya ucapkan terimakasih
saya sudah coba menghapus beberapa file sesuai yang ada internet bertebaran tetapi tidak memecahkan masalahnya.
Diubah oleh sanseru 26-02-2018 06:27
nona212 memberi reputasi
1
1.8K
Kutip
3
Balasan
Guest
Tulis komentar menarik atau mention replykgpt untuk ngobrol seru
Mari bergabung, dapatkan informasi dan teman baru!
Programmer Forum
20.2KThread•4.3KAnggota
Terlama
Guest
Tulis komentar menarik atau mention replykgpt untuk ngobrol seru