• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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