macaddict

OK… I had this same 500 issue with upgrading from 2.2.x to 2.3.x before, and got so frustrated, I dropped it and stayed 2.2.x

So here I am again with a new build of 2.3.3 and I still cannot get either an upgrade or raw install to work.

I have expanded the memory requirements for php via htaccess, which does nothing. I still get the 500 error.

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

# php_flag display_errors on
php_value memory_limit 16M

As per phpinfo(), my server is running:

FreeBSD 6.1-STABLE FreeBSD 6.1-STABLE #0:

mySQL:

Server version: 4.0.26

As others have had, I have no access to the raw log files, as this is a shared hosting account. The logs I see are just access logs, and give no reason as to the error.

Now, I realize this is a server issue, as my local Macintosh displays the correct screens via HyperEdit, (macs render php almost natively) but what could possibly be preventing it from working correctly on a unix server? Does mySQL have to be a newer version?

Any help/guidance is appreciated, as I would like to keep up with the most current builds. I have a number of other websites that need to be taken to current builds.

I don’t know what to do. Apparently it “might” be something to do with this “Suhosin” patch to PHP, but I am not a server admin with that type of training to know what/where/how thats applied. Nor do I have full access to tweak the server to my needs, being as this is a shared hosting reseller account.

In that other post, KentW reported:

The previously cited google search mostly centers around reports for PHP 4.x, citations against PHP 5.x show the issues turned out to be with the script from the ones I read.

Which indicates that the “Suhosin” patch problem should not be happening, being as the server I am using is on PHP 5.x.

So I guess I will have to wait until a future WP version comes out, and try installing that, hoping that this intermittent issue is fixed. Reading other posts in support, other people are receiving “Internal Server Errors” intermittently on this new 2.3 version, even after a successful install.

My older versions of WordPress work fine, but I was interested in staying with the most current versions of WP.

*sigh*

(Oh… and this is a Unix server, not windoze, so there’s no php.ini file I can edit)

Yes.. I am receiving a similar error here on even a BRAND NEW install of 2.3 with a NEW database –

Internal server error, Please contact the host blah blah blah…

I have done over 2 dozen installs of previous WordPress packages for clients and for myself, and have never had a single issue like this with the install.

After contacting the host, here is the details of the error in the server log that it is generating:

ALERT – canary mismatch on efree() – heap overflow detected (attacker ‘**.**.***.*’, file ‘/###/local/home/macsplac/*********.com/NEW/wp-includes/taxonomy.php’, line 11)
[Tue Oct 9 07:29:42 2007] [error] [client **.**.***.*] Premature end of script headers: /###/local/home/macsplac/*********.com/NEW/wp-admin/install.php

The hosting I am using meets the requirements for the install, and I even went into my .htaccess file and bumped the memory used for php to 16mb, and I get the same error.

Yeah.. I had similar problems here after upgrading. The visual editor used to work, then stopped working after upgrading to 2.1.3

I swept back through my plugins, turning them all off, then one by one back on, and now things are normal again.

Not running any off the wall plugins.. just:
Spam Karma
Widgets
wp-polls + widget
recent-comments
subscribe-to-comments

Strange that just turning them on and off would fix it. Hope it stays fixed, but I will repost if it ‘breaks’ again…

looks pretty cool, although slow loading even on DSL 6.0 …. loaded up in blocks and pieces… just FYI… But all in all, a decent look for wordpress…