• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved error_log not in expected but unknown location

Sebastian

New Pleskian
When creating new subdomains, the log folder
/var/www/vhosts/domain.com/logs/subdomain.domain.com
is created, but is missing the PHP error_log file, so we can't tail anything.

Going to the Plesk's log file browser
https://domain.com:8443/smb/log-file/browser/id/37
there are no errors, while there should be some (php error_log('test');)

When managing log files with
https://domain.com:8443/smb/log-file/list/id/37
the path is shown as logs/error_log, like the sudomains with proper working error_log files.

When opening
https://domain.com:8443/smb/log-file/view/id/37?filename=error_log
the expected errors are there(!), so they are written somewhere (else).

Questions:
  1. Where are errors written to, where is the real used error_log file?
  2. What causes this behavior?
  3. Can I change/repair it to default?

Thanks a lot in advance!
 
Meanwhile I found the location:
/var/www/vhosts/system/subdomain.domain.com/logs/error_log
So question 1 is answered while 2 & 3 are still open.
 
The directory /var/www/vhosts/<domain>/logs is a hardlink to /var/www/vhosts/system/<domain>/logs
The hardlinks are only updated after the statistics run in the early morning hours, so a newly created subdomain will only have the Apache logs in /var/www/vhosts/<domain>/logs after the first statistics run.
 
Back
Top