You are not logged in.
Hi,
When I run this script in cron
0 3 * * * php /usr/share/glpi/plugins/massocsimport/scripts/run.php --thread_nbr=2 --server_id=1
I always get this ALERT
ALERT - script tried to increase memory_limit to 4294967295 bytes which is above the allowed value (attacker 'REMOTE_ADDR not set', file '/usr/share/glpi/plugins/massocsimport/scripts/run.php', line 108)
ALERT - script tried to increase memory_limit to 4294967295 bytes which is above the allowed value (attacker 'REMOTE_ADDR not set', file '/usr/share/glpi/plugins/massocsimport/scripts/ocsng_fullsync.php', line 39)
ALERT - script tried to increase memory_limit to 4294967295 bytes which is above the allowed value (attacker 'REMOTE_ADDR not set', file '/usr/share/glpi/plugins/massocsimport/scripts/ocsng_fullsync.php', line 39)
ALERT - script tried to increase memory_limit to 4294967295 bytes which is above the allowed value (attacker 'REMOTE_ADDR not set', file '/usr/share/glpi/plugins/massocsimport/scripts/ocsng_fullsync.php', line 39)
Where can I change the allowed value (attacker 'REMOTE_ADDR )
or is something else wrong?
Many thanks
Offline
Je pense que c'est une alerte Suhosin.
Donc => revoir la config de suhosin
+
Dév. Fedora 29 - PHP 5.6/7.0/7.1/7.2/7.3/7.4 - MariaDB 10.3 - GLPI master
Certifié ITILv3 - RPM pour Fedora, RHEL et CentOS sur https://blog.remirepo.net/
Offline
Many thanks,
But what do you mean with 'revoir la config de suhosin'. Where can I find this config and where do I have to look.
Offline
> Where can I find this config and where do I have to look.
Which OS ? , version ? ...
I have a /etc/php.d/suhosin.ini, but is probaly Fedora/Redhat specific
Search for suhosin.memory_limit
Or disable suhosin
+
Dév. Fedora 29 - PHP 5.6/7.0/7.1/7.2/7.3/7.4 - MariaDB 10.3 - GLPI master
Certifié ITILv3 - RPM pour Fedora, RHEL et CentOS sur https://blog.remirepo.net/
Offline
Thanks,
i found it in /etc/php5/conf.d/suhosin.ini
For the moment the value is
;suhosin.memory_limit = 0
What should be a good value?
OS is debian lenny
Offline
Look at debian ans suhosin documentations.
; -> means the option is not active
0 -> sometime means 'illimited', sometime it's a value
CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6 - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)
Offline
Hi ,
Someone an idea what the value should be? I tries fast everything.
Many thanks
Last edited by gekkos (2009-11-11 19:15:16)
Offline
Anyone can help ??
Many thanks
Offline
Not enough information about your configuration (os, version, ...)
I will say, if you don't know how to configure the suhosin extension, you probably don't need it.
+
Dév. Fedora 29 - PHP 5.6/7.0/7.1/7.2/7.3/7.4 - MariaDB 10.3 - GLPI master
Certifié ITILv3 - RPM pour Fedora, RHEL et CentOS sur https://blog.remirepo.net/
Offline
Hi, I have the same problem here on debian squeeze, with GLPI 0.72.4 and massocsimport 1.3.0.
The php5 for Debian Squeeze has been packaged with suhosin included, so we can consider this suhosin error will propagate. http://packages.debian.org/squeeze/php5
I see these two lines in ocsng_fullsync.php :
ini_set("memory_limit", "-1");
ini_set("max_execution_time", "0");
From a system administrator point of view, I consider it's a sane decision from suhosin to consider that "script tried to disable memory_limit by setting it to a negative value -1 bytes which is not allowed". I would also not permit an unlimited execution time. A configuration for php cli in /etc/php5/cli/php.ini should be the standard (at least in the debian way)
By the way, i discovered this issues because of another issue : ocsng_fullsync.php just hangs, never returns and can stay running for several days without doing anything.
Organize your helpdesk!
Offline