[Tickets #12654] Re: Infinite loop if logfile not writable

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12654
------------------------------------------------------------------------------
  Ticket             | 12654
  Updated By         | stefan at 404-net.de
  Summary            | Infinite loop if logfile not writable
  Queue              | Horde Base
  Version            | 5.1.4
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


stefan at 404-net.de (2013-09-09 10:43) wrote:

The memory exhaust is triggered within seconds after login. I raised  
the php limit from
128M up to 2G and problem stays the same - couldn't think of an object  
used by Horde big enough to use that much memory. (Yes, there are huge  
mailboxes and calendars, but at the moment the error is triggered,  
there's no reasen fot them to be in use)
That's why I thought of a loop trying to write errors to the log file  
and calling the handler again when it fails. Didn't take a closer look  
to the source file yet.

With some syncing process over day the overall apache memory used by  
Horde increments up to some GB.. After fixing the permissions problem  
the exhaust errors are gone (with standard 128M limit) and the memory  
usage stays low. The horde log just shows login notes and sometimes a  
minor unauthorized-errors, no significant problems.


Sure it's caused by misconfiguration, so basically administrator's fault...