Jump to content
  • Sign Up

Ganok

Members
 View Profile  See their activity

  • Content Count

    1

  • Joined

  • Last visited

Posts posted by Ganok

  1. Posted

    i have an error when i try to start openserver (red flag -> green)

     

    view shows some log like below but i don't knows why...

     

    2019-11-17 18:06:55 0 [Note] w:\modules\database\MySQL-5.6\bin\mysqld.exe (mysqld 5.6.38-log) starting as process 9964 ...
    2019-11-17 18:06:55 9964 [Note] Plugin 'FEDERATED' is disabled.
    2019-11-17 18:06:55 9964 [Note] InnoDB: Using atomics to ref count buffer pool pages
    2019-11-17 18:06:55 9964 [Note] InnoDB: The InnoDB memory heap is disabled
    2019-11-17 18:06:55 9964 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
    2019-11-17 18:06:55 9964 [Note] InnoDB: Memory barrier is not used
    2019-11-17 18:06:55 9964 [Note] InnoDB: Compressed tables use zlib 1.2.3
    2019-11-17 18:06:55 9964 [Note] InnoDB: Not using CPU crc32 instructions
    2019-11-17 18:06:55 9964 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    2019-11-17 18:06:55 9964 [Note] InnoDB: Completed initialization of buffer pool
    2019-11-17 18:06:55 9964 [Note] InnoDB: Highest supported file format is Barracuda.
    2019-11-17 18:06:55 9964 [Note] InnoDB: 128 rollback segment(s) are active.
    2019-11-17 18:06:55 9964 [Note] InnoDB: Waiting for purge to start
    2019-11-17 18:06:55 9964 [Note] InnoDB: 5.6.38 started; log sequence number 1796323
    2019-11-17 18:06:55 9964 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
    2019-11-17 18:06:55 9964 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
    2019-11-17 18:06:55 9964 [Note] Server socket created on IP: '127.0.0.1'.
    2019-11-17 18:06:55 9964 [Warning] Can't open and lock time zone table: Incorrect file format 'time_zone_transition' trying to live without them
    InnoDB: Error: the size of single-table tablespace file .\mysql\slave_master_info.ibd
    InnoDB: is only 0, should be at least 65536!
    2019-11-17 18:06:55 73c  InnoDB: Assertion failure in thread 1852 in file fil0fil.cc line 769
    InnoDB: Failing assertion: 0
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
    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.6/en/forcing-innodb-recovery.html
    InnoDB: about forcing recovery.
    09:06:55 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.
    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=26214400
    read_buffer_size=2097152
    max_used_connections=0
    max_threads=30
    thread_count=0
    connection_count=0
    It is possible that mysqld could use up to 
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 118015 K  bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.

    Thread pointer: 0x10849ad8
    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...
    1462e30    mysqld.exe!my_thread_name()
    773fd7c5    MSVCR100.dll!abort()
    14f3f62    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    14f81b6    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    15caee5    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    15cb75d    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    1527af7    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    15852b4    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    1585381    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    1585876    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    152cdcf    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    152cefb    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    1532c7e    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    148afee    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    12105c6    mysqld.exe!?ha_open@handler@@QAEHPAUTABLE@@PBDHH@Z()
    1301354    mysqld.exe!?open_table_from_share@@YAHPAVTHD@@PAUTABLE_SHARE@@PBDIIIPAUTABLE@@_N@Z()
    12591e7    mysqld.exe!?open_table@@YA_NPAVTHD@@PAUTABLE_LIST@@PAVOpen_table_context@@@Z()
    1259921    mysqld.exe!?recover_from_failed_open@Open_table_context@@QAE_NXZ()
    125a994    mysqld.exe!?open_tables@@YA_NPAVTHD@@PAPAUTABLE_LIST@@PAIIPAVPrelocking_strategy@@@Z()
    125abc4    mysqld.exe!?open_and_lock_tables@@YA_NPAVTHD@@PAUTABLE_LIST@@_NIPAVPrelocking_strategy@@@Z()
    125ad79    mysqld.exe!?open_n_lock_single_table@@YAPAUTABLE@@PAVTHD@@PAUTABLE_LIST@@W4thr_lock_type@@IPAVPrelocking_strategy@@@Z()
    145a08c    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
    1457e52    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
    1451d44    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
    1451e14    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
    1452059    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
    1452672    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
    144dcf4    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
    12030bd    mysqld.exe!?win_main@@YAHHPAPAD@Z()
    1203377    mysqld.exe!?mysql_service@@YAHPAX@Z()
    16a2eea    mysqld.exe!my_mb_ctype_mb()
    7570343d    kernel32.dll!BaseThreadInitThunk()
    771c9812    ntdll.dll!RtlInitializeExceptionChain()
    771c97e5    ntdll.dll!RtlInitializeExceptionChain()

    Trying to get some variables.
    Some pointers may be invalid and cause the dump to abort.
    Query (0): Connection ID (thread ID): 0
    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.

     

     

     

     

    anyone knows how to fix this?

     

    thank you!

  2. Posted

    i have an error when i try to start openserver (red flag -> green)

     

    view shows some log like below but i don't knows why...

     

    2019-11-17 18:06:55 0 [Note] w:\modules\database\MySQL-5.6\bin\mysqld.exe (mysqld 5.6.38-log) starting as process 9964 ...
    2019-11-17 18:06:55 9964 [Note] Plugin 'FEDERATED' is disabled.
    2019-11-17 18:06:55 9964 [Note] InnoDB: Using atomics to ref count buffer pool pages
    2019-11-17 18:06:55 9964 [Note] InnoDB: The InnoDB memory heap is disabled
    2019-11-17 18:06:55 9964 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
    2019-11-17 18:06:55 9964 [Note] InnoDB: Memory barrier is not used
    2019-11-17 18:06:55 9964 [Note] InnoDB: Compressed tables use zlib 1.2.3
    2019-11-17 18:06:55 9964 [Note] InnoDB: Not using CPU crc32 instructions
    2019-11-17 18:06:55 9964 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    2019-11-17 18:06:55 9964 [Note] InnoDB: Completed initialization of buffer pool
    2019-11-17 18:06:55 9964 [Note] InnoDB: Highest supported file format is Barracuda.
    2019-11-17 18:06:55 9964 [Note] InnoDB: 128 rollback segment(s) are active.
    2019-11-17 18:06:55 9964 [Note] InnoDB: Waiting for purge to start
    2019-11-17 18:06:55 9964 [Note] InnoDB: 5.6.38 started; log sequence number 1796323
    2019-11-17 18:06:55 9964 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
    2019-11-17 18:06:55 9964 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
    2019-11-17 18:06:55 9964 [Note] Server socket created on IP: '127.0.0.1'.
    2019-11-17 18:06:55 9964 [Warning] Can't open and lock time zone table: Incorrect file format 'time_zone_transition' trying to live without them
    InnoDB: Error: the size of single-table tablespace file .\mysql\slave_master_info.ibd
    InnoDB: is only 0, should be at least 65536!
    2019-11-17 18:06:55 73c  InnoDB: Assertion failure in thread 1852 in file fil0fil.cc line 769
    InnoDB: Failing assertion: 0
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
    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.6/en/forcing-innodb-recovery.html
    InnoDB: about forcing recovery.
    09:06:55 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.
    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=26214400
    read_buffer_size=2097152
    max_used_connections=0
    max_threads=30
    thread_count=0
    connection_count=0
    It is possible that mysqld could use up to 
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 118015 K  bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.

    Thread pointer: 0x10849ad8
    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...
    1462e30    mysqld.exe!my_thread_name()
    773fd7c5    MSVCR100.dll!abort()
    14f3f62    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    14f81b6    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    15caee5    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    15cb75d    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    1527af7    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    15852b4    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    1585381    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    1585876    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    152cdcf    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    152cefb    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    1532c7e    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    148afee    mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
    12105c6    mysqld.exe!?ha_open@handler@@QAEHPAUTABLE@@PBDHH@Z()
    1301354    mysqld.exe!?open_table_from_share@@YAHPAVTHD@@PAUTABLE_SHARE@@PBDIIIPAUTABLE@@_N@Z()
    12591e7    mysqld.exe!?open_table@@YA_NPAVTHD@@PAUTABLE_LIST@@PAVOpen_table_context@@@Z()
    1259921    mysqld.exe!?recover_from_failed_open@Open_table_context@@QAE_NXZ()
    125a994    mysqld.exe!?open_tables@@YA_NPAVTHD@@PAPAUTABLE_LIST@@PAIIPAVPrelocking_strategy@@@Z()
    125abc4    mysqld.exe!?open_and_lock_tables@@YA_NPAVTHD@@PAUTABLE_LIST@@_NIPAVPrelocking_strategy@@@Z()
    125ad79    mysqld.exe!?open_n_lock_single_table@@YAPAUTABLE@@PAVTHD@@PAUTABLE_LIST@@W4thr_lock_type@@IPAVPrelocking_strategy@@@Z()
    145a08c    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
    1457e52    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
    1451d44    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
    1451e14    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
    1452059    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
    1452672    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
    144dcf4    mysqld.exe!?opt_sum_query@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@PAVItem@@@Z()
    12030bd    mysqld.exe!?win_main@@YAHHPAPAD@Z()
    1203377    mysqld.exe!?mysql_service@@YAHPAX@Z()
    16a2eea    mysqld.exe!my_mb_ctype_mb()
    7570343d    kernel32.dll!BaseThreadInitThunk()
    771c9812    ntdll.dll!RtlInitializeExceptionChain()
    771c97e5    ntdll.dll!RtlInitializeExceptionChain()

    Trying to get some variables.
    Some pointers may be invalid and cause the dump to abort.
    Query (0): Connection ID (thread ID): 0
    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.

     

     

     

     

    anyone knows how to fix this?

     

    thank you!

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept