Error Log will not display

8 posts by 4 authors in: Forums > CMS Builder
Last Post: December 4, 2015   (RSS)

I cannot get the error log to open.  I've looked for a table to check but cannot find one.  I get notification in my email of errors.  Where are the errors stored?  All the other functions work great; just can't see the contents of the error log.

Eric

By Damon - November 2, 2015

Hi Eric,

In CMS Builder, you can see the Error Log under Admin > Error Logs. Last link in the at the bottom in the left navigation.

If you still can't find it, let me know.

Cheers,
Damon Edis - interactivetools.com

Hire me! Save time by getting our experts to help with your project.
http://www.interactivetools.com/consulting/

By eduran582 - November 2, 2015 - edited: November 2, 2015

Hi Damon,

Thanks for the reply.  I can see it listed at the bottom in the left navigation it's just when I click on it to see the errors, a blank page displays.  It's been working fine but recently (a few days ago), I suddenly cannot see the errors and each time I try and go 'back', it increments by one.

Eric

Forgot to include the last errors that were emailed to me in case this helps:

Latest errors:

Oct 31st, 2015 - 03:34:47 PM
E_NOTICE: Undefined index: menuName
/home/content/.../cmsAdmin/lib/menus/_error_log/actionHandler.php (line 19)
https://www.cmpdsites.com/cmsAdmin/admin_265-1122.php?menu=_error_log

Oct 31st, 2015 - 03:34:47 PM
E_NOTICE: Undefined index: listPageOrder
/home/content/.../cmsAdmin/lib/menus/default/list_functions.php (line 57)
https://www.cmpdsites.com/cmsAdmin/admin_265-1122.php?menu=_error_log

Oct 31st, 2015 - 03:24:16 PM
E_ERROR: Allowed memory size of 134217728 bytes exhausted (tried to allocate 6377140 bytes)
/home/content/.../cmsAdmin/lib/viewer_functions.php (line 433)
https://www.cmpdsites.com/cmsAdmin/admin_265-1122.php?menu=_error_log

By Damon - November 3, 2015

Hi Eric,

Can you upgrade to the latest version of CMS Builder (2.65)?  

Make a full backup first. Then get the latest CMS Builder here: http://www.interactivetools.com/order/upgrade.php

If you are already running 2.65, can you make a full backup and then reupload the CMS Builder files?

Then let us know if that resolves the issue or if the Error Log is still not visible.

Thanks!

Cheers,
Damon Edis - interactivetools.com

Hire me! Save time by getting our experts to help with your project.
http://www.interactivetools.com/consulting/

By DreamSync - December 3, 2015 - edited: December 3, 2015

Hi Damon,

I'm seeing this issue when the error logs get big - not sure what the threshold is.  Last time I experienced it (a few minutes ago) the error log listed (86) records.  Even after clearing out the error logs on the server within the root directory as well as the CMS directory I haven't been able to get the front end of the CMS to recognize the cleared error log. 

In fact, attempting to load the error log from the CMS and getting the blank page creates this error in the log:

[04-Dec-2015 08:37:26] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 3660650 bytes) in /***/***/***/***/cmsb/lib/viewer_functions.php on line 433

This CMS was just upgraded to 2.65 yesterday after a full backup.  Error logs were working fine with low error numbers.  My high errors were caused by the "Unable to load dynamic library '/usr/local/lib/php/extensions/no-debug-non-zts-20090626/'" which I've since remedied. 

____________

Update - I've reinstalled 2.65 and I still cannot access the error log page. It's just a blank white screen.

_______________________________________

DreamSync

By Dave - December 4, 2015

Hi DreamSync, 

It's a known issue when more data is loaded on the error log page then PHP can hold in memory.  

Try this link to load fewer records at a time on the list page: admin.php?menu=_error_log&perPage=10

Let me know if that works for you.  Thanks!

Dave Edis - Senior Developer
interactivetools.com

Hey Dave and DreamSync,

I tried what you suggested Dave (admin.php?menu=_error_log&perPage=10) and the page came up.  The last error reported was: E_ERROR: Allowed memory size of 134217728 bytes exhausted (tried to allocate 6537037 bytes) so it appears it's as you said (more data is loaded on the error log page then PHP can hold in memory).  Once I cleared the log, I was able to access it again.

Thanks!

Eric