Imaging Log Report issue

[Fernando Gietz]

Server

• FOG Version: 1.4.0 (SVN version 6070)
• OS: RedHat 7.3

Client

• Service Version: 0.11.12
• OS: Windows

Browser

• Version: Firefox 53.0.2

Description

When I try to see Imaging Log Report the page is blank and in the apache error_log file appears:

PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32 bytes) in /var/www/html/fog/lib/fog/fogcontroller.class.php on line 834, referer: http://fog.ehu.eus/fog/management/index.php?node=report

With the the others reports works fine except with snaping log that the error is different:

PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcontroller.class.php on line 1073, referer: http://fog.ehu.eus/fog/management/index.php?node=report

The server has 4 cores and 4 GB RAM.

[Tom Elliott]

You need to adjust the memory available to use.

[Fernando Gietz]

I have increased the memory and the imaging log report works fine

But the snaping log follows with the same error:

PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcontroller.class.php on line 1023, referer: http://fog.ehu.eus/fog/management/index.php?node=report&sub=file&f=aW1hZ2luZyBsb2c=

[Quazz]

@Fernando-Gietz You need to increase the max ecution time in php.ini

Although, it is odd to me that it would take over 30 seconds for the snapin report. Have you done loads and loads of them?

Additionally, a proposal would be to implement a higher execution time and memory limit in the respective log generating php files so this issue crops up less often.

[Tom Elliott]

In working I’ve set the execution time limit to unlimited. This means it will take a while to display all of the records, of course, but it shouldn’t through an error anymore (hopefully).

[Fernando Gietz]

As a suggetion, perhaps if you could config an interval time … I don’t need all log, only the last ones In this way we can optimize the resources.

[Tom Elliott]

@Fernando-Gietz Reporting means it could take a long time, which is the only reason I applied it to the report management page. All reports tie in to it. Just because we give it unlimited time, doesn’t mean it will use all that time to load “all reports”. It just means it will occur on all reports.

[Tom Elliott]

Can you please update us to let us know if your timing issues are resolved now? Thank you.

[Fernando Gietz]

Sorry Tom I forget do it. Yes, If I increase the maximum execution time to 60 seconds, the report runs well