WordPress.org

1. T34se
   Member
   Posted 3 months ago #

   Hi Mitchoyoshitaka,

   Just wanted to inform you that we have had 3 crashes that froze the server plus our rss feeds were locked (not sure if related, feeds were unreadable error code for password protected feeds even though they are not)

   Operating system Linux 2.6.24.5-85.fc8
   CPU GenuineIntel, Intel(R) Celeron(R) CPU 2.80GHz
   MySQL - 5.0.45
   phpMyAdmin - 2.8.2.4
   IP 64.150.181.248
   using wp8.3 with the latest Yarp.

   Below are excerpts from mysqld.log
   090810 11:46:45 [ERROR] Got error 134 when reading table './leslie/wordpress_yarpp_related_cache'
   090810 11:46:53 [ERROR] Got error 134 when reading table './leslie/wordpress_yarpp_related_cache'
   090810 12:27:35 [ERROR] Got error 134 when reading table './leslie/wordpress_yarpp_related_cache'
   090810 12:27:40 [ERROR] Got error 134 when reading table './leslie/wordpress_yarpp_related_cache'
   090810 12:27:51 [ERROR] Got error 134 when reading table './leslie/wordpress_yarpp_related_cache'
   090810 12:27:59 [ERROR] Got error 134 when reading table './leslie/wordpress_yarpp_related_cache'
   090810 17:09:22 [ERROR] Got error 134 when reading table './leslie/wordpress_yarpp_related_cache'
   090810 17:09:30 [ERROR] Got error 134 when reading table './leslie/wordpress_yarpp_related_cache'
   090810 19:51:17 mysqld started
   090810 19:51:17 InnoDB: Database was not shut down normally!
   InnoDB: Starting crash recovery.

   Next

   Version: '5.0.45' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
   090810 21:52:19 [ERROR] Got error 134 when reading table './leslie/wordpress_yarpp_related_cache'
   090810 21:52:24 [ERROR] Got error 134 when reading table './leslie/wordpress_yarpp_related_cache'
   InnoDB: Warning: a long semaphore wait:
   --Thread 2996206480 has waited at log0log.c line 1986 for 242.00 seconds the semaphore:
   S-lock on RW-latch at 0xb7da919c created in file log0log.c line 801
   a writer (thread id 2996206480) has reserved it in mode exclusive
   number of readers 0, waiters flag 1
   Last time read locked in file log0log.c line 1986
   Last time write locked in file log0log.c line 1782
   InnoDB: ###### Starts InnoDB Monitor for 30 secs to print diagnostic info:
   InnoDB: Pending preads 0, pwrites 0

2. mitchoyoshitaka
   Member
   Posted 3 months ago #

   @T34se, this seems like an underlying mysql engine issue. Apparently the table is corrupt. Please try check table wp_yarpp_related_cache extended and let me know what you get.

   You can then repair table wp_yarpp_related_cache. If that doesn't work, feel free to just drop the table... YARPP should attempt to rebuild it.

   You can also make sure that the two YARPP tables and the wp_posts table are using MyISAM as the engine.

3. T34se
   Member
   Posted 3 months ago #

   Hi Hi Mitchoyoshitaka,

   MySQL said:

   #145 - Table './leslierad/wordpress_yarpp_related_cache' is marked as crashed and should be repaired.

   I removed YARP last night and no further crashes, rather than repair the table I will delete it and try YARP again,

   BTW I'm now using WP 8.4 and your Plugin Page supports to 8.2, should it be OK?

   Thanks for the quick support and great plugin.

4. mitchoyoshitaka
   Member
   Posted 3 months ago #

   @T34e, 8.4 is supported.

5. T34se
   Member
   Posted 3 months ago #

   Hi Hi Mitchoyoshitaka,

   Just had another crash after the reinstall, am gonna try isolate the issue by removing YARP for now,

   I just checked the all the tables you mentioned and all were fine plus are are/were using MyISAM

   The below was the only warning in the tables

   wordpress_posts

   post_content + yarpp_content

   Warning image: More than one FULLTEXT key was created for column post_content

   Nothing else for us to do now but wait a few days to see if it is YARP or something else.

6. mitchoyoshitaka
   Member
   Posted 3 months ago #

   @T34se, hmm... thanks for testing and keeping me updated. :/

Reply

You must log in to post.