A few hundred notices in error log..
My hostingprovider had to reboot my VDS three times today, because my (dev) site had all memory in use..
For some reason I'm getting a few hundred notices/errors (rules in the error log) per page view..
A whole lot like these:
PHP Notice: unserialize() [function.unserialize]: Error at offset 0 of 22 bytes in ... referer: ...
And a whole lot like these:
Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: ...
Because I just installed the wp super cache plugin (last page-load) that's being referred to in almost every rule.
Already tried it with the mu-plugin folder empty and with the plugins folder empty. Both didn't give the 'magic answer' (so it seems to be in WPMU itself..)??
Does anyone know what's causing it and how to fix this? I have 512mb memory at my disposal with my VDS and just the main blog and one demo blog (which I made after testing btw), so it's not like the website is being visited too much (just me, because it's still in-dev-stage).
Everyday at WPMU DEV we help hundreds of WP Users. Become a member today to:
- Download 250+ Premium Plugins and Themes
- Get unlimited support from WordPress Experts
- Get help with your WordPress or BuddyPress projects
Help & Support from WPMU DEV members and staff
Keeper of the Dark Chocolate
We discussed this a few days ago on the mu forums:
http://mu.wordpress.org/forums/topic.php?id=10567
There's a previous thread as well:
Keeper of the Dark Chocolate
If you;re running buddypress as well, do note that there's an outstanding issue with that and Donncha's site wide tag plugin that may be the cause of this:
Get personal, comprehensive and timely support and assistance
from WordPress Experts
hmm.. didn't find those, because the main-problem is the unserialize errors (the LimitInternalRecursion ones not as much as the unserialized ones, now with super-cache installed - don't know if it's related though - don't have the limitinternalrecursion ones anymore).
And no, I'm not running buddypress.
Btw, also changed theme to the default one to see if it had something to do with it, but didn't help either..
Keeper of the Dark Chocolate
Next step would be the loglevel change to see what comes up.
edit: You're not getting a line number or file name for the first error, are you? There's a ton of those but they always have a file attached.
here are a few lines:
[Thu Jan 08 17:14:25 2009] [error] [client ipaddress] PHP Notice: unserialize() [function.unserialize]: Error at offset 0 of 22 bytes in /var/www/vhosts/domain.com/httpdocs/wp-includes/functions.php on line 342, referer: http://domain.com/
[Thu Jan 08 17:14:25 2009] [error] [client ipaddress] PHP Notice: unserialize() [function.unserialize]: Error at offset 0 of 12 bytes in /var/www/vhosts/domain.com/httpdocs/wp-includes/functions.php on line 342, referer: http://domain.com/
[Thu Jan 08 17:14:25 2009] [error] [client ipaddress] PHP Notice: unserialize() [function.unserialize]: Error at offset 0 of 22 bytes in /var/www/vhosts/domain.com/httpdocs/wp-includes/functions.php on line 342, referer: http://domain.com/
[Thu Jan 08 17:14:25 2009] [error] [client ipaddress] PHP Notice: unserialize() [function.unserialize]: Error at offset 0 of 12 bytes in /var/www/vhosts/domain.com/httpdocs/wp-includes/functions.php on line 342, referer: http://domain.com/
[Thu Jan 08 17:14:25 2009] [error] [client ipaddress] PHP Notice: unserialize() [function.unserialize]: Error at offset 0 of 22 bytes in /var/www/vhosts/domain.com/httpdocs/wp-includes/functions.php on line 342, referer: http://domain.com/
It's all in wp-includes/functions.php or wpmu-functions.php. Function is get_option and get_blog_option but since those files are wp-core I have no idea where the real error is happening..
Keeper of the Dark Chocolate
I was hoping the error would be occurring somewhere where we could see when it was being kicked out but, just our luck, it's where the function starts.
So much for that idea.
Get personal, comprehensive and timely support and assistance
from WordPress Experts
yup, that's what I thougt too.. Guess I'll just backup what I have on the server now and retry it with a fresh install (and first see what the fresh install says).
Keeper of the Dark Chocolate
And I don't see anything right off on the normal trac:
http://trac.wordpress.org/search?ticket=on&changeset=on&wiki=on&q=unserialize&noquickjump=1&page=1
Keeper of the Dark Chocolate
Have you tried the "Turn off all plugins and see if it still happens" route yet?
Yeah, did that. but didn't help.. Already reinstalled wpmu btw. No errors, but when I reinstalled my custom theme, I got a whole bunch of errors again (those unserialized ones). Find that a little weird, since I also tried that with the last install (use the default theme instead of my custom one), but perhaps that's not the only issue.
I'm trying to figure out where all those unserialized errors are coming from (still no luck) and hope it's fixed soon :)
Get personal, comprehensive and timely support and assistance
from WordPress Experts
Found out that the errors went away when I deleted the functions.php
With commenting every function out (one at a time) I found out that the logging stopped once I deleted error_reporting(E_ALL); ini_set('error_reporting', E_ALL); from that file..
Still don't know what it is that triggered those errors (went through every file in my theme and found nothing that looked weird)..
Keeper of the Dark Chocolate
I'm not in a position to check but I could have sworn that you can set that in the wp-config.php file:
