Sudden php error logging after upgrade to v60

Jan 13, 2016
Istanbul, Turkey
cPanel Access Level
Root Administrator

I build the new server with v58 3 weeks ago and optimized it. A couple of days ago I upgraded to v60.x for the new features. Just recognized the HDD space is diminishing in the last few days and found out large log files under home... /home/*/logs/*.php.error.log ...

They were there as logging was enabled but the error levels are low. This time the logs were full with "PHP Strict Standards", "PHP Deprecated" etc, although they were disabled. This happened on 3 out of the 13 (sub)domains on the VDS.

(Sidenote: All domains are Joomla installations)

Under MultiPHP INI Editor, in all 5.5, 5.6 and 7.0 the related settings are as follows (I think these were the defaults):

error_reporting = E_ALL & ~E_NOTICE & ~E_WARNING & ~E_STRICT & ~E_DEPRECATED
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
track_errors = Off
html_errors = On
error_log = error_log
There are php.ini fles under accounts, but they all are empty.

In Apache "Pre VirtualHost" there are only mod_deflate and mode_expires related settings.

.htaccess files:

/home/*/.htaccess are all empty (moved all the stuff to Apache)

/home/*/public_html/.htaccess files are there (derivative of Joomla .htaccess with some more stuff like com/net/org redirection, mod_pagespeed settings, and lately stuff added yesterday by AutoSSL which I'm examining... No PHP related directives.

In Joomla configuration error reporting is off (it is display, not log anyway)

Something interesting: There are no error_log files but the ones under /home/*/logs are used.

Do I forget something? Where do they come from?

(I gzip-backed them and deleted but they will fill up rapidly, so I need a solution)

Thanks in advance :)[/code]


Staff member
Apr 11, 2011

Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome.

Thank you.
  • Like
Reactions: Harikalar Kutusu


Staff member
Apr 11, 2011

I'm happy to see the issue is now resolved. Thank you for updating us with the outcome and documentation.