Results 1 to 3 of 3
  1. #1
    Join Date
    Apr 2015
    Posts
    2

    Unanswered: Server hung twice now. Mysql log help

    My server hung two times in the last week and was rebooted. I see the following entries in the MySQL log. Much is from the reboot .... I believe some action is needed on my part to clear up some of these issues but I'm not sure what to do, or how to do it.

    Please look over the log snippit below and advise what action is needed. Note: I am running VB forums on this server and the VB software is the prime user of MySQL

    Thu Mar 26 00:01:02 EDT 2015
    150326 18:12:16 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    150326 18:12:17 [Warning] /usr/libexec/mysqld: Option '--set-variable' is deprecated. Use --variable-name=value instead.
    150326 18:12:17 InnoDB: Initializing buffer pool, size = 8.0M
    150326 18:12:17 InnoDB: Completed initialization of buffer pool
    InnoDB: The log sequence number in ibdata files does not match
    InnoDB: the log sequence number in the ib_logfiles!
    150326 18:12:17 InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    150326 18:12:18 InnoDB: Started; log sequence number 0 5624774
    150326 18:12:18 [Note] Event Scheduler: Loaded 0 events
    150326 18:12:18 [Note] /usr/libexec/mysqld: ready for connections.
    Version: '5.1.56' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
    Fri Mar 27 00:01:01 EDT 2015
    Sat Mar 28 00:01:01 EDT 2015
    Sun Mar 29 00:01:01 EDT 2015
    150329 17:53:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    150329 17:53:13 [Warning] /usr/libexec/mysqld: Option '--set-variable' is deprecated. Use --variable-name=value instead.
    150329 17:53:13 InnoDB: Initializing buffer pool, size = 8.0M
    150329 17:53:13 InnoDB: Completed initialization of buffer pool
    InnoDB: The log sequence number in ibdata files does not match
    InnoDB: the log sequence number in the ib_logfiles!
    150329 17:53:13 InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    150329 17:53:15 InnoDB: Started; log sequence number 0 5624784
    150329 17:53:16 [Note] Event Scheduler: Loaded 0 events
    150329 17:53:16 [Note] /usr/libexec/mysqld: ready for connections.
    Version: '5.1.56' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
    150329 19:18:59 [Note] /usr/libexec/mysqld: Normal shutdown

    150329 19:18:59 [Note] Event Scheduler: Purging the queue. 0 events
    150329 19:18:59 InnoDB: Starting shutdown...
    150329 19:19:02 InnoDB: Shutdown completed; log sequence number 0 5624784
    150329 19:19:02 [Note] /usr/libexec/mysqld: Shutdown complete

    150329 19:19:02 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
    150329 19:19:39 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    150329 19:19:40 [Warning] /usr/libexec/mysqld: Option '--set-variable' is deprecated. Use --variable-name=value instead.
    150329 19:19:40 InnoDB: Initializing buffer pool, size = 8.0M
    150329 19:19:40 InnoDB: Completed initialization of buffer pool
    150329 19:19:40 InnoDB: Started; log sequence number 0 5624784
    150329 19:19:40 [Note] Event Scheduler: Loaded 0 events
    150329 19:19:40 [Note] /usr/libexec/mysqld: ready for connections.
    Version: '5.1.56' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
    Mon Mar 30 00:01:02 EDT 2015
    Tue Mar 31 00:01:01 EDT 2015
    Wed Apr 1 00:01:01 EDT 2015

  2. #2
    Join Date
    Dec 2007
    Location
    Richmond, VA
    Posts
    1,328
    Provided Answers: 5
    This log info shows that MySQL handled itself as it should have. Had to go through crash recovery to ensure that you had a recoverable database prior to allowing you to change anything. The question is what happened prior to this to cause you all to reboot your server without shutting down normally?
    Dave

  3. #3
    Join Date
    Apr 2015
    Posts
    2
    Not sure. That is the problem. I thought maybe it was a DB issue otherwise I'm going to have to start hunting some more.
    Load average was not up. httpd log had nohting special. Very strange.

Posting Permissions

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