Ad Widget

Collapse

Memory size exhausted on modifying triggers

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • badener
    Member
    • Sep 2009
    • 42

    #1

    Memory size exhausted on modifying triggers

    Hi,

    I just upgraded to zabbix 2.0.2. The GUI is run with php 5.4.5 on Apache 2.2.22.
    Today I wanted to modify a trigger but I just get a blank screen. In apache error log I find:

    PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 81 bytes) in /opt/httpd/zabbix-2.0.2/include/classes/debug/CProfiler.php on line 232, referer: triggers.php?form=update&hostid=&triggerid=&sid=
    PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 81 bytes) in /opt/httpd/zabbix-2.0.2/include/classes/debug/CProfiler.php on line 232, referer: triggers.php
    PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 130968 bytes) in /opt/httpd/zabbix-2.0.2/api/classes/CTemplate.php on line 491, referer: triggers.php

    Has anyone experienced similiar problems after upgrade. Searching this forum I found threads but nothing regarding version 2.

    Any ideas how to fix this ?
  • JBo
    Senior Member
    • Jan 2011
    • 310

    #2
    Hi,

    It seems that you have a 256 MB PHP memory limit.
    You can try to increase memory_limit parameter in php.ini.

    Hope this helps
    JBo

    Comment

    • badener
      Member
      • Sep 2009
      • 42

      #3
      no luck

      Hi,

      thanks for your advice - I tried it immediately, changing the memory limit from 256M to 384M - restartet Apache and immediately tried to change a trigger and got an error

      PHP Fatal error: Allowed memory size of 402653184 bytes exhausted (tried to allocate 83 bytes) in /opt/httpd/zabbix-2.0.2/include/classes/helpers/CHtml.php on line 42

      This only happens when I try to modify a trigger. It is possible to disable/enable a trigger as well as creating new triggers or deleting old ones.

      OK - it seems this is only related to old trigegrs - I managed to change a newly created trigger without error. Could this be a problem of the database upgrade ? I didn't notice any errors when I did the patch.sql .

      Anybody have any more ideas ? I'd hate to have to recreate all triggers.

      Comment

      Working...