This is a fast but durable and stable solution
Client wesites on one of my ISPConfing Web Servers (actually I have to check the others yet) started or, better, stopped logging websites accesses into the expected access log file (the one into /var/log/ispconfig/httpd/blog.giuseppeurso.net/access.log), and start logging into the generic “other_vhosts_access.log” used for the “generic website” the one wich responds to all unmanaged virtualhost requests, the ones that comes by IP address instead of hostnames.
Ispconfig vhost config templates:
The solution is to check if the CusomLog directive is in place into the vhost config template used by ISPConfig during a new website creation, or a website update. This file is located into “/usr/local/ispconfig/server/conf”. When I checked mine, obviously after several searches, i discovered that the CustomLog directive wasn’t there. So what i’ve done was to add my CustomLog directive right after the ErrorLog directive paying attention while copying the variables part (tmpl_var name=’domain’), where the domain name should go.
Here is part of my file before the change:
ServerAdmin webmaster@ ErrorLog /var/log/ispconfig/httpd/ /error.log
Here, instead, is the part of the same file after i added the CustomLog directive line:
; ServerAdmin webmaster@ ErrorLog /var/log/ispconfig/httpd/ /error.log CustomLog /var/log/ispconfig/httpd/ /access.log combined
That’s all, i just wrote this little article because after several searches on google, i didn’t find any direct answer to this issue. I really ope this will save your time, if yes, please leave a comment.