"random" internal server errors

[ottmance]

Click the search icon in upper right. Search for the term HUMAN. Internal server error. Search for the term STUPID, works fine.

Try to get to the url http://8e3.070.myftpupload.com/tag/lean-six-sigma, internal server error.

http://8e3.070.myftpupload.com/tag/leadership/ and this will work fine.

Install the stock 2013 theme and the above things will work fine. Note its just a theme change, no need to disable any plugins, the them alone will fix it.

Theme and framework are all up to date.

Thoughts?

Chuck

[David Martin – Support]

Hi Chuck,

Please open your wp-config.php file and add this: define('WP_MEMORY_LIMIT', '256M');

Thanks,
David

[ottmance]

added to the wp-config file and tried again. No change.

Contacted my web host support and was told not to put it there, because it would break things, but to put it in the php.ini file.

Added this to php.ini

memory_limit = 256M ; Maximum amount of memory a script may consume (default 64MB)

there was no change. Added the setting back to the wp-config file as well, no change.

Found a reference to adding php_value memory_limit 256M to the .htaccess file and that setting caused the whole site to break.

Other thoughts?

Chuck

[Rui Guerreiro – SUPPORT]

Hi,
Those are 2 different things, 1 is the php memory and the other one the WordPress memory.
Can you check in the server error logs what is causing that internal server error? The information should be there.

-Rui

[ottmance]

Added

define('WP_DEBUG', true);
define( 'WP_DEBUG_LOG', true );

to the wp-config file and all I see in the debug.log file is

[18-Oct-2016 13:33:00 UTC] PHP Notice: Constant WP_MEMORY_LIMIT already defined in /home/content/p3pnexwpnas10_data01/74/2854374/html/wp-config.php on line 99
[18-Oct-2016 13:34:12 UTC] PHP Notice: Constant WP_MEMORY_LIMIT already defined in /home/content/p3pnexwpnas10_data01/74/2854374/html/wp-config.php on line 99

First instance is when I loaded the page, second is when I used the search function to search for the term HUMAN. I might add here that in the backend on the post page I can search for the same term without issue.

Chuck

[Rui Guerreiro – SUPPORT]

it seems you have the same line of code in different files. You need to remove the WP_MEMORY_LIMIT line of code from the php.ini

Can you try to activate the default WordPress theme and do the same search to see what happens.

-Rui

[ottmance]

Removed php.ini file entirely, there was only that one line in it. No help.

As stated in the initial request it works just fine with the stock 2013 theme.

Chuck

[David Martin – Support]

The errors are informing you, you have two constants defined WP_MEMORY_LIMIT.

Better add your FTP as it seems you host is unwilling to help you out.

– David.

[ottmance]

This reply has been marked as private.

[ottmance]

Anything on this guys?

Chuck

[Rui Guerreiro – SUPPORT]

Hi,

Tried everything I could but with no luck.
Can you check in your cPanel if your there the error logs for this 500 Internal server error.

Also ask your hosting support for the error description of this 500 error.

-Rui

[ottmance]

Well I don’t have access to any of the server logs so I’m not sure how much more help I’m going to be on this. Since I’m on a shared hosting environment I can understand why I can’t see the logs. The support guy I was talking with was going to see if he could escalate this to the server admin staff to see if the can look into the log files and see if there’s anything in there regarding this error that we’re seeing but right at this point I’m not feeling hopeful.

Chuck

[Rui Guerreiro – SUPPORT]

hhumm I have a hostgator account that is also shared hosting and I can see the error logs in a specific option in the CPanel.
Let’s wait for their reply.

We don’t have any similar situation and it doesn’t make any sense why it only break with that word. In last resort try to install the theme in new sub domain in a fresh WordPress installation.

-Rui

[ottmance]

Well it behaves in the exact same manner on my production site as it does in my sandbox site. I’ll also add that my production site isn’t running the current version of the them/framework either. I’ve been experimenting with trying to drag my live database over on to a local XAMPP setup and see what I get but am not having much luck getting it to go. I was debating if I could be looking at some kind of database issue but since things work ok with the WordPress 2013 theme I kind of ruled that out. Just at a loss here.

Chuck

[ottmance]

and if this help make it more or less sense, this link will die with an internal server error as well

http://8e3.070.myftpupload.com/body-of-knowledge/page/6/