We are transitioning over to a new forum platform. Please post new issues there. Existing threads will be dealt with here unless you choose to move them over. Visit the new forum

Forum

Thread tagged as: Question, Problem, Error

SQL Tables Keep Crashing on Client Site

A client's site is still on Perch 2.8.34, and they've recently had the perch_events and _content_items database tables crash. I've repaired them, but don't know why they're crashing. Disk space and memory and bandwidth have plenty of room left. All I'm thinking is its because we're on 2.8.34 and not 3.0.5, but it should keep running, right?

Diagnostic report:

SUMMARY INFORMATION

Perch: 2.8.34, PHP: 5.6.30, MySQL: mysqlnd 5.0.11-dev - 20120503 - $Id: 76b08b24596e12d4553bd41fc93cccd5bac2fe7a $, with PDO
Server OS: Linux, cgi-fcgi
Installed apps: content (2.8.34), assets (2.8.34), categories (2.8.34), perch_blog (4.6), perch_events (1.9.2), perch_forms (1.8.3), perch_shop_paypal (1.2.3), perch_podcasts (1.1)
App runtimes: <?php $apps_list = array( 'content', 'categories', 'perch_blog', 'perch_events', 'perch_forms', 'perch_shop_paypal', 'perch_podcasts' ); ?>
PERCH_LOGINPATH: /perch
PERCH_PATH: /home/mchsadmn/public_html/perch
PERCH_CORE: /home/mchsadmn/public_html/perch/core
PERCH_RESFILEPATH: /home/mchsadmn/public_html/perch/resources
Image manipulation: GD Imagick
PHP limits: Max upload 1024M, Max POST 1024M, Memory: 256M, Total max file upload: 256M
F1: 6a33f95eca3667f9e0c39bf5ca2980fe
Resource folder writeable: Yes
DOCUMENT_ROOT: /home/mchsadmn/public_html
HTTP_HOST: mchistory.org
REQUEST_URI: /perch/core/settings/diagnostics/
SCRIPT_NAME: /perch/core/settings/diagnostics/index.php

I don't want to update them if there's another problem that would make this situation worse. How should I proceed in troubleshooting this?

Gary Iverson

Gary Iverson 0 points

  • 2 years ago
Rachel Andrew

Rachel Andrew 394 points
Perch Support

This is unlikely to be an issue with Perch. If it were we would be seeing this from large numbers of people. Most likely you are on an overloaded shared database server.