Server crashed due to logfile > 16gB

I have a good working cms installed, but i keep getting enormous logfiles. Since i did not have a cronjob running, clearing these logfiles, my provider did shut me down. The logfiles are growing 50mB in 10 mintes and had grown over 16gB.
But from the outside, everything is running fine and the 2 conncted screens do their job just fine.
Now the cronjob runs, or I shut down logging to keep control of the logfile size, but the errors are telling me not much. Who can put me on the right track what is wrong and why i create so much logfile.

Here are some samples…

76327
16-01-22 02:23:21
CMS
log

require_once(): Inserting [/home/gcdk/domains/golfclubdekoepel.nl/public_html/xibo/lib/pages/log.class.php]

8
Notice
/home/gcdk/domains/golfclubdekoepel.nl/public_html/xibo/lib/app/pagemanager.class.php
139

76435
16-01-22 02:24:02
CMS

require_once(): Inserting [/home/gcdk/domains/golfclubdekoepel.nl/public_html/xibo/lib/pages/log.class.php]

8
Notice
/home/gcdk/domains/golfclubdekoepel.nl/public_html/xibo/lib/app/pagemanager.class.php
139

76326
16-01-22 02:23:21
CMS
log

require_once():
apc_cache_make_file_entry: entry->data.file.filename is
[/home/gcdk/domains/golfclubdekoepel.nl/public_html/xibo/lib/pages/log.class.php]

8
Notice
/home/gcdk/domains/golfclubdekoepel.nl/public_html/xibo/lib/app/pagemanager.class.php
139

76434
16-01-22 02:24:02
CMS

require_once():
apc_cache_make_file_entry: entry->data.file.filename is
[/home/gcdk/domains/golfclubdekoepel.nl/public_html/xibo/lib/pages/log.class.php]

8
Notice
/home/gcdk/domains/golfclubdekoepel.nl/public_html/xibo/lib/app/pagemanager.class.php
139

Firstly you need to be running the maintenance script which will clean up old log entries and prevent this exact thing happening.

The other things you have logged suggest you’re running your CMS in test and or debug mode which will cause huge amounts of logs to be saved.

Please ensure you have the CMS mode set to production and auditing off on the CMS and all your displays too. You should only switch that on if you are actively debugging an issue.

Alex, thanks for the quick answer. I checked all settings and they were most as you said:
All displays have AUDITING OFF.
The CMS was in PRODUCTION mode.
I did (and do) not run the maintenance script, because for the time being I cannot set any script with cron. So far no access, still talking to the provider.
Can I runs this script from another server or through a browser ? The latter showed me some data. For the time being i clean the log table using phpmyadmin.
I also went to the page Report a fault and clicked on switch OFF debugging.
Went back to settings, switched logging ON and the same kind of error reports showed up with a rate of 1Mb per minute.
Noticed that running http://xibo.golfclubdekoepel.nl/maintenance.php?key=xxxxxxxxxxxxxx from the browser did not empty the log table. Switched logging OFF again, because Xibo by itsself runs fine so far.
Erik

Debug logging should be off and is off by default, do leave it that way. The maintenance script won’t empty the log table but it will delete log messages older than the configured time to retain them. You certainly call it remotely from another server and there are lots of free and paid web cron services you can use to do that

Alex,
All is well now. the logfile remains small and i run a script from another free service.
Thanks for the support and a fine piece of software.
Erik

2 Likes