Web Hosting Talk







View Full Version : new PHP, Apache, & mySQL .pkg's don't work together


netastic
09-10-2001, 09:50 AM
i just upgraded my RaQ4r with all of the latest security, bug, and software udates found at both http://pkg.nl.cobalt.com/ and http://www.cobalt.com/support/download/raq4.eng.html last week. everything works ok except PHP will not communicate with mySQL. phpMyAdmin generates errors when trying to set up a new database and a shopping cart developed in PHP will not work either. i had older versions of both that worked fine together. my programmer tried everything listed below (no compiling has been done yet):

> mgkimsal: I've got to pull down Apache and do a partial compile so the
> headers are there
> mgkimsal: so PHP can compile against them
> mgkimsal: so I can compile PHP as a DSO
> mgkimsal: to (hopefully) let it tie in with your current Apache
> mgkimsal: and it also needs to link against mySQL
> mgkimsal: which I had to pull down afresh and do last night
> mgkimsal: but that broke the ODBC stuff for your netastic store
> mgkimsal: and I dunno what, if anything else, it broke
> mgkimsal: just doing the PKGs didn't work
> mgkimsal: i erased mySQL
> mgkimsal: and put on the binary tar.gz file from mysql.com
> mgkimsal: and pointed it to /home/mySQL
> mgkimsal: and it seems to work
> mgkimsal: at least as good as it did before,
> mgkimsal: but the unixODBC stuff is broke I think - I can't really tell

has anyone experienced something like this? if so what fixed the problem?

netastic
09-10-2001, 11:04 AM
BTW here is a bug report on PHP that could be related http://www.php.net/bugs.php?id=4759

mgkimsal
09-10-2001, 11:09 AM
For anyone who can help with this, here's some additional stuff...

http://www.php.net/bugs.php?id=4759 describes the bug symptoms.

Things get put in the database, but only the first SQL INSERT or UPDATE or DELETE command works - "SELECTs" work fine, but anything that needs to update the DB in any way breaks. It *works*, but PHP reports an error.

What seems to be the case is that the client library compiled in to PHP is somewhat out of date, and the new mysql stuff doesn't talk properly with an old library. That's my hunch. The other related possibility is that there is another mysql client library loaded into Apache's RAM space which is conflicting with the PHP one. A possibility, because iHTML and unixODBC are on the box ( think).

Has anyone else been able to simply use the cobalt PKG files for mysql and PHP and have them work together without this bug?

Thanks...