1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Huge error_log because of .htaccess?

Discussion in 'Plesk for Linux - 8.x and Older' started by MAXW, Jul 26, 2006.

  1. MAXW

    MAXW Guest

    0
     
    Hi,

    we've got problems with our Suse Linux 9/Plesk 7.5.4 Server

    The /var/log/apache2/error_log is growing huge every day! This log file is full of entrys like this:

    In the httpdocs of this subdomain we have an .htaccess file looking like that
    This is only an example, because we have many domains an subdomains with different PHP values running. So everything works fine, but we can't monitor the error_log because it's spammed with the messages. I would say, these are no errors, but how to avoid writing them to the error_log?

    greeds
    Norbert
     
  2. wagnerch

    wagnerch Guest

    0
     
    Check your LogLevel in httpd.conf, make sure it is set to warn and not debug.

     
  3. MAXW

    MAXW Guest

    0
     
    yes , this was the first thing I tried. In my /etc/apche2/http.conf looks like that
    I even tried LogLevel error, but no effect to the error_log. I didn't configure a higher LogLevel, because it would have no sense, if I don't see the "Merge dir" entrys, but evenso no errors ;)
     
  4. MAXW

    MAXW Guest

    0
     
    Something else I don't mentioned. The error_log files of the several domains/subdomains are totaly OK. No strange "Merge dir" messages.
    :confused:
     
  5. wagnerch

    wagnerch Guest

    0
     
    It could be the command line switch -e for httpd, on Fedora there is a file /etc/sysconfig/httpd where you define the command line switches to start httpd with. Check there as well, and you may want to look at the start script (/etc/rc.d/init.d/httpd) and see if it was modified.

    I have seen some stuff via Google that implies this may be caused by duplicate VirtualHost entries.
     
Loading...