Hi, in my Instance (ISPConfig 3.3 on Debian) the customLogs Directive is not written into the vhosts. So the access-logs are written to /var/log/apache2/other_vhosts_access.log. What configurations could cause this? In the webserver configuration (Section: System) the setting "Store website access and error logs" is set to "anonimize IP". For the website I have set statistics application to "none", but I assume this has no effect on the log itself. I could not find anymore settings in the client-/server- or siteconfiguration that seems to fit. Thanks a lot for your help and suggestions. Best Regards
Chapter 5: https://forum.howtoforge.com/threads/please-read-before-posting.58408/ Also, check if there is an .err file in the sites-available for this vhost. Also, which exact custom log config did you add in the Apache directives field? Adding this will disable things like log anonymization, so better not to manually change the log system; use the settings in ISPConfig. That's not from ISPConfig and is not used by ISPConfig. That's a system default from Debian. ISPConfig uses vlogger with a global custom log directive for all vhosts. The log files are stored under /var/log/ispconfig/httpd/.... and are visible in the log folder of the website. Adding a custom log directive is generally not a good idea, as it creates a conflict with ISPConfig, and various log-related functions will likely stop working. Also the functions you mentioned like IP anonymization, will stop working when you add custom log directives yourself into a vhost file or Apache directives field. All logging and anonymization is done by ISPConfig scripts and vlogger; adding your own custom log config simply breaks these functions.
Thanks for your reply. I did not add any custom log directive and also the vhosts do not contain any at all. All vhosts are affected/same. I also checked the .err hosts. There are some, but they are older and not for every vhost. I tried to add the Directive via the Apache directives field when I found out, that the logs were written to the debian default. But it was blocked by ISPConfig (which is good as you said). But I just noticed that there is no package vlogger installed - I guess that might be the reason then? Must have been forgotten when updating or something.
vlogger comes with ISPConfig as we use a modified version. You don't need that as a package. Do you have access log files in the log folder of each website? If yes, vlogger is there and works.
I think I found the reason. In the file /etc/apache2/sites-available/ispconfig.conf the line CustomLog was commented. Also there was a file /etc/apache2/conf-available/other-vhosts-access-log.conf which set the path to CustomLog ${APACHE_LOG_DIR}/other_vhosts_access.log vhost_combined a2dismod other-vhosts-access-log and uncommenting the line in ispconfig.conf solved it. I gues both changes are not default. Is that correct? Edit: according to the install files they are not. Thanks for your support Till!
