• I was doing some simple edits last night (uploading/replacing images, adding custom CSS to menu styles, adding new menu links) when suddenly I began to get internal server errors

    Internal Server Error
    The server encountered an internal error or misconfiguration and was unable to complete your request.  ...
    Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

    I finally renamed by .htaccess and the site popped back up – at least the homepage – I didn’t look at the other pages before quitting for the night. This morning I began editing again and the same thing happened. But this time I took note of a few more things.

    1. Looking in my cPanel it show that Memory Usage is maxing out.
    2. I/O usage is maxing out.
    3. The admin section works but live site gives “internal server error” for the homepage and 404 errors (or sometimes 500) on all other pages.
    4. renaming the HTACCESS file temporarily brings back the homepage.
    5. I did try re-saving the permalinks under settings but that does’t fix the 404 or 500 error for those pages.
    6. No new plugins in the last couple weeks
    7. Nothing showing up in error log

    Using most recent WordPress
    Avada theme (up-to-date)
    server is mySQL 5.6 on UNIX
    site url: cantria.org

    Thanks for any help!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    please show your problemmatic .htaccess file and look in your server’s error logs for a clue as to what it doesn’t like about that file (/var/log/httpd/whatever-you-defined-as-the-sites-error-log)

    Thread Starter andysb72

    (@andysb72)

    Hi Steve,

    Here’s the htaccess

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    
    # END WordPress

    I wasn’t seeing errors in the error log before, but I do see this now.

    [01-Dec-2016 15:32:03 UTC] PHP Warning: Error while sending QUERY packet. PID=992177 in /home/########/public_html/wp-includes/wp-db.php on line 1870

    Could that be it?

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    aha! usually that means that you’ve exceeded the max packet size for your mysql configuration.

    You can edit your mysql config file to increase that limit. Restart mysqld after making the change.

    https://dev.mysql.com/doc/refman/5.5/en/packet-too-large.html

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Internal server error, 404s, and maxed out memory’ is closed to new replies.