500 Internal Error, troubleshot everything

  • Resolved metathriving

    (@metathriving)


    9 years, 8 months ago

    I was running some site work today via the server portal where I can get to the guts of everything, and noticed an alert letting me know that the WP version was due for an update, so I clicked for that to do its thing while I was checking some of my site structure to figure out how I wanted to set up the redesign I’m poking at.

    When I went to look at the blog itself to evaluate what I wanted to change about it to fit with the new look, I was hit with a 500 Internal Server Error. http://metathriving.com/wordpress/

    Came here, went through the troubleshooting checklist. Cleared my cache and checked my browser (using Firefox 47.0.1 btw) and disabled plugins (which I had to do via PhpMyAdmin because I cannot access anything any other way.) Backed up all the theme folders onto my computer and deleted everything but twentysixteen off my server. Manually installed an upgrade and followed instructions to the dot.

    Ran checks for errors through MySQL, hit nothing.

    I normally can puzzle my way out of these situations, but this one has me rather like Jeremy Clarkson trying to repair a car engine. And I know neither horsepower nor chainsaws are the answer to this issue. But I’m here to throw in the towel because I’m ready to try either of those in sheer frustration. Help?

Viewing 15 replies - 1 through 15 (of 26 total)
1 2
  • Moderator James Huff

    (@macmanx)

    9 years, 8 months ago

    If resetting the plugins and theme did not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.

    If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that specific time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

    Thread Starter metathriving

    (@metathriving)

    9 years, 8 months ago

    Okay. Went digging, I know the file you’re talking about, looked high and low, triple-checked on the invisible file visibility, searched via both CPanel and FireFTP, then set up FireFTP to do a search through the remote host and subdirectories for the file. Only hit was in the akismet plugin, which I deactivated (but renamed anyway just to check) no luck. There was nothing in the root WP file.

    I don’t recall ever making a WP htaccess file specifically, so I did some looking, and used this site and made a file with this content and uploaded it to the root directory.

    # BEGIN WordPress
RewriteRule ^index\.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

    No luck. Tried renaming it, no luck. (changed everything back to the original names, by the way, and kept the new htaccess file in the root WP directory with the above code where it is. Did not get any ‘already exists’ warning when uploading either)

    So. Error logs. Let’s go see.

    Looks like it started sometime in July. (I haven’t updated lately — it’s been an overwhelming summer for me) so I picked a random point in late July to start copying. And when it starts giving errors about there not being any wp-includes directory, it LIES. (This happened after I attempted the manual reinstall.) The directory is there and fully intact. (And I made sure I was following the instructions to the letter on that manual, because that crap makes me paranoid, especially after chemo put holes in my memory banks and I screw up a bit easier.)

    So here’s the log. (It rolls downstairs, alone or in pairs, rolls over the neighbor’s dog, it’s great for a snack and fits on your back…)

    [23-Jul-2016 14:04:02 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\functions\actions.php on line 9
[23-Jul-2016 14:09:26 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\functions.wp-scripts.php on line 260
[23-Jul-2016 16:55:01 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[23-Jul-2016 16:55:18 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-admin\includes\media.php on line 16
[23-Jul-2016 16:58:57 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\functions.php on line 4571
[23-Jul-2016 18:01:31 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[24-Jul-2016 12:39:06 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[25-Jul-2016 09:28:59 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\admin\theme-definitions.php on line 2
[25-Jul-2016 11:02:08 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\admin\theme-options-visual-effects.php on line 10
[26-Jul-2016 03:06:45 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\random_compat\random_int.php on line 39
[29-Jul-2016 03:10:04 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\widgets\class-wp-widget-text.php on line 17
[29-Jul-2016 03:10:37 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[29-Jul-2016 03:43:06 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\template.php on line 518
[29-Jul-2016 05:26:26 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-admin\includes\image.php on line 25
[29-Jul-2016 05:27:41 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\functions.php on line 4571
[29-Jul-2016 16:58:40 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\l10n.php on line 902
[30-Jul-2016 23:56:37 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\locale.php on line 14
[30-Jul-2016 23:56:37 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\locale.php on line 14
[31-Jul-2016 00:13:58 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[31-Jul-2016 04:59:59 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\functions.php on line 4577
[01-Aug-2016 17:01:55 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\functions.php on line 4571
[02-Aug-2016 05:05:49 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\functions.php on line 4571
[02-Aug-2016 11:26:39 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[02-Aug-2016 12:54:13 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[02-Aug-2016 13:05:15 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[03-Aug-2016 00:27:21 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\version.php on line 7
[03-Aug-2016 00:50:50 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\template.php on line 518
[03-Aug-2016 00:50:52 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[03-Aug-2016 09:19:06 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\template.php on line 518
[03-Aug-2016 10:06:06 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[04-Aug-2016 10:20:36 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\cron.php on line 23
[04-Aug-2016 10:20:38 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\class.wp-scripts.php on line 18
[04-Aug-2016 10:29:31 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[05-Aug-2016 05:00:51 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\theme.php on line 476
[05-Aug-2016 05:51:19 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\admin\theme-options.php on line 10
[05-Aug-2016 05:51:31 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[05-Aug-2016 06:20:10 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\widgets\suffusion-subscription.php on line 30
[05-Aug-2016 07:10:09 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\media.php on line 41
[05-Aug-2016 07:11:25 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\template.php on line 518
[05-Aug-2016 07:38:53 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\class-http.php on line 21
[05-Aug-2016 08:35:27 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[05-Aug-2016 09:30:34 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\nav-menu.php on line 18
[05-Aug-2016 10:47:05 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\class-wp-widget.php on line 19
[06-Aug-2016 04:57:08 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-admin\includes\template.php on line 12
[06-Aug-2016 05:07:06 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\functions.php on line 4571
[06-Aug-2016 08:56:33 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\admin\theme-options-custom-types.php on line 2
[06-Aug-2016 09:33:50 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\script-loader.php on line 20
[06-Aug-2016 09:34:43 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\admin\theme-options-typography.php on line 10
[06-Aug-2016 11:38:45 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\plugins\akismet\wrapper.php on line 3
[06-Aug-2016 11:58:48 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\widget-areas.php on line 10
[06-Aug-2016 13:37:16 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\widgets\suffusion-widgets.php on line 9
[07-Aug-2016 05:00:13 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\functions.php on line 4571
[07-Aug-2016 19:51:04 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\widgets\class-wp-widget-links.php on line 17
[08-Aug-2016 05:45:06 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\pomo\mo.php on line 10
[09-Aug-2016 09:40:36 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\rest-api.php on line 15
[09-Aug-2016 17:08:55 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\functions.php on line 4571
[09-Aug-2016 18:01:49 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\update.php on line 24
[09-Aug-2016 18:01:59 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\plugins\akismet\akismet.php on line 35
[10-Aug-2016 08:10:12 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\l10n.php on line 556
[10-Aug-2016 10:24:09 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\class-wp-post.php on line 22
[10-Aug-2016 10:48:09 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[10-Aug-2016 13:45:05 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[10-Aug-2016 14:52:19 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[10-Aug-2016 16:59:16 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\l10n.php on line 902
[10-Aug-2016 17:03:20 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\l10n.php on line 895
[10-Aug-2016 18:56:56 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\admin\theme-options-typography.php on line 10
[11-Aug-2016 10:57:38 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\functions\template.php on line 14
[11-Aug-2016 11:23:45 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\header.php on line 8
[11-Aug-2016 12:03:20 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\widgets\suffusion-search.php on line 9
[11-Aug-2016 13:07:44 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[11-Aug-2016 13:11:47 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\revision.php on line 24
[11-Aug-2016 13:15:20 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\template.php on line 23
[11-Aug-2016 13:23:52 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[11-Aug-2016 13:24:08 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[11-Aug-2016 13:41:43 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\taxonomy.php on line 24
[11-Aug-2016 13:41:43 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\taxonomy.php on line 24
[11-Aug-2016 13:45:04 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\class-walker-category-dropdown.php on line 17
[11-Aug-2016 13:51:18 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\class-wp.php on line 8
[11-Aug-2016 13:51:49 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\author-template.php on line 23
[11-Aug-2016 13:52:04 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\bookmark-template.php on line 51
[11-Aug-2016 13:52:36 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\plugins\akismet\akismet.php on line 35
[11-Aug-2016 13:53:07 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\admin\theme-options-layouts.php on line 10
[11-Aug-2016 13:53:36 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\class.wp-scripts.php on line 447
[11-Aug-2016 14:16:00 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\class.wp-styles.php on line 18
[11-Aug-2016 14:16:24 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\widgets\class-wp-nav-menu-widget.php on line 17
[11-Aug-2016 14:18:35 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[11-Aug-2016 20:26:55 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[11-Aug-2016 22:10:37 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\widgets\suffusion-subscription.php on line 20
[11-Aug-2016 22:30:35 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[12-Aug-2016 02:59:31 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\functions\fonts.php on line 10
[12-Aug-2016 03:54:39 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\class.wp-scripts.php on line 18
[12-Aug-2016 03:58:55 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\widgets\suffusion-featured-posts.php on line 10
[12-Aug-2016 05:11:00 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\widgets\class-wp-widget-text.php on line 17
[12-Aug-2016 05:11:06 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\admin\theme-options.php on line 10
[12-Aug-2016 05:11:44 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\functions.php on line 4577
[12-Aug-2016 05:19:38 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\functions.php on line 4571
[12-Aug-2016 05:40:25 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\widgets\class-wp-widget-recent-posts.php on line 17
[12-Aug-2016 05:56:13 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\media.php on line 41
[12-Aug-2016 05:56:29 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\admin\theme-options.php on line 10
[12-Aug-2016 08:09:33 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\admin\theme-options-templates.php on line 10
[12-Aug-2016 08:09:33 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\widgets\suffusion-widgets.php on line 9
[12-Aug-2016 08:27:01 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\widgets\suffusion-twitter.php on line 10
[12-Aug-2016 12:25:46 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\widgets\class-wp-widget-archives.php on line 17
[12-Aug-2016 12:51:08 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\single.php on line 6
[12-Aug-2016 14:18:20 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-content\themes\suffusion\widgets\suffusion-query-posts.php on line 10
[12-Aug-2016 14:18:38 UTC] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\wp-db.php on line 1811
[14-Aug-2016 01:18:42 UTC] PHP Warning:  require(E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php): failed to open stream: No such file or directory in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21
[14-Aug-2016 01:18:42 UTC] PHP Warning:  require(E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php): failed to open stream: No such file or directory in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21
[14-Aug-2016 01:18:42 UTC] PHP Fatal error:  require(): Failed opening required 'E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php' (include_path='.;.\includes;.\pear') in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21
[14-Aug-2016 01:20:47 UTC] PHP Warning:  require(E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php): failed to open stream: No such file or directory in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21
[14-Aug-2016 01:20:47 UTC] PHP Warning:  require(E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php): failed to open stream: No such file or directory in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21
[14-Aug-2016 01:20:47 UTC] PHP Fatal error:  require(): Failed opening required 'E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php' (include_path='.;.\includes;.\pear') in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21
[14-Aug-2016 01:24:34 UTC] PHP Warning:  require(E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php): failed to open stream: No such file or directory in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21
[14-Aug-2016 01:24:34 UTC] PHP Warning:  require(E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php): failed to open stream: No such file or directory in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21
[14-Aug-2016 01:24:34 UTC] PHP Fatal error:  require(): Failed opening required 'E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php' (include_path='.;.\includes;.\pear') in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21
[14-Aug-2016 01:25:49 UTC] PHP Warning:  require(E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php): failed to open stream: No such file or directory in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21
[14-Aug-2016 01:25:49 UTC] PHP Warning:  require(E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php): failed to open stream: No such file or directory in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21
[14-Aug-2016 01:25:49 UTC] PHP Fatal error:  require(): Failed opening required 'E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php' (include_path='.;.\includes;.\pear') in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21
    Moderator James Huff

    (@macmanx)

    9 years, 8 months ago

    So here’s the log. (It rolls downstairs, alone or in pairs, rolls over the neighbor’s dog, it’s great for a snack and fits on your back…)

    So, like I mentioned, “if you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that specific time period.”

    Basically, the entirety of the error log is useless without knowing which entry corresponds to the 500 error.

    When you access the site, you’ll see the 500, and its cause will be recorded in the log at that moment. I need that entry, and only that entry.

    Thread Starter metathriving

    (@metathriving)

    9 years, 8 months ago

    Ack. Sorry. Having quite this much free access to the information regarding my website is new territory for me, so I wasn’t clear as to what I was supposed to look for where. (Ex-hubs owns it, I can do pretty much anything that doesn’t require top level admin access, which is a bit more than a standard webhost package deal. And in the past, most errors of that level were not usually something I had enough access to investigate or fix, or I was too lost in general and couldn’t find enough information to feel comfortable proceeding on my own. I’m entirely self-taught from the late ’90s onward, more daring with things on my side of the server that I know I can un-bork without it being a big crisis for someone else.)

    I read up a bit, and I think I’m looking at the right info now?

    2016-08-13 18:18:42			PHP Warning: require(E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php): failed to open stream: No such file or directory in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21				php_error
2016-08-13 18:18:42			PHP Fatal error: require(): Failed opening required 'E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php' (include_path='.;.\includes;.\pear') in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21				php_error
2016-08-13 18:18:42	8.29.198.25	500	GET /wordpress/feed/ - HTTP/1.1		Feedly/1.0 ( http://www.feedly.com/fetcher.html; like FeedFetcher-Google)	286 	IIS access
2016-08-13 18:20:46	66.249.69.8	500	GET /wordpress/october-26-guest-blogger-jennifer-eisenbart/ - HTTP/1.1		Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.96 Mobile Safari/537.36 (compatible; Googlebot/2.1; http://www.google.com/bot.html)	267 	IIS access
2016-08-13 18:20:47			PHP Warning: require(E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php): failed to open stream: No such file or directory in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21				php_error
2016-08-13 18:20:47			PHP Warning: require(E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php): failed to open stream: No such file or directory in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21				php_error
2016-08-13 18:20:47			PHP Fatal error: require(): Failed opening required 'E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php' (include_path='.;.\includes;.\pear') in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21				php_error
2016-08-13 18:24:34			PHP Warning: require(E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php): failed to open stream: No such file or directory in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21				php_error
2016-08-13 18:24:34			PHP Warning: require(E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php): failed to open stream: No such file or directory in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21				php_error
2016-08-13 18:24:34			PHP Fatal error: require(): Failed opening required 'E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php' (include_path='.;.\includes;.\pear') in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21				php_error
2016-08-13 18:24:34	138.201.86.218	500	GET /wordpress/xmlrpc.php - HTTP/1.1		yacybot (-global; amd64 Linux 3.16.0-4-amd64; java 1.8.0_101; Europe/en) http://yacy.net/bot.html	286 	IIS access
2016-08-13 18:25:48	65.19.138.34	500	GET /wordpress/feed/ - HTTP/1.1		Feedly/1.0 ( http://www.feedly.com/fetcher.html; like FeedFetcher-Google)	286 	IIS access
2016-08-13 18:25:49			PHP Warning: require(E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php): failed to open stream: No such file or directory in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21				php_error
2016-08-13 18:25:49			PHP Warning: require(E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php): failed to open stream: No such file or directory in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21				php_error
2016-08-13 18:25:49			PHP Fatal error: require(): Failed opening required 'E:\vhosts\METATHRIVING.COM\httpdocs\wordpress/wp-includes/load.php' (include_path='.;.\includes;.\pear') in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-settings.php on line 21

    What’s really weird to me though, that’s the only bit of 500s, and just to make sure Firefox wasn’t being super-stubborn with the cache, I booted up all my alternate browsers, none of which I’ve visited the site or blog with since updating them after upgrading to Win10, and I’m getting the same problem.

    But I’m looking at the log files as recently as today, and I have entries like this?

    2016-08-14 09:38:41 202.46.55.151 200 GET /wordpress/the-trouble-with-survivor-and-the-lack-of-boundaries/ - HTTP/1.1 Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.93 Safari/537.36 483

    So… I’m not able to access WP through any means, not even CPanel, through any browser, getting a 500 error every time, but the only 500 I’m seeing in what I think is the correct log is for that time period in the first code box, which is yesterday. And there’s plenty of 200 log records for blog entries as recently as today. Shouldn’t those entries be inaccessible in general?

    If something is impossibly screwy here and it’s going into ‘nuke the site from orbit’ territory, I’ll bite that bullet, especially if there’s a way to run a backup through FTP of entries/images. If not, I’ll just cry a lot and do it anyway and chalk it up as a lesson hard-learned, and see how much the Wayback Machine can give me. (I’ve never been into blogging and WP in the past, never had much to talk about to the general population.)

    Thread Starter metathriving

    (@metathriving)

    9 years, 8 months ago

    Nevermind about the FTP backup for the blog – I just checked, that takes the phpMyAdmin database. I used to play with that all the time for something else years ago. I’ll find it. Found the images easily and can nab those.

    Moderator James Huff

    (@macmanx)

    9 years, 8 months ago

    Sounds like some core files are missing.

    Try downloading WordPress again, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and delete then replace your copies of everything except the wp-config.php file and the /wp-content/ directory with fresh copies from the download. This will effectively replace all of your core files without damaging your content and settings.

    Some uploaders tend to be unreliable when overwriting files, so don’t forget to delete the original files before replacing them.

    Thread Starter metathriving

    (@metathriving)

    9 years, 8 months ago

    … I think the server needs a young priest, an old priest, and a lot of salt. Or something. I did exactly as you said. I deleted the zip and zip folder I’d downloaded the other day, re-downloaded it, unzipped, logged into FTP, deleted the files/directories you said, and uploaded fresh copies once they were gone.

    Here’s a screencap of my FTP and directory.

    I did not delete the “blogs” or “tmp” folders because there weren’t any corresponding ones in the unzipped folder to replace them, and you didn’t say anything about those, so I didn’t touch them. I did not touch the .htaccess file, the content folder, or the wp-config file either. Everything else on the right side of the FTP? Deleted. Then I uploaded everything BUT the content folder and wp-config file from the left side, the freshly unzipped WP download, over onto the server. (You’re looking at the screenshot of everything post-transfer at that point.)

    I’m still 500’ing. There’s no new 500 log entries, I forced a refresh of it, I changed it to live updates, kept accessing (or trying to) the blog, there’s new 200s since this afternoon, and… I can’t even.

    My mother in law just blew up the household and it’s bedtime and I want to stab everything in the face. Bleh. *eyetic* I’ll tackle this thing more tomorrow if you or anyone else has more suggestions.

    (and people, please to be not sending me emails telling me you can fix this for more than I spend a week on groceries, you want money, I have none, go away.)

    Moderator James Huff

    (@macmanx)

    9 years, 8 months ago

    Have you been using any plugin-based or server-side caches?

    Thread Starter metathriving

    (@metathriving)

    9 years, 8 months ago

    As far as I’m aware, no. This is actually the first I’d heard about that. (My plug-ins are still disabled, by the by) and after Googling around looking into server-side caches, I cannot find anything even remotely familiar. I went through everything in every category of my CPanel, and did not hit on anything, even ran a search for ‘cache’, nothing. Where and what do I need to look for to check for this? This is new territory for me. To try and make it easier, here’s a screencap of my specific CPanel, if there’s any particular area I should look at (and possibly screencap as well) for this.

    I use postimg for these because I have hotlinking disabled. As much fun as it was substituting Goatse and Tubgirl when I found people hotlinking and using my bandwidth, now that I can control that, this is more mature 🙂

    Moderator James Huff

    (@macmanx)

    9 years, 8 months ago

    Setting up a cache is very involved, so if you don’t recall setting on up, you probably don’t have one.

    1. Are you using Cloudflare?

    2. Can you switch to PHP 5.6 or 7.0 in cPanel? If so, please see if that makes any difference.

    Thread Starter metathriving

    (@metathriving)

    9 years, 7 months ago

    … I am sorry it took two days to get back to you. I never received a new reply notif. At any rate, an emergency situation (a good kind, but still very last minute NEED RIGHT NOW) popped up literally as I was about to go to sleep and had me out of town 16 hours. 6 of those hours were spent driving. So there would have been nothing from me yesterday anyway. (Tho I ended up on the Iron Throne for a while.)

    Anyhow. Down to business.

    1. No. It’s set up with Plesk.

    2. Yes. I did so – version 7.0.4 now. and the screen did change to give me… well,
    this is what’s up.

    I clicked on the 4.6 update link, and was given a list of these errors. Tried a few more times, and the errors just repeat.

    The WordPress installations were updated with errors:

    Installation "My CMS": PHP Fatal error: Uncaught Error: Call to undefined function apply_filters() in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\load.php:317 Stack trace: #0 E:\Parallels\Plesk\Additional\wp-cli\php\utils-wp.php(22): wp_debug_mode() #1 E:\Parallels\Plesk\Additional\wp-cli\php\wp-settings-cli.php(59): WP_CLI\Utils\wp_debug_mode() #2 E:\Parallels\Plesk\Additional\wp-cli\php\WP_CLI\Runner.php(862): require('E:\\Parallels\\Pl...') #3 E:\Parallels\Plesk\Additional\wp-cli\php\WP_CLI\Runner.php(810): WP_CLI\Runner->load_wordpress() #4 E:\Parallels\Plesk\Additional\wp-cli\php\wp-cli.php(21): WP_CLI\Runner->start() #5 E:\Parallels\Plesk\Additional\wp-cli\php\boot-fs.php(24): include('E:\\Parallels\\Pl...') #6 {main} thrown in E:\vhosts\METATHRIVING.COM\httpdocs\wordpress\wp-includes\load.php on line 317
    Moderator James Huff

    (@macmanx)

    9 years, 7 months ago

    Hm, that sounds like a problem with Plesk’s updater. Try updating manually: https://codex.wordpress.org/Upgrading_WordPress_Extended

    Thread Starter metathriving

    (@metathriving)

    9 years, 7 months ago

    That didn’t work either. I swear I followed that correctly, and tried a few different ways to access my admin panel, but quoth the server 500.

    Moderator James Huff

    (@macmanx)

    9 years, 7 months ago

    After manually upgrading, what is the recorded error in the log now when the 500 is triggered?

    Thread Starter metathriving

    (@metathriving)

    9 years, 7 months ago

    … it’s the same as before. Same date stamp, same error, same bat time, same bat channel.

    same as in this post.

Viewing 15 replies - 1 through 15 (of 26 total)
1 2

The topic ‘500 Internal Error, troubleshot everything’ is closed to new replies.