GET 24/7 LIVE HELP NOW

Announcement

Announcement Module
Collapse
No announcement yet.

errors in the log file

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • errors in the log file

    Hi All,

    I am getting below errors from my Percona 5.6 64bit database. Could you please help me to understand those and take some corrective steps to our come those errors. If you would like have complete error log to analyze that also I can provide it.

    Your expert advice is highly appreciated.

    Thanks,
    Manjula


    2014-03-06 12:37:51 12496 [Note] InnoDB: Database was not shutdown normally!
    2014-03-06 12:37:51 12496 [Note] InnoDB: Starting crash recovery.
    2014-03-06 12:37:51 12496 [Note] InnoDB: Reading tablespace information from the .ibd files...
    2014-03-06 12:37:52 12496 [Note] InnoDB: Restoring possible half-written data pages
    2014-03-06 12:37:52 12496 [Note] InnoDB: from the doublewrite buffer...
    InnoDB: Doing recovery: scanned up to log sequence number 13298995712
    InnoDB: Doing recovery: scanned up to log sequence number 13304238592
    InnoDB: Doing recovery: scanned up to log sequence number 13304945179
    2014-03-06 12:37:53 12496 [Note] InnoDB: Starting an apply batch of log records to the database...
    InnoDB: Progress in percent: 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

    --------------------------------------------------------------------------------------------------------------------------------------------------------------------

    2014-03-01 15:19:54 6784 [ERROR] Incorrect definition of table mysql.proc: expected column 'comment' at position 15 to have type text, found type char(64).

    04:37:51 UTC - 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.
    Please help us make Percona Server better by reporting any
    bugs at http://bugs.percona.com/

    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Thread pointer: 0x9e3a670
    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 = 7f0cd655cd48 thread_stack 0x40000
    /usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8e0425]
    /usr/sbin/mysqld(handle_fatal_signal+0x4c4)[0x666b94]
    /lib64/libpthread.so.0[0x341c00f710]
    /usr/sbin/mysqld(_Z9get_fieldP11st_mem_rootP5Field+0x46)[0x77a6d6]
    /usr/sbin/mysqld[0x6812b4]
    /usr/sbin/mysqld(_Z11mysql_grantP3THDPKcR4ListI11st_lex_user Embb+0x551)[0x68e991]
    /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x4ac8)[0x6eac68]
    /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x60 8)[0x6eb6e8]
    /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3 THDPcj+0x146f)[0x6ecbbf]
    /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x16f)[0x6b9b0f]
    /usr/sbin/mysqld(handle_one_connection+0x47)[0x6b9be7]
    /usr/sbin/mysqld(pfs_spawn_thread+0x12a)[0x91d9ca]
    /lib64/libpthread.so.0[0x341c0079d1]
    /lib64/libc.so.6(clone+0x6d)[0x341bce8b6d]

    Trying to get some variables.
    Some pointers may be invalid and cause the dump to abort.
    Query (7f0c84009ae0): is an invalid pointer
    Connection ID (thread ID): 396936
    Status: NOT_KILLED

    -------------------------------------------------------------------------------------------------------------------------------

    2013-12-10 03:10:16 4224 [Note] Plugin 'FEDERATED' is disabled.
    2013-12-10 03:10:16 4224 [Note] InnoDB: The InnoDB memory heap is disabled
    2013-12-10 03:10:16 4224 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    2013-12-10 03:10:16 4224 [Note] InnoDB: Compressed tables use zlib 1.2.3
    2013-12-10 03:10:16 4224 [Note] InnoDB: Using Linux native AIO
    2013-12-10 03:10:16 4224 [Note] InnoDB: Using CPU crc32 instructions
    2013-12-10 03:10:16 4224 [Note] InnoDB: Initializing buffer pool, size = 4.0G
    2013-12-10 03:10:17 4224 [Note] InnoDB: Completed initialization of buffer pool
    2013-12-10 03:10:17 4224 [Note] InnoDB: Highest supported file format is Barracuda.
    2013-12-10 03:10:17 4224 [Note] InnoDB: 128 rollback segment(s) are active.
    2013-12-10 03:10:17 4224 [Note] InnoDB: Waiting for purge to start
    2013-12-10 03:10:17 4224 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.14-rel62.0 started; log sequence number 1626154
    2013-12-10 03:10:17 4224 [Note] RSA private key file not found: /var/lib/mysql//private_key.pem. Some authentication plugins will not work.
    2013-12-10 03:10:17 4224 [Note] RSA public key file not found: /var/lib/mysql//public_key.pem. Some authentication plugins will not work.




  • #2
    I would first need the idea on any changes you might have made on your Percona installation, which caused this issue for you.

    Comment


    • #3
      Hi,

      Have you recently upgrade Percona Server? This kind of error related to MySQL tables should be resolved by running mysql_upgrade. Run it and then start server.
      2014-03-01 15:19:54 6784 [ERROR] Incorrect definition of table mysql.proc: expected column 'comment' at position 15 to have type text, found type char(64).

      Comment

      Working...
      X