WordPress MU

Hi all,
I just updated to WPmu 2.7 SVN, and everything was working fine, but all of a sudden, one of the blogs just stopped loading, it just loads a blank page, I cannot even access wp-admin for that blog, it also loads blank. I have tried nearly everything:

1- Deactivate/Re-activate plugins
2- Update all plugins
3- Deleted plugins from server
4- Deleted all mu-plugin files (including BuddyPress)
5- Disabled and enabled all themes
6- Deleted and re-installed the blog's theme
5- Deleted all WPmu 2.7 files and re-copied them
6- Deleted WPmu 2.7, replaced with WPmu 2.6.5 files
7- Deleted 2.6.5 files and replaced with 2.7 SVN
8- Cleared Cache, restarted server
9- Reviewed .htaccess file ( http://pastebin.com/m586bc4e8 )
10- Deleted wp-config.php and re-installed

I don't know what else to do, it was working this morning, and then it just stopped, please help!
I'm now checking the server error logs to see if anything shows up.

WPmu version:
SVN 2.7

Faulty blog:
http://avatar.iamzaks.com

Working blog:
http://dieguillo.iamzaks.com

Main site:
http://iamzaks.com

Thanks in advance

please, someone, this is urgent

Anything in your error log?

Did you look at that blog's db files?

VentureMaker, there is a repeating error, http://pastebin.com/m1600d53c

andrea_r, what am I looking for there?

This means that not enough memory is allocated for php on your server. Raise php memory limits.

but that should not be causing this problem, it's another problem, isn't it?

Are you by any chance running buddypress and sitewide tags?

And have you disabled the buddypress recent posts widget?

Im running only BuddyPress, and the single post widget was not called in that blog. I tried deleting buddypress and all other plugins, to no avail.

I contacted my hosting's support regarding the DNS wildcard configuration and got this answer:

"Looking at the DNS for the domain iamzaks.com I can see that you do have a wildcard setup properly for this domain. I believe the reason you are currently receiving this blank page is because you do not have a physical hosting environment for the subdomain avatar.iamzaks.com. Once the domain is created correctly in Plesk the subdomain should no longer display the blank page."

Should I setup a sub-domain for the blog? would that do any difference, I thought WPmu did not need this

Your host is wrong. tell him you're running WPMU and the wildcard handles all requests for subdomains. None need to exist on the server. MU then looks it up in the db and serves the right files.

Check the db and look over that blog's tables to see any differences between it and one that works. make sure plugins on that blog have all been disabled.

What did the error logs say?

this is going to sound like slaughter, but I tried something and I pinpointed the error to a single table.

I went to my phpMyAdmin, and deleted all tables that where not used anymore, like those left behind by several plugins. The non working blog ID is 2. That did not fix the problem, I then noticed that the wp_2_options was different than the wp_26_options (the blog that works) so, I manually tried to correct as much as I could, but that did not fix it either.
(Let the butchery begin...)

I went to the wp_blogs table and changed the Blog ID from 2 to 26, then, the address http://avatar.amzaks.com was accessible, of course, with the other blog's posts (ID 26).

Then I renamed wp_2_posts to wp_26_posts, and all my posts where now being displayed, same for wp_2_comments.

wp_2_options however, when renamed to wp_26_options loaded the blank page. So I believe the error is a misconfiguration in the BlogID 2 wp_2_options.

I noticed that wp_2_options goes on for 155 pages of 250 entries each, totaling 38,750 entries in this table, out of which, I can only see copies of one entry:

19941 0 cron a:5:{i:1230995297;a:1:{s:10:"polls_cron";a:1:{s:32...

now, what could this be? should I delete all of them manually?

Edit: there is another entry: doing_cron

Yeah, delete all the duplicate blog options. Sort by option name and nuke all those cron ones. the look like they are related to a poll plugin. they certainly aren't default ones.

I've noticed some stuff like that too before, although not that many entries. It's like a hiccup or something.

there are many different duplicate entries. A couple of them poll related, I am organizing them by option_ID, that should tell me which where the first ones to be created.

I already deleted about 25,000 cron and doing_cron entries...

we will see

edit:

so far, problems with repeated:
cron
doing_cron
update_plugins
wpsupercache_gc_time
tla_last_update
sm_status

uninstall_plugins
update_core
update_themes

I will keep posting as they appear, there can't be many more, over 30,000 deleted

Well, 38,457 deleted entries later, I have a working blog!
Thank you very much andrea_r and all who helped!

Hi mikeboy3,

Glad to hear you got things working again.

Out of interest, which version of WPMU were you running before you tried to upgrade to WPMU 2.7 trunk?

A few months ago I came across a similar problem with duplicate wp_option records, however the problem was fixed in WPMU 2.6.2.

I'm wondering whether the duplicate records were introduced before the upgrade to 2.7, or as a result of the 2.7 upgrade.

James

jamescollins: I was using 2.6.5 before the upgrade.

I just checked my wp_2_options again, and its packed with:
cron
doing_cron
update_core

at least 400 of them... It's starting again. There must be some cron process triggered in this blog that just keeps looping!

here is the option_value for each:

cron: http://pastebin.com/m472ed229
doing_cron: 0
update_core: http://pastebin.com/m169be19

Active mu-plugins:
Buddypress 1.0b
Incsub Support Module
Google Analytics for WPmu (Rafik_ga)
wp-super-cache
wp_ozh_whoseesads

Active Plugins:
Akismet 2.2.3
NextGEN Gallery 1.0.2
Wordpress Video Plugin 0.69
WP-Polls 2.40
WP-SWF Object 2.0
WP125 1.2.1

How can I check to see which one is causing the conflict?

mikeboy3,

What is the value of the autoload columns (yes or no)?

Are the duplicate wp_2_option records also occurring in the other blogs in your WPMU installation?

If it happens in all of them, then it's probably a mu-plugin causing it.

If it is only happening in blog id 2, which plugin(s) are only activated in blog id 2 and not activated in the other blogs?

Deactivate all the ones in plugins. rename or remove the ones in mu-plugins. Add them back one at a time, wait, check the db.

I believe the problem is the wp-super-cache plugin with the blog, but it is only on that blog in particular, the rest seem fine.

now the entry: wpsupercache_gc_time is part of the repeated ones. Over 1400 by now...

jamscollins, autoload value is "yes" in all entries, It does not happen in all of them, just the BlogID 2, I'm trying what andrea_r suggested, testing one by one.