The tranquility of my morning was disturbed by receiving an email “Disk Usage Warning” from the web hosting service for the g4ilo.com website.
This was worrying as I had not made any significant changes to the site for several months. I was concerned that hackers might have found a way to upload files to the server so that it was serving porn or some other equally objectional stuff.
After a look around using the disk management tools in cPanel the public_html directory seemed to be excessively large.
I FTP’ed in to the server with FileZilla and found that the error_log file was astronomically large. I took a look at it and the file was full of warnings about a deprecated PHP function:
PHP Deprecated: Function split() is deprecated in /home/g4ilo/public_html/lib/classes/class.contentoperations.inc.php on line 881
A sI hadn’t changed anything my suspicion was that the web host had changed some global PHP setting. When I submitted a support ticket they didn’t admit to anything but with a bit of help I was able to turn error logging off. This seems to have solved the problem so I am crossing my fingers that ‘s the end of it.
It was fine maintaining and supporting a website when my mind was sharp and my eyesight good. But I don’t find messing with this kind of thing very easy nowadays and I could do without the hassle and stress of things like this.
I have recieve a couple of email from g4il0.com. I have not opening any of them. I would like to if he is a true ham operator or not. Please let me know by email.
As of PHP V5.3.0 the function split() has been deprecated. What probably happened here is your hosting company upgraded PHP while your site’s PHP code has one or more split() calls, thereby generating the errors.
Look at the PHP documentation for split, it explains why this was done and offers an alternative. Also google the error line from your error log file, there are lots of other suggestions on the web.
Just turning off error logging is a bad idea IMO. You should either fix the source code (if you wrote it yourself), upgrade your source package (if a new version fixes this) or if your source package has not fixed this, log a bug and request a fix.
To prevent your log files from becoming too large, they should be rotated at periodic intervals. It seems you, and/or your host provider aren’t doing this. Google methods of enabling log rotation. Or perhaps if your host is in the USA, there may be some nasty new NSA laws that say you can never throw your logs away just in case the Government wants to examine them?
Finally, the fact that you only found this because your log file was becoming so large is an indicator that you’re not examining your error logs regularly. This is bad practice in my opinion. Logs are there for a reason and have a story to tell, which is useless if nobody listens.
Just some suggestions and a bit of constructive criticism… 73’s, David