Topic: Whats up with Apache 2.2.15 and php 5.3.2

[Squirre1]

Ok so let me break down the Woes here...

Gotta love how a few versions back of PHP, they started to break MySQL support because of how the packages are compiled, deved, whatever, where I have to use an older php_mysql so my Apache instance doesnt die. Now it just seems to be getting worse...

So I wanted to upgrade my WinSrv2003 apachelounge apache 2.2.11/php 5.2.9-2/MySQL 5.1.30 instance to the most current.

So I grabbed the apachelounge 2.2.15
PHP 5.3.2 VC9 Ts(thread safe)
MySQL 5.1.48

I started by upgrading my DB and then went into my sites to validate all is good.
Next I upgraded my apache to 2.2.15, which that went fine as well..
Now php comes into play... I tried the php 5.3.2 and this is where the proverbial shite hit the fan.

And you would never believe some of these mockups of what is workin and not.. But Anyway...

With 5.3.2 configured I was not able to start my apache service, so I started eliminating items. I run multiple vhosts on my apache environment. This is where it starts to bake your noodle. With my primary host, all is good, BUT if I enable my vhosts, httpd wont start, it just dumps out. Oh yeah, I failed to mention. Even with only my primary host configured, it can only be started via commandline.

Now I am not new to this at all as I have been running php from version 3.x, apache from 1.3.7 and MySQL 3.2x GA releases, with annual and semi annual upgrades as necesary. But this business with PHP appearing to be more and more incompatible is killing me...

Does anyone have ideas on this issue, when PHP dies its adding the fault on php5ts.dll in my event log, for which there are complaints all over the web...

Thanks All,

Squirre1

[glsmith]

I hear ya, I bitch and moan about the exact same thing!

I have so little on PHP/MySQL for this exact reason. I'm a true believer in flat file DBs, yeah they are old skool, yeah they can be a bit slower, but at least the data is not locked into this never ending nightmare of matching PHP & MySQL or something just as miserable. And even better, have never had them injected with <script> links to drive-by malware sites.

Anyhow, from what I understand, php 5.3 is supposed to be the cure-all, looks like it is not.

Honestly, PHP and MySQL need to merge, or at least one needs to talk to the other so this crap becomes a thing of the past.

My rant:
http://www.apachehaus.com/forum/index.php?topic=117.0

[James Blond]

I'm a true PHP lover. Since PHP has mysqlnd and there is no more need of libmysql. it works pretty fine even when you update to a never mysql or php version.
For the injection horror just use mysql_real_escape_string or just mysql_escape_string.

[glsmith]

"We'll see" said the Zen master

[murrayE]

I had had Apache 2.2.14 and an older PHP 5.2.x working happily together, supporting MySQL, phpMyAdmin, etc., on a localhost set-up under Windows XP Pro (SP3). I uninstalled all that and instead:

(1) Installed Apache 2.2.15 in a localhost config from httpd-2.2.15-win32-x86-no_ssl.msi (also tried the openssl version when the former + PHP didn't work). That worked just fine.

(2) Installed PHP 5.3.2 from php-5.3.2-Win32-VC6-x86.msi (thread safe), which php.net says to use, as I read its instructions. (It says NOT to use the VC9 version with apache.org binaries.)

Now the apache httpd service will not start. So of course I never got so far as to try a .php script in the browser.

Of course I put the correct entries in PATH and PHPRC. My httpd.conf was what the apache installer set up plus my changes in appropriate spots: