GET 24/7 LIVE HELP NOW

Announcement

Announcement Module
Collapse
No announcement yet.

Unknows thread - ha_myisam.cc:873

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

  • Unknows thread - ha_myisam.cc:873

    Got this error when restarted MySQL.
    [ERROR] Got an error from unknown thread, /home/buildbot/src/work/BUILD/Percona-Server-5.5.19-rel24.0/ Percona-Server-5.5.19-rel24.0/storage/myisam/ha_myisam.cc:87 3

  • #2
    Hi,

    Can you paste here the exact output of error log when you are starting MySQL?
    When you are getting this error? After installations, first time start? or MySQL was already running properly and just a schedule restart cause this error?

    Please provide some more information. It would be helpful to troubleshoot this issue. Thanks.

    Comment


    • #3
      Please find the details below -

      120727 20:40:38 mysqld_safe Number of processes running now: 0
      120727 20:40:38 mysqld_safe mysqld restarted
      120727 20:40:38 [Note] Flashcache bypass: disabled
      120727 20:40:38 [Note] Flashcache setup error is : ioctl failed

      120727 20:40:39 [Note] Plugin 'FEDERATED' is disabled.
      120727 20:40:39 InnoDB: The InnoDB memory heap is disabled
      120727 20:40:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
      120727 20:40:39 InnoDB: Compressed tables use zlib 1.2.3
      120727 20:40:39 InnoDB: Using Linux native AIO
      120727 20:40:39 InnoDB: Initializing buffer pool, size = 8.0G
      120727 20:40:40 InnoDB: Completed initialization of buffer pool
      120727 20:40:40 InnoDB: highest supported file format is Barracuda.
      InnoDB: The log sequence number in ibdata files does not match
      InnoDB: the log sequence number in the ib_logfiles!
      120727 20:40:40 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...
      InnoDB: Last MySQL binlog file position 0 783116746, file name /var/log/mysql/db1.000008
      120727 20:40:44 InnoDB: Waiting for the background threads to start
      120727 20:40:45 Percona XtraDB (http://www.percona.com) 1.1.8-rel24.0 started; log sequence number 10213583561
      120727 20:40:45 [Note] Recovering after a crash using /var/log/mysql/db1
      120727 20:41:07 [Note] Starting crash recovery...
      120727 20:41:07 [Note] Crash recovery finished.
      120727 20:41:08 [Note] Event Scheduler: Loaded 0 events
      120727 20:41:08 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '5.5.19-55-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Percona Server (GPL), Release rel24.0, Revision 204
      120727 20:41:08 [Note] Event Scheduler: scheduler thread started with id 1

      Comment


      • #4
        Hi, I'm not seeing any "unknown thread error" in above output. Seems server is properly started with crash recovery as per the log output.

        Comment


        • #5
          Sorry, please find the logs below -


          120727 20:40:38 mysqld_safe Number of processes running now: 0
          120727 20:40:38 mysqld_safe mysqld restarted
          120727 20:40:38 [Note] Flashcache bypass: disabled
          120727 20:40:38 [Note] Flashcache setup error is : ioctl failed

          120727 20:40:39 [Note] Plugin 'FEDERATED' is disabled.
          120727 20:40:39 InnoDB: The InnoDB memory heap is disabled
          120727 20:40:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
          120727 20:40:39 InnoDB: Compressed tables use zlib 1.2.3
          120727 20:40:39 InnoDB: Using Linux native AIO
          120727 20:40:39 InnoDB: Initializing buffer pool, size = 8.0G
          120727 20:40:40 InnoDB: Completed initialization of buffer pool
          120727 20:40:40 InnoDB: highest supported file format is Barracuda.
          InnoDB: The log sequence number in ibdata files does not match
          InnoDB: the log sequence number in the ib_logfiles!
          120727 20:40:40 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...
          InnoDB: Last MySQL binlog file position 0 783116746, file name /var/log/mysql/db1.000008
          120727 20:40:44 InnoDB: Waiting for the background threads to start
          120727 20:40:45 Percona XtraDB (http://www.percona.com) 1.1.8-rel24.0 started; log sequence number 10213583561
          120727 20:40:45 [Note] Recovering after a crash using /var/log/mysql/db1
          120727 20:41:07 [Note] Starting crash recovery...
          120727 20:41:07 [Note] Crash recovery finished.
          120727 20:41:08 [Note] Event Scheduler: Loaded 0 events
          120727 20:41:08 [Note] /usr/sbin/mysqld: ready for connections.
          Version: '5.5.19-55-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Percona Server (GPL), Release rel24.0, Revision 204
          120727 20:41:08 [Note] Event Scheduler: scheduler thread started with id 1
          120727 20:41:12 [ERROR] /usr/sbin/mysqld: Table './DB1/wp_options' is marked as crashed and should be repaired
          120727 20:41:12 [Warning] Checking table: './DB1/wp_options'
          120727 20:41:13 [ERROR] Got an error from unknown thread, /home/buildbot/src/work/BUILD/Percona-Server-5.5.19-rel24.0/ Percona-Server-5.5.19-rel24.0/storage/myisam/ha_myisam.cc:87 3
          120727 20:41:13 [Warning] Recovering table: './DB1/wp_options'

          Note - We have installed percona through RPM's where server version is - Server version: 5.5.19-55-log Percona Server (GPL), Release rel24.0, Revision 204

          Comment

          Working...
          X