In my server's syslog, I'm getting continously messages like this:

Jan 17 04:52:37 ns225163 suhosin[4345]: ALERT - script tried to increase memory_limit to 1048576000 bytes which is above the allowed value (attacker 'xxx', file '/var/www/drupal/sites/all/modules/boost/boost.module', line 1285)

Something isn't working here as it should; Suhosin tries to prevent malicious applications to consume too much memory, and as well Drupal as PHP have memory limits defined; either Suhosin does not accept the PHP memory_limit setting, or 'boost' is trying to go beyond it.

Any ideas? Thanks!


mgifford’s picture

bgm’s picture

Version: 6.x-1.x-dev » 6.x-1.20
Status: Active » Fixed

The function boost_views_async() tries to set a memory limit 4 times higher than the default because the operation it does can be pretty heavy. It's not very elegant, but it's normally not a big deal (although I guess it could crash a server in some circumstances).

The function itself is used to expire the cache of views when new nodes are created. It is disabled by default, if I recall correctly.

There's a few options:

- disable the option boost_flush_views_update ("Clear all cached views pages associated with a node on update").
- we should probably remove that php_init code. If people really need it, they can put it in their settings.php.
- we should think of doing a boost 6.x-2.x that uses the expire module (and httprl for the crawler!) - anyone want to work on that or sponsor? needed for 7.x-1.x as well.

As a compromise, I committed a fix to 6.x-1.x dev so that it tries to increase the memory only if it is under 256 M. There's not much logic in this, except that I assume this code was there because of some cheap PHP hosts that set a default low limit.

Also fixed an IPv6 bug while debugging this (#1670322: IPv6 bug in boost_views_async()).

mgifford’s picture


Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.