[RESOLVED] Problem when running as Cron Job against browser

genista

All,
I have code that executes fine when run through a browser and yet when run as a Cron Job produces this error:

Call to a member function query() on a non-object

The error is in this: $result2 = $mysqli->query($query) or die($mysqli->error.LINE);

from the following

set_include_path('/home/user/includes/');
include("base2.php");


  $query="SELECT content_id, title, source_image, url FROM detail where approved='y'";

$result2 = $mysqli->query($query) or die($mysqli->error.__LINE__);

What causes this to behave differently?

Thanks,

Weedpacket

Running through a web server the script will be run under the server's user account; as a cron job it will run under the account of the job's user.

dalecosp

Cron also has no idea of PATH as far as the shell is concerned; since you're using PHP and setting the include_path specifically, that's of little consequence here, but it might be worth knowing about in the future...

bradgrafelman

It's also possible that it isn't using the same php.ini file as would be used when PHP is invoked via the webserver.

Rather than guess at which of the above is the issue, I'd recommend doing two things:

Ensure log_errors is set to On, error_log is configured appropriately, and error_reporting is set to E_ALL.
Change [man]include[/man] into either [man]require[/man] or [man]require_once[/man]. Can your application go without base2.php? If that file is missing, will it detect this and gracefully handle that? If the answer is no to both, base2.php is a required component, thus it makes more sense to describe it as such in the code.

genista

Thanks, I have changed it to require, base2 is where I set the database connection so it is absolutely needed. The error reporting is configured and despite the change is still returning the same error. As the file being run is not in my public folder I have also taken out the reference to base2 out and copied the contents of base2 into the file itself. Still no joy..

bradgrafelman;11039425 wrote:
It's also possible that it isn't using the same php.ini file as would be used when PHP is invoked via the webserver.

Rather than guess at which of the above is the issue, I'd recommend doing two things:

Ensure log_errors is set to On, error_log is configured appropriately, and error_reporting is set to E_ALL.

Change [man]include[/man] into either [man]require[/man] or [man]require_once[/man]. Can your application go without base2.php? If that file is missing, will it detect this and gracefully handle that? If the answer is no to both, base2.php is a required component, thus it makes more sense to describe it as such in the code.

bradgrafelman

Speaking of the contents of base2...

Can you show us what that is?

genista

Thanks, here are the contents with the relevant credentials removed:

    $dbhost = "localhost"; // this will ususally be 'localhost', but can sometimes differ
    $dbname = "x"; // the name of the database that you are going to use for this project
    $dbuser = "x"; // the username that you created, or were given, to access your database
    $dbpass = "x"; // the password that you created, or were given, to access your database

mysql_connect($dbhost, $dbuser, $dbpass) or die("MySQL Error: " . mysql_error());
mysql_select_db($dbname) or die("MySQL Error: " . mysql_error());

bradgrafelman;11039433 wrote:
Speaking of the contents of base2...

Can you show us what that is?

Derokorian

well your base2.php seems to be using the old deprecated mysql_* extension. Don't use that (see MySQL(i) warning in my signature).

Instead you'll want to create a new mysqli object attached to a $mysqli variable, so that your query code can use it.

bradgrafelman

Er... right, well, if you look at that code and think about it for a second, the problem should be quite obvious. The code you posted above has two issues:

It's still using the deprecated mysql extension (relevant stickied topic: Stop Using the MySQL Extension!).
It never defines an object named $mysqli that your other code assumes will exist (which, by the name, is probably supposed to be a [man]MySQLi[/man] object).

EDIT: Derokorian beat me to the punch while I was making tea. :glare:

genista

Thanks to both of you, I haven't touched 'base' in a few years and just didn't see it. Interesting that using through the browser didn't pick it up, but anyway I will go away and test again.

bradgrafelman;11039439 wrote:
Er... right, well, if you look at that code and think about it for a second, the problem should be quite obvious. The code you posted above has two issues:

It's still using the deprecated mysql extension (relevant stickied topic: Stop Using the MySQL Extension!).

It never defines an object named $mysqli that your other code assumes will exist (which, by the name, is probably supposed to be a [man]MySQLi[/man] object).

EDIT: Derokorian beat me to the punch while I was making tea. :glare:

bradgrafelman

genista;11039447 wrote:
Interesting that using through the browser didn't pick it up

There's not really anything to "pick up"; the contents of base2.php that you posted above would never have worked with the code you posted in your first post, no matter whether you're invoking PHP via the command line, a webserver, or a watermelon.

If it actually worked when invoked via a webserver, then perhaps you were using a different base2.php that you haven't shown us.