AI Search
Classic Search
 Search Phrase:
 Search Type:
Advanced search options
 Search in Forums:
 Search in date period:

 Sort Search Results by:

AI Assistant
Notifications
Clear all

[Solved] wpforo_topics is marked as crashed and should be repaired

2 Posts
1 Users
0 Reactions
704 Views
Posts: 212
 fawp
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@fawp)
Reputable Member
Joined: 7 years ago
[#62278]

Hi support,

 

Yesterday I got the following table errors:

 37 [ERROR] mariadb: Table '_wpforo_posts' is marked as crashed and should be repaired

38 [ERROR] mariadbd: Table '_wpforo_topics' is marked as crashed and should be repaired

There were no DB / table errors within wpForo control panel, nor were there any issues in the debug tab.

(Tables/Servers/Errors & Issues: No issues found)

What I did

  • deleted all caches
  • clean up
  • ran a `sudo mysqlcheck --repair --all-databases`

I received a

_wpforo_posts OK

_wpforo_topics OK

 

However today I have again received the following system error (only for Topics)

38 [ERROR] mariadb : Table '_wpforo_topics' is marked as crashed and should be repaired

 

Besides running a repair again like I did already, is there anything else you would recommend?

 

Thanks

fawp


1 Reply
Posts: 212
 fawp
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@fawp)
Reputable Member
Joined: 7 years ago

Update: I now don't think this was a database issue. It was likely caused by web scrapers crashing the site, so closing as resolved for now.


Share: