• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Huge error_log because of .htaccess?

M

MAXW

Guest
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:

Merge dir (0x5c57b0) (0xd2ad68)
APPLYING (session.gc_maxlifetime)(36000)
APPLYING (session.cache_expire)(600)
APPLYING (engine)(1)
APPLYING (open_basedir)(/var/www/vhosts/MYDOMAIN/subdomains/MYSUBDOMAIN/httpdocs:/tmp)
Destroying config 0xd2ad68

In the httpdocs of this subdomain we have an .htaccess file looking like that
php_value session.gc_maxlifetime "36000"
php_value session.cache_expire "600"

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
 
Check your LogLevel in httpd.conf, make sure it is set to warn and not debug.

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn
 
yes , this was the first thing I tried. In my /etc/apche2/http.conf looks like that
LogLevel warn
ErrorLog /var/log/apache2/error_log
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 ;)
 
Something else I don't mentioned. The error_log files of the several domains/subdomains are totaly OK. No strange "Merge dir" messages.
:confused:
 
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.
 
Back
Top