Results 1 to 3 of 3
  1. #1
    Join Date
    May 2012
    Location
    Chennai
    Posts
    45

    Question Unanswered: mysql error and sometimes crash the table

    Hi All,

    We are getting the slowness issue on Mysql. Last three days we have repaired the table too. That table's rows contains 91 lakhs. Also, find the recent error log file. Pls, do the needful.

    130813 18:06:50 [ERROR] Got error 134 when reading table './sms/attend'
    130813 18:07:20 [ERROR] Got error 134 when reading table './sms/attend'
    130813 19:40:09 [Note] Found 9151097 of 9151104 rows when repairing './sms/attend'
    130814 7:10:28 - 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=2147483648
    read_buffer_size=5238784

    Number of processes running now: 0
    130814 07:10:31 mysqld restarted
    130814 7:11:40 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '5.0.51a-community-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL)
    130815 9:44:03 [ERROR] /usr/sbin/mysqld: Sort aborted

  2. #2
    Join Date
    Jun 2007
    Posts
    197
    What is mysql version

    give my.cnf contant

    Is the table Innodb

    Sort aborted usually comes when query executed and temp table has no space in disk means tmp disk got full while executing query

  3. #3
    Join Date
    May 2012
    Location
    Chennai
    Posts
    45

    Question mysql error and sometimes crash the table

    Hi,

    ok.. But, we have more than 51GB available space on the mysql filesystem, Can you explain more on temporary table and disk full. And also, how to find out that issue and suggest me to fix the issue.

    Note: Not innodb


    --Recently, we got the error log

    130815 23:38:41 - 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=67108864
    read_buffer_size=5238784
    max_used_connections=247
    max_connections=190
    threads_connected=26
    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1426694 K
    bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.

    thd=0x2f306e60
    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...
    Cannot determine thread, fp=0x169e197c, backtrace may not be correct.
    Stack range sanity check OK, backtrace follows:
    Fatal signal 6 while backtracing
    mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed.
    0x81c4317
    0x82034aa
    0x8203d48
    0x8203ec4
    0x823c44f
    0x81ddc6c
    0x81e18ba
    0x81e2766
    0x81e31b7
    0x81e3bf0
    0x83e5cc
    0x7a8f0e
    New value of fp=(nil) failed sanity check, terminating stack trace!
    Please read MySQL :: MySQL 5.6 Reference Manual :: 23.4.1.5 Using a Stack Trace and follow instructions on how to resolve the stack trace. Resolved
    stack trace is much more helpful in diagnosing the problem, so please do
    resolve it
    Trying to get some variables.
    Some pointers may be invalid and cause the dump to abort...
    thd->query at 0x22868ca8 is invalid pointer
    thd->thread_id=181228
    The manual page at http://www.mysql.com/doc/en/Crashing.html contains
    information that should help you find out what is causing the crash.
    mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed.
    mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed.

    ================================================== ========

    Kindly, find the mysql version.

    mysql> SHOW VARIABLES LIKE "%version%";
    +-------------------------+-------------------------------+
    | Variable_name | Value |
    +-------------------------+-------------------------------+
    | protocol_version | 10 |
    | version | 5.0.51a-community-log |
    | version_comment | MySQL Community Edition (GPL) |
    | version_compile_machine | i686 |
    | version_compile_os | redhat-linux-gnu |
    +-------------------------+-------------------------------+
    ================================================== ========
    -- my.cnf file

    # The following options will be passed to all MySQL clients
    [client]
    #password = your_password
    port = 3313
    socket = /var/lib/mysql/mysql.sock

    # Here follows entries for some specific programs

    # The MySQL server
    [mysqld]
    user = mysql
    datadir=/mysqldb/ #was /var/lib/mysql/
    port = 3306
    socket = /var/lib/mysql/mysql.sock
    # General query log by Veon on 04-March-2008
    #log=/var/lib/mysql/mysql-query.log
    # Binary/update log by Veon on 04-March-2008
    log-bin=/var/lib/mysql/mysql-bin.log
    #### Changed on 08May2010 ####
    log-slow-queries=/var/lib/mysql/slow-queries.log


    max_connections=500
    max_user_connections=300
    #max_connections=250
    #max_user_connections=125
    skip-locking
    #key_buffer = 256M
    key_buffer = 2048M
    max_allowed_packet=16M
    table_cache=1024
    join_buffer_size=2M
    read_buffer_size=5M
    #sort_buffer_size=3M
    sort_buffer_size=2M
    read_rnd_buffer_size = 4M
    myisam_sort_buffer_size = 64M
    thread_cache_size=128
    query_cache_limit=2M
    #query_cache_limit=1M
    query_cache_size=128M
    #query_cache_size=32M
    query_cache_type=1
    # Try number of CPU's*2 for thread_concurrency
    thread_concurrency=8

    wait_timeout=60
    #wait_timeout=14400
    connect_timeout=10
    #connect_timeout=400
    max_connect_errors=10000


    # skip-locking
    # key_buffer = 256M
    # max_allowed_packet = 1M
    # table_cache = 256
    # sort_buffer_size = 1M
    # read_buffer_size = 1M
    # read_rnd_buffer_size = 4M
    # myisam_sort_buffer_size = 64M
    # thread_cache_size = 8
    # query_cache_size= 16M
    # Try number of CPU's*2 for thread_concurrency
    # thread_concurrency = 8

    # Don't listen on a TCP/IP port at all. This can be a security enhancement,
    # if all processes that need to connect to mysqld run on the same host.
    # All interaction with mysqld must be made via Unix sockets or named pipes.
    # Note that using this option without enabling named pipes on Windows
    # (via the "enable-named-pipe" option) will render mysqld useless!
    #
    #skip-networking

    # Replication Master Server (default)
    # binary logging is required for replication
    # log-bin deactivated by default since XAMPP 1.4.11
    #log-bin=mysql-bin

    # required unique id between 1 and 2^32 - 1
    # defaults to 1 if master-host is not set
    # but will not function as a master if omitted
    server-id = 1

    # Replication Slave (comment out master section to use this)
    #
    # To configure this host as a replication slave, you can choose between
    # two methods :
    #
    # 1) Use the CHANGE MASTER TO command (fully described in our manual) -
    # the syntax is:
    #
    # CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
    # MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
    #
    # where you replace <host>, <user>, <password> by quoted strings and
    # <port> by the master's port number (3306 by default).
    #
    # Example:
    #
    # CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
    # MASTER_USER='joe', MASTER_PASSWORD='secret';
    #
    # OR
    #
    # 2) Set the variables below. However, in case you choose this method, then
    # start replication for the first time (even unsuccessfully, for example
    # if you mistyped the password in master-password and the slave fails to
    # connect), the slave will create a master.info file, and any later
    # change in this file to the variables' values below will be ignored and
    # overridden by the content of the master.info file, unless you shutdown
    # the slave server, delete master.info and restart the slaver server.
    # For that reason, you may want to leave the lines below untouched
    # (commented) and instead use CHANGE MASTER TO (see above)
    #
    # required unique id between 2 and 2^32 - 1
    # (and different from the master)
    # defaults to 2 if master-host is set
    # but will not function as a slave if omitted
    #server-id = 2
    #
    # The replication master for this slave - required
    #master-host = <hostname>
    #
    # The username the slave will use for authentication when connecting
    # to the master - required
    #master-user = <username>
    #
    # The password the slave will authenticate with when connecting to
    # the master - required
    #master-password = <password>
    #
    # The port the master is listening on.
    # optional - defaults to 3306
    #master-port = <port>
    #
    # binary logging - not required for slaves, but recommended
    #log-bin=mysql-bin


    # Point the following paths to different dedicated disks
    #tmpdir = /tmp/
    #log-update = /path-to-dedicated-directory/hostname

    # Uncomment the following if you are using BDB tables
    #bdb_cache_size = 4M
    #bdb_max_lock = 10000

    # Comment the following if you are using InnoDB tables
    skip-innodb
    #innodb_data_home_dir = /opt/lampp/var/mysql/
    #innodb_data_file_path = ibdata1:10M:autoextend
    #innodb_log_group_home_dir = /opt/lampp/var/mysql/
    #innodb_log_arch_dir = /opt/lampp/var/mysql/
    # You can set .._buffer_pool_size up to 50 - 80 %
    # of RAM but beware of setting memory usage too high
    #innodb_buffer_pool_size = 16M
    #innodb_additional_mem_pool_size = 2M
    # Set .._log_file_size to 25 % of buffer pool size
    #innodb_log_file_size = 5M
    #innodb_log_buffer_size = 8M
    #innodb_flush_log_at_trx_commit = 1
    #innodb_lock_wait_timeout = 50

    [mysqldump]
    quick
    max_allowed_packet = 64M

    [mysql]
    no-auto-rehash
    # Remove the next comment character if you are not familiar with SQL
    #safe-updates

    [isamchk]
    key_buffer = 128M
    sort_buffer_size = 128M
    read_buffer = 2M
    write_buffer = 2M

    [myisamchk]
    key_buffer = 128M
    sort_buffer_size = 128M
    read_buffer = 2M
    write_buffer = 2M

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •