Announcement

Collapse
No announcement yet.

MySQL crashing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Pirotess
    replied
    Originally posted by Steve Machol View Post
    For future reference, please do not double-post. Thank you.
    I assume you are referring to the post in the server configuration forum?

    If so then you may want to consider a common moderation policy since the only reason I did that is the last time I posted up here in this section, I was asked to post instead down in that forum.

    http://www.vbulletin.com/forum/showthread.php?t=170208

    I dont say this to be contrary, just to explain Im trying to be a consistant and conscientious user providing as much info as possible when I ask for assistance.

    Leave a comment:


  • Steve Machol
    replied
    For future reference, please do not double-post. Thank you.

    Leave a comment:


  • Pirotess
    replied
    Update:

    Thanks to Tomek for pointing out this known bug which was the cause of my problems.

    http://www.vbulletin.com/forum/bugs3...iew&bugid=2449

    Leave a comment:


  • Pirotess
    started a topic MySQL crashing

    MySQL crashing

    Good morning,

    Unfortunately I woke up this morning to two very sick vBulletin installations. From what I can gather from my logs and email alerts, cPanel upgraded MySQL from 5.0.19 to 5.0.21 last night. Immediately after the upgrade I started getting frequent errors from vBulletin queries.

    Those errors being MySQL Error : Lost connection to MySQL server during query, Error Number : 2013 and MySQL Error : MySQL server has gone away Error Number : 2006.

    Now I have read this thread http://www.vbulletin.com/forum/showt...265#post310265 about those two errors but in my case as you can see from my config below, my settings arent in question. In fact my settings (with the exception of wait_timeout which I bumped to 28800 from 300) were given to me from the folks in the server optimization forum.

    PHP Code:
    [mysqld]
    safe-show-database
    old_passwords
    skip
    -innodb
    max_connections 
    500
    key_buffer 
    64M
    myisam_sort_buffer_size 
    32M
    join_buffer_size 
    1M
    read_buffer_size 
    2M
    read_rnd_buffer_size 
    2M
    sort_buffer_size 
    2M
    table_cache 
    1500
    thread_cache_size 
    64
    thread_concurrency 
    2
    wait_timeout 
    28800
    connect_timeout 
    10
    interactive_timeout 
    100
    tmp_table_size 
    32M
    max_allowed_packet 
    16M
    max_connect_errors 
    10
    query_cache_limit 
    1M
    query_cache_size 
    16M
    query_cache_type 
    1
    query_prealloc_size 
    16384
    query_alloc_block_size 
    16384
    old
    -passwords 1

    [mysqld_safe]
    open_files_limit 8192

    [mysqldump]
    quick
    max_allowed_packet 
    16M

    [myisamchk]
    key_buffer 64M
    sort_buffer 
    64M
    read_buffer 
    16M
    write_buffer 
    16M 
    What I do have is a server that crashes repetatively. Using mysqladmin version Im only getting uptimes of seconds instead of days. This is a copy of my MySQL error log.

    060607 09:22:46 mysqld started
    060607 9:22:46 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '5.0.18-standard' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)
    060613 3:04:16 [Note] /usr/sbin/mysqld: Normal shutdown

    060613 3:04:18 [Note] /usr/sbin/mysqld: Shutdown complete

    060613 03:04:19 mysqld ended

    060613 03:04:33 mysqld started
    060613 3:04:33 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '5.0.21-standard' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)
    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=2093056
    max_used_connections=2
    max_connections=500
    threads_connected=1
    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2111532 K
    bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.

    thd=0xa301ba0
    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=0x15f7e4, backtrace may not be correct.
    Stack range sanity check OK, backtrace follows:
    0x815fa4a
    0x9edf88
    0x81f56c2
    0x81f56c2
    0x81f59cf
    0x81f2a30
    Stack trace seems successful - bottom reached
    Please read http://dev.mysql.com/doc/mysql/en/Us...ack_trace.html 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 0xa308ed8 = SELECT forum.forumid
    FROM vb3_forum AS forum
    LEFT JOIN vb3_forumread AS forumread ON (forum.forumid = forumread.forumid AND forumread.userid = 117)
    WHERE forum.forumid IN (11,24,-1)
    AND forum.forumid NOT IN (11, -1)
    AND (forum.lastpost = 0 OR
    IF(forumread.readtime IS NULL, 1149320426, forumread.readtime) > forum.lastpost
    )
    thd->thread_id=482
    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.

    Number of processes running now: 0
    060613 03:40:26 mysqld restarted
    060613 3:40:26 [Note] /usr/sbin/mysqld: ready for connections.
    I honestly dont know where to go from here. I feel I've identified the problem but dont know how to fix it besides trying to roll the server back to 5.0.19. Any other suggestions? My thanks in advance.
    Last edited by Pirotess; Tue 13th Jun '06, 11:53am.
widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Working...
X