Results 1 to 5 of 5
  1. #1

    unable to run mysql on linux - after shuting down

    hi,

    I was having issue with ibdata1 file which had grown to 5GB on the server machine. so after reading couple of blogs, i got the way how to remove it. i backedup my DB's, stopped the mysql and deleted that ibdata1 file.

    now after that, i am unable to run mysql in ANYWAY!. I have searched accross the boards, across the blogs and i am still unable to figure out the problem.

    every time i start it gives me following error
    Code:
    [[email protected] init.d]# /etc/init.d/mysqld start
    Timeout error occurred trying to start MySQL Daemon.
    Starting MySQL:                                            [FAILED]
    and here is my my.cnf file
    Code:
    [mysqld]
    datadir=/var/lib/mysql
    socket=/var/lib/mysql/mysql.sock
    max_connections=50
    table_cache=1000
    thread_cache_size=40
    thread_stack=100K
    wait_timeout=10
    join_buffer=2M
    myisam_sort_buffer_size=6M
    query_cache_size=6M
    read_rnd_buffer_size=2M
    #i wrote this line to recover, but failed. innodb_force_recovery=4
    
    [mysql.server]
    user=mysql
    basedir=/var/lib
    
    [mysqld_safe]
    err-log=/var/log/mysqld.log
    pid-file=/var/run/mysqld/mysqld.pid

  2. #2
    Join Date
    Jun 2007
    Location
    UK
    Posts
    219
    There should be something in the logs telling you why MySQL failed to start.
    I think the server saw what was required of it and just committed suicide instead.

  3. #3
    InnoDB: End of page dump
    080514 3:00:35 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
    InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
    InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
    InnoDB: Page number (if stored to page already) 0,
    InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
    080514 3:00:35InnoDB: Error: trying to access a stray pointer 0x35c57ff8
    InnoDB: buf pool start is at 0xb5c48000, end at 0xb6448000
    InnoDB: Probable reason is database corruption or memory
    InnoDB: corruption. If this happens in an InnoDB database recovery,
    InnoDB: you can look from section 6.1 at
    InnoDB: how to force recovery.
    080514 3:00:35InnoDB: Assertion failure in thread 3081860800 in file ./../include/buf0buf.ic line 262
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to
    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: InnoDB: about forcing recovery.
    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=0
    read_buffer_size=131072
    max_used_connections=0
    max_connections=50
    threads_connected=0
    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 108799 K
    bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.

    thd=(nil)
    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=0xbfff9d7c, backtrace may not be correct.
    Stack range sanity check OK, backtrace follows:
    0x8130bff
    0xb7e653e8
    (nil)
    0x82fcb74
    0x829b52f
    0x829c044
    0x8282f66
    0x82811dc
    0x81b6a81
    0x81a9537
    0x812f485
    0x8132cdb
    0xb7bf5d5f
    0x80d0161
    New value of fp=(nil) failed sanity check, terminating stack trace!
    Please read 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
    The manual page at
    contains
    information that should help you find out what is causing the crash.
    080514 03:00:35 mysqld ended

  4. #4
    Join Date
    Aug 2003
    Location
    Chicago, IL USA
    Posts
    2,781
    I'm assuming you followed these directions
    http://dev.mysql.com/doc/refman/5.0/...-removing.html
    CloudRck.com - Host on Cloudrck
    Unmetered VPS Solutions at it's finest

  5. #5

    use strace

    do this go inside the /etc/init.d/ directory

    then run

    this command

    strace /etc/init.d/mysql start

    strace will allow you to find out what exactly is causing this issue. Cut and paste the results and paste it here.

    Tepezcuintle

Posting Permissions

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