PEAR not working

mpar612

I am stumped. Below is my code and it doesn't work.

require 'PEAR/DB.php';

// Connect to the database
$db = DB::connect($login);
if (DB::isError($db)) { die ("Can't connect: " . $db->getMessage()); }

// Set up automatic error handling
$db->setErrorHandling(PEAR_ERROR_DIE);

// Set up fetch mode: rows as objects
$db->setFetchMode(DB_FETCHMODE_ASSOC);

if (class_exists('DB')) {

print "ok";

} else {

print "failed";

}

However, this code does:

require 'PEAR/DB.php';

if (class_exists('DB')) {

print "ok";

} else {

print "failed";

}

I just switched ISP's and none of the stuff that utilizes PEAR works on the new ISP. PEAR is installed. The DB module is installed, but I can't connect to a database. I don't get any errors. I just get a blank screen.

Any thoughts would be greatly appreciated. Thanks!

sneakyimp

So the first script just leaves a blank page? Have you tried to view the source to make sure?

What does the second script do?

mpar612

I have been having issues getting PEAR to work on my new server. So I totally stripped down some code and added things line-by-line to see what would work. This code just checks to make sure that the DB.php file is properly being included. Once I start adding the db connection info it stops working.

sneakyimp

You didn't answer my questions.

mpar612

Both scripts should theoretically produce the same output. The shorter of the two without the DB connect info works, but the other one with the DB connect info doesn't. Once I introduce the DB connection info, the script starts returning an empty file in the browser.

sneakyimp

You still didn't answer my questions. I wil reprint them here so you know what i'm talking about:
1) So the first script just leaves a blank page (the answer appears to be yes)
2) HAVE YOU TRIED LOOKING AT THE SOURCE CODE TO BE SURE? You could have some broken html which just makes it look like an empty page.
3) WHAT DOES THE OTHER SCRIPT DO? Like does it say 'ok' or 'failed' ?

mpar612

The first piece of code returned a blank page. That means totally blank. Even if you check the source.

I said the 2nd piece of code worked, which would mean that it returned ok.

sneakyimp

sounds like PHP might be timing out waiting for the connection to happen. You should check your $login string. make sure that's correct.

maybe also try putting some trace or echo statements in to see which instruction is failing to complete. i bet it's this one:

$db = DB::connect($login);

If $login doesn't have the password in it or something, the db server might be waiting for the password to be entered which never happens, resulting in a timeout.

I'm not familiar with the PEAR db object but you might want to read the documentation for more tips. Or possibly contact your service provider, although i expect they won't be much help unless they recommend the use of PEAR to connect to a database.

mpar612

Thanks for the response!

I did some snooping around on the web and it turns out that my new server doesn't display errors. I added:

ini_set('display_errors', 1);
error_reporting(E_ALL);

Now I am getting the following errors when I view the code:

Warning: main(): open_basedir restriction in effect. File(/usr/share/pear/DB.php) is not within the allowed path(s): (/var/www/vhosts/xxxxxxx/httpdocs:/tmp) in /var/www/vhosts/ygptechnologies.com/httpdocs/test.php on line 6

Warning: main(DB.php): failed to open stream: Operation not permitted in /var/www/vhosts/xxxxxxxx/httpdocs/test.php on line 6

Fatal error: main(): Failed opening required 'DB.php' (include_path='.:/usr/share/pear:/user/share/pear:') in /var/www/vhosts/xxxxxxxx/httpdocs/test.php on line 6

I really don't understand what what those errors are, but one thing that looked odd to me was in the final error it says: "include_path='.:/usr/share/pear:/user/share/pear:'" is that supposed to 'user'?

Any thoughts would be greatly appreciated. Thanks!

mpar612

BTW - I did check my login string and it is functioning properly.

sneakyimp

sounds to me like your server might be in safe mode (search the php.net site for details).

the webserver doesn't have permission to access that folder where pear is supposed to be installed.

NogDog

Note that the open_basedir restriction does not depend on whether safe_mode is in effect: it is a separate restriction which will be in effect regardless of the safe_mode setting.

You basic options are either to convince your web host admin to add the PEAR directory to the the open_basedir php.ini setting, or else copy the required PEAR packages to your personal directory space where you can access them. I suppose you could also try to get the admin to turn off the open_basedir restriction, but then that makes your site a bit more susceptible to malicious attacks by PHP scripts running elsewhere on your shared host (assuming it is a shared host?).

mpar612

I should have mentioned this earlier. I have a dedicated server running Plesk so I can host multiple sites on it. I tried copying the PEAR and DB module folders and files into this sites directory and that did not work. I am getting the same errors. I will explore the open_basedir restrictions and post my findings.

Thanks for your help!

Elan

mpar612,

Did you have a fix for this issue?