Error log size

Rate this topic: Evaluations: 1, 1.00 on the average.Evaluations: 1, 1.00 on the average.Evaluations: 1, 1.00 on the average.Evaluations: 1, 1.00 on the average.Evaluations: 1, 1.00 on the average.Evaluations: 1, 1.00 on the average.1.00 out of 6 based on 1 vote(s)
GK User
Wed Nov 04, 2015 6:05 pm
Reply with quote
Report this post
In order to research a 1064 error problem, we accessed the error log on the server which was 3.25GB, too large to open with any software we currently have. We deleted the error log and recreated the 1064 error and immediately downloaded the error log again. The log, after only one hour of being created is already over 9000 KB. After 5 hours it is now at 38,000KB. I do not think the application should be generating this many errors. Is it possible for you to address some of them so that the file can be kept at a manageable size?

Error log attached.
User avatar
Senior Boarder

GK User
Wed Nov 04, 2015 9:42 pm
Reply with quote
Report this post
Those are only warnings. Depending on what access you have to your server you can try one of the methods described in this article:
http://www.inmotionhosting.com/support/ ... php-errors
You could also contact your hosting company and ask them how to stop reporting of "PHP Notice:" to apache/nginx log files.
User avatar
Moderator


cron