Updated to 3.2, seems ok – but errors in server logs

  • Resolved GFCphotog

    (@gfcphotog)


    13 years, 4 months ago

    After upgrading to 3.2 last night (seemed to go quite well), I’m seeing one old friend and some new warnings/errors in the server logs. The “RewriteCond” warning I’ve seen forever, but the others are new. Is this something expected?

    Thanks,
    Tim
    Log entries (this would be easier if I could attach a file – hint, hint):
    /home1/{…}/public_html/wp-admin/error_log:
    [10-Jul-2011 05:18:31] PHP Warning: implode() [function.implode]: Invalid arguments passed in
    /home1/{…}/public_html/wp-content/plugins/wp-super-cache/wp-cache.php on line 2443
    [10-Jul-2011 05:18:31] PHP Warning: implode() [function.implode]: Invalid arguments passed in
    /home1/{…}/public_html/wp-content/plugins/wp-super-cache/wp-cache.php on line 2444
    [10-Jul-2011 05:18:31] PHP Warning: Cannot modify header information – headers already sent by (output started at
    /home1/{…}/public_html/wp-content/plugins/wp-super-cache/wp-cache.php:2443) in /home1/{…}/public_html/wp-includes/pluggable.php on line 897

    MAIN error_log:
    [Sun Jul 10 09:50:10 2011] [warn] RewriteCond: NoCase option for non-regex pattern ‘-f’ is not supported and will be ignored.
    [Sun Jul 10 09:50:11 2011] [error] [client 124.115.6.16] 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.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Force flush your cache.

    Thread Starter GFCphotog

    (@gfcphotog)

    Cache was flushed last night after the upgrade, but I’ll try again.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    I’ve tagged this for the dev. It maybe is a plugin conflict.

    Thread Starter GFCphotog

    (@gfcphotog)

    After flushing again this morning the errors haven’t repeated again, but it seemed to be on a long cycle so I”ll check in again in the morning.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    It could be your server held on to some files…

    The PHP warning you’re seeing is on an implode of the $wp_cache_mobile_browsers and $wp_cache_mobile_prefixes arrays. For some reason they’re not set. Disable mobile support in the settings page and that problem will go away. If you need mobile support you’ll need to debug it yourself unfortunately.

    I’m not sure why you’re getting the NoCase warning but you can edit your .htaccess and remove the [NC] on the RewriteCond lines of the Supercache rules.

    Thread Starter GFCphotog

    (@gfcphotog)

    Thanks, it seems it is the mobile support as I can force an error when accessing the site with a mobile device as soon as I switch on the Mobile Theme switch at the bottom. Of the errors I’ve seen, only one remains:
    PHP Fatal error: Call to a member function get() on a non-object in /home1/{…}/public_html/wp-includes/cache.php on line 93

    This one is sufficient to prevent the mobile style from being used. It looks like there are some caching configuration requirements for WPtouch that may either be new or got flushed during the upgrade (I didn’t do the initial config).

    Thanks for the pointers, I’ll post back if I run into something I can’t resolve.

    That get() error isn’t Supercache. That is caused by some plugin using the object cache while PHP is shutting down. Unfortunately PHP kills objects first and then runs the shutdown code. Guess what? The object cache is an object …

    Thread Starter GFCphotog

    (@gfcphotog)

    Ok, all’s well. The blog is stable at WP 3.2.1 with no new errors.

    Solution was pilot error on my part. When upgrading to 3.2 the WPTouch/SuperCache settings got lost. Reconfiguring SuperCache to play nice with WPTouch (the exceptions device list) fixed the problem.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Updated to 3.2, seems ok – but errors in server logs’ is closed to new replies.