My logs have started to fill up with the following errors (IP addresses redacted). I'm getting several hundred per day - doesn't seem to be having an effect on the actual website though - any idea what could be causing this?
[Sat Jul 0204:46:412011][error][client xx.xx.xxx.xxx] PHP Fatal error: Call to a member function getPackageID() on a non-object in /var/www/concrete/startup/tools.php on line 34[Sat Jul 0205:14:022011][error][client xx.xx.xxx.xxx] PHP Fatal error: Call to a member function getPackageID() on a non-object in /var/www/concrete/startup/tools.php on line 34[Sat Jul 0205:14:022011][error][client xx.xx.xxx.xxx] PHP Fatal error: Call to a member function getPackageID() on a non-object in /var/www/concrete/startup/tools.php on line 34[Sat Jul 0205:18:572011][error][client xx.xx.xxx.xxx] PHP Fatal error: Call to a member function getPackageID() on a non-object in /var/www/concrete/startup/tools.php on line 34[Sat Jul 0205:48:172011][error][client xx.xx.xxx.xxx] PHP Fatal error: Call to a member function getPackageID() on a non-object in /var/www/concrete/startup/tools.php on line 34[Sat Jul 0205:48:172011][error][client xx.xx.xxx.xxx] PHP Fatal error: Call to a member function getPackageID() on a non-object in /var/www/concrete/startup/tools.php on line 34[Sat Jul 0205:53:452011][error][client xx.xx.xxx.xxx] PHP Fatal error: Call to a member function getPackageID() on a non-object in /var/www/concrete/startup/tools.php on line 34[Sat Jul 0206:20:122011][error][client xx.xx.xxx.xxx] PHP Fatal error: Call to a member function getPackageID() on a non-object in /var/www/concrete/startup/tools.php on line 34[Sat Jul 0206:20:122011][error][client xx.xx.xxx.xxx] PHP Fatal error: Call to a member function getPackageID() on a non-object in /var/www/concrete/startup/tools.php on line 34[Sat Jul 0206:24:572011][error][client xx.xx.xxx.xxx] PHP Fatal error: Call to a member function getPackageID() on a non-object in /var/www/concrete/startup/tools.php on line 34
From looking at the code, it seems this can be due to something calling a URL in the form
/tools/blocks/block_name/file
Typically, it then gets the block with the handle 'block_name', which is the step causing the error. Which probably means a block with the handle block_name isn't available, despite it being called.
Basically, I would consider this a 404 error. You should look in your access logs (what log is this coming from, anyways?) for matching entries to try to figure out what non-existent block is generating the error.
This is from the apache error_log, and you were right, compared it to the access_log and found a link to a ProBlog RSS feed that is no longer there... guess someone's reader must still be trying to poll it or something. Thanks for the help, -Brian.
Code
Post Reply
Delete Post
You are allowed to delete your post for 5 minutes after it's posted.
This website stores cookies on your computer. These cookies are used to improve
your website experience and provide more personalized services to you, both on this website and through
other media. To find out more about the cookies we use, see our Privacy Policy.
/tools/blocks/block_name/file
Typically, it then gets the block with the handle 'block_name', which is the step causing the error. Which probably means a block with the handle block_name isn't available, despite it being called.
Basically, I would consider this a 404 error. You should look in your access logs (what log is this coming from, anyways?) for matching entries to try to figure out what non-existent block is generating the error.
James