AnsweredAssumed Answered

Logger not logging custom [FATAL] logs

Question asked by gianluca poli on Jan 19, 2016
Latest reply on Jan 20, 2016 by gianluca poli

Hi all, i am facing a strange behaviour:

 

my sugar logs are set to FATAL in administration panel configuration, i wrote a lot of custom code, which works well, in wich i log a lot of things (errors and other stuff) always using $GLOBALS['log']->fatal.

 

Now the problem is that the only [FATAL] i get is from scheduler:

 

Tue Jan 19 16:02:01 2016 [29624][1][FATAL] Job runs too frequently, throttled to protect the system.

Tue Jan 19 16:03:01 2016 [29706][-none-][FATAL] Configuration variable date.timezone is not set, guessed timezone Europe/Berlin. Please set date.timezone="Europe/Berlin" in php.ini!

 

seems like the scheduler is "not releasing" logger, and no other file can write to it.

 

apache error.log is working fine, it is only a sugarCRM logger issue.

 

An example of working logger:

 

Thu Dec 21 16:15:18 2015 [11475][a87f0bf4-8595-0713-abf3-52d919ec060f][FATAL] AFTER SAVE--->Record created already, not calling Shepard.

 

Any idea?? i tried removing all sheduled operations whic run "As often as possible" without success..

Outcomes