• Resolved seisyuku

    (@seisyuku)


    hello,everyone

    In a month ago, my blog upgrade 2.3.3 to 2.5.x, I still have a new problem in server error log.
    When my blog’s Visitor access any page, and system log will add an error message everytime.
    (e.g. “ALERT – script tried to increase memory_limit to 33554432 bytes which is above the allowed value (attacker ‘59.120.**.**’, file ‘/web/***.org/seisyuku/wordpress/wp-settings.php’, line 16)” ) It’s 200,000 error messages in log file / a monthly.

    I unload all Plugins, but still report error.

    I cant changing the memory_limit setting in php.ini, my host don’t allow this. But I try to Increase the PHP memory limit to 64MB via .htaccess /wp-config.php /wp-setting.php, Still didn’t be effective…

    WP2.5 works normal, no other error message. so How can I resolve this problem, or just “ignore him”?

Viewing 3 replies - 1 through 3 (of 3 total)
  • line 16 of wp-settings.php should be this:

    @ini_set('memory_limit', WP_MEMORY_LIMIT);

    the constant WP_MEMORY_LIMIT is 32 meg, which is the number you’re being shown there.

    Notice the @ symbol is on that line. That’s supposed to tell PHP to suppress any warning messages created by that action. In your case, it doesn’t seem to be suppressing it.

    Please check that your wp-settings.php has an @ symbol in that location. If it does, and you still get this filling your log files, then comment out lines 15 and 16, in wp-settings.php and your blog should continue to run fine. Please make a backup of that file, and replace those lines with the following:

    //if ( function_exists('memory_get_usage') && ( (int) @ini_get('memory_limit') < abs(intval(WP_MEMORY_LIMIT)) ) )
    //	@ini_set('memory_limit', WP_MEMORY_LIMIT);
    Thread Starter seisyuku

    (@seisyuku)

    Yes,It’s work! after remark lines 15 and 16, no more error message, WP still run fine.

    Thank a lot, Ivovic!

    you’re welcome

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘script tried to increase memory_limit’ is closed to new replies.