More precisely, I believe the proper fix would be to set the memory_limit in /etc/php5/cli/php.ini to a proper system-wide value (not -1), and to add "--define suhosin.memory_limit=512M" to the cacti poller command in /etc/cron.d/cacti.
-- François Beaulieu, CISSP Conseiller principal / Senior Consultant Secure by Knowledge +1 (514) 667-0691 ext 2061 francois.beaul...@securebyknowledge.com<mailto:francois.beaul...@securebyknowledge.com> On 2011-04-15, at 12:08 PM, Francois Beaulieu wrote: This isn't a suhosin bug, as it is simply doing what it is supposed to be doing. The log mesages can be fixed by changing the memory_limit in /etc/php5/cli/php.ini to a hard limit above 512M, or it can be fixed by changing the suhosin.memory_limit to 512M or more. (Or by uninstalling php5-suhosin...) The root cause of this problem is that php5-common recommends the installation of php5-suhosin while at the same time setting the memory_limit in /etc/php5/cli/php.ini to -1 and setting the suhosin.memory_limit to 0 by default. These settings are mutually incompatible. I suggest you file a bug on php5-common, but I presume that it will be filed as WontFix based on this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582384 -- François Beaulieu, CISSP Conseiller principal / Senior Consultant Secure by Knowledge +1 (514) 667-0691 ext 2061 francois.beaul...@securebyknowledge.com<mailto:francois.beaul...@securebyknowledge.com>
