Error log per site

Discussion in 'Installation/Configuration' started by zapyahoo, Aug 7, 2014.

  1. zapyahoo

    zapyahoo New Member

    One of my client sites creates a huge error log... 30gb to 60gb :eek: Incredible

    This used space is totally outside the allocated disk quota for the website.

    Without turning off apache2 logging altogether, is there a specific site setting to turn off logging just for that website?
    Maybe apache directives?
     
  2. srijan

    srijan New Member HowtoForge Supporter

    Please check the thread, it might help you.
     
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    Add:

    ErrorLog /dev/null

    in the apache directives field of this website.
     
  4. zapyahoo

    zapyahoo New Member

    Thanks Till, seems to work.

    But with is this happening? are the error logs rotating like the access logs?
    How can and error log reach 60GB without being split and gz?

    Also, is the log client site folder being monitored and added to the client hard disk quota?
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    The error.log is checked every night and gets rotated and gzipped when its size exceeds 10MB. Maybe the cron_dialy.sh cronjob is not running on your server (root crontab).
     
  6. zapyahoo

    zapyahoo New Member

    It's running.
    I just think the process hangs with huge files 60gb plus.
     

Share This Page