my database keep rebooting after 4.2 upgrade

Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

If that does not resolve the issue, try switching to the Twenty Fourteen theme to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via FTP or SFTP, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

If that does 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 FTP or SFTP and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your FTP or SFTP 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 time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

Problem still persist and I failed to see which plugin is causing the issue. I don’t think its theme issue since I can easily crash my sqldatabase by just refresh multiple add-new post window at once, I’m running a pretty advance server, this couldn’t be possibly happening. OMG, help!

Ok, so how much of the above did you actually try? Please list it all out, and the results from each test.

I first deactivated all my plugin and rename .htaccess to htaccess, and changed the theme to default theme (twenty-fifteen). but the error still happening, wow. I havent even start reactivate my plugins yet.

I keep refreshing 10 add-new-post windows

the error keep showing up

[Wed May 13 05:06:02 2015] [warn] [client 108.162.254.23] mod_fcgid: can’t apply process slot for /var/www/cgi-bin/cgi_wrapper/cgi_wrapper
[Wed May 13 05:06:02 2015] [warn] [client 108.162.219.121] mod_fcgid: can’t apply process slot for /var/www/cgi-bin/cgi_wrapper/cgi_wrapper, referer: https://*************/wp-admin/post-new.php

after renamed the .htaccess

the error became:

[Wed May 13 05:03:38 2015] [error] [client 173.245.52.147] File does not exist:

I even increase my memory limit to 1000m and execution time to 900secs.

I run php as FAst CGI application, should I change it to Apache module? I’m not sure if its the issue here.

I have complete control of the server.

php verison 5.33

I switched to Apache module, the error somehow disappear. If the latest verison not compatible with fastcgi, its going to be a problem because its one of the fastest, newest verison runs for php.

After I switched to Apache module, I found out that my latest post showing on my homepage is 3 hours ago even I deleted the cached files, whats wrong?

Never mind, it was the super cache issue.

If the latest verison not compatible with fastcgi, its going to be a problem because its one of the fastest, newest verison runs for php.

Actually, not true. FastCGI has been around since the mid-1990s. In a basic sense, it’s an emulation environment designed to remove overhead, but as with most emulation environments, it doesn’t always work that way. It’s not a particular version of PHP.

Personally, I prefer to run PHP as it was intended, as an Apache module.

WordPress should work just fine with FastCGI though, so it’s possible that it is not configured properly on your server.