[wp-testers] Upgrade to 2.3-whitescreen at step 1 - too big post2cat table?

[Evil ZEN Scientist]

Boris

I'm running with PHP at 384MB right now; 32MB is pretty slim.

-----Original Message-----
From: wp-testers-bounces at lists.automattic.com
[mailto:wp-testers-bounces at lists.automattic.com] On Behalf Of Boris Anthony
Sent: Friday, October 12, 2007 2:08 PM
To: wp-testers at lists.automattic.com
Subject: Re: [wp-testers] Upgrade to 2.3-whitescreen at step 1 - too big
post2cat table?

thank you zen-san

yeah i went peeking into the logs as I waited. It does seem to be  
bumping up into the 32M PHP limit. Having the admin up that for us  
and see if that works. Will report back.

thnx

B.


On 12-Oct-07, at 3:36 PM, Evil ZEN Scientist wrote:

> How's your PHP configured for memory?
>
> Anything showing in the apache error logs?
>
> -----Original Message-----
> From: wp-testers-bounces at lists.automattic.com
> [mailto:wp-testers-bounces at lists.automattic.com] On Behalf Of Boris  
> Anthony
> Sent: Friday, October 12, 2007 1:29 PM
> To: wp-testers at lists.automattic.com
> Subject: [wp-testers] Upgrade to 2.3-whitescreen at step 1 - too big
> post2cat table?
>
> Hi gang,
>
> We're running a test upgrade of globalvoicesonline.org, from 2.2 to  
> 2.3.
> Within about 5 seconds after hitting "Upgrade Wordpress" we get
> either a totally blank screen or just the head part of what should be
> shown (WP logo, grey back ground, then nothing) (We've started over a
> few times heh)
>
> Peeking into the database, the 3 new terms tables are created, terms
> and term_taxonomy are properly populated with all 347 previous
> Categories, but term_relationships is empty.
>
> our post2cat table counts 169,552 records (just over 10meg). I am
> guessing it's choking on that? It isn't timing out, to be clear. It
> just dies unceremoniously, I suspect, as soon as it considers trying
> to convert the post2cat data. ;)
>
> any insights/wisdom appreciated!
>
> B.
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Scanned with Copfilter Version 0.84beta2 (ProxSMTP 1.6)
> AntiSpam:  SpamAssassin 3.1.8
> AntiVirus: ClamAV 0.91rc2-exp/4533 - Fri Oct 12 04:59:29 2007
> by postmaster at gonetoutah.com
>
>
>
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Scanned with Copfilter Version 0.84beta2 (ProxSMTP 1.6)
> AntiSpam:  SpamAssassin 3.1.8
> AntiVirus: ClamAV 0.91rc2-exp/4533 - Fri Oct 12 04:59:29 2007
> by postmaster at gonetoutah.com
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Scanned with Copfilter Version 0.84beta2 (ProxSMTP 1.6)
> AntiSpam:  SpamAssassin 3.1.8
> AntiVirus: ClamAV 0.91rc2-exp/4533 - Fri Oct 12 04:59:29 2007
> by postmaster at gonetoutah.com
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers

_______________________________________________
wp-testers mailing list
wp-testers at lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-testers

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.84beta2 (ProxSMTP 1.6)
AntiSpam:  SpamAssassin 3.1.8
AntiVirus: ClamAV 0.91rc2-exp/4533 - Fri Oct 12 04:59:29 2007
by postmaster at gonetoutah.com




=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.84beta2 (ProxSMTP 1.6)
AntiSpam:  SpamAssassin 3.1.8
AntiVirus: ClamAV 0.91rc2-exp/4533 - Fri Oct 12 04:59:29 2007
by postmaster at gonetoutah.com

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.84beta2 (ProxSMTP 1.6)
AntiSpam:  SpamAssassin 3.1.8
AntiVirus: ClamAV 0.91rc2-exp/4533 - Fri Oct 12 04:59:29 2007
by postmaster at gonetoutah.com