Error Log - Table crash with cmsb__error_log table with over 13 gigs of info

2 posts by 2 authors in: Forums > CMS Builder
Last Post: October 18, 2018   (RSS)

By depdesign - October 18, 2018

Hi all,

Today i had a major issue, still trying to resolve, where the cmsb__error_log table encountered over 13 gigs of info.  It first caused the site to receive a "Hello, Website Visitors! error page. and then finally crashed the server.

I believe this may have happened today as both bing and google bots were on the sites gathering their info.

The iT guys at hostgator said the permalinks dispatch php was  causing an issue too.

Here is my thought

Could the bing bots have caused to many permalinks to get loaded at once which then increased the amount of server errors per permalink causing the cmsb_error_log to get too large which then crashed the DB eventually the server?

If so, can the Error Log be turned off?

Is there something that can be done to optimize the permalink plugin?

My server and sql db are being checked as I write this message.  If anyone has encountered anything similar or if you have a solution please reply.

Thanks

Dan

Dan Perez

By daniel - October 18, 2018

Hi Dan,

It is a bit concerning that your error log grew to 13GB in size, however, modern servers can support MySQL table sizes of 2TB+, so unless this was causing the server to run out of disk space, I think it more likely that this is a symptom of whatever caused the server crash, rather than being the sole reason. I've definitely seen situations where search engine bots crawling sites very quickly causes spikes in server load, which - depending on a few factors - can lead to a crash. 13 gigs in your error log could easily be indicative of that level of bot traffic.

While it's possible to disable the error log for certain cases, there's no simple way to globally turn it off for the whole site. Though it should be possible to either fix whatever is causing the errors or suppress the error log in those places. Whether or not it was the size of the error log that caused the crash, it is still a good idea to prevent it from ballooning to that size, and reducing the errors on your site will also reduce its impact on the server load if you ever get "spammed" by search engine bots in the future.

To get a better idea of what has happened, could you let me know:

  • Your installed version of CMSB
  • Your installed version of Permalinks Plugin
  • A sampling of any errors showing up in the Developer Log

Thanks,

Daniel
Technical Lead
interactivetools.com