Php 5.3.10

[gohighvoltage]

Ok, I used easy apache and upgraded to PHP 5.3.10, everything went ok, but it broke my vbulletin site,

I got an error that said memcache was missing. Odd, cause I double checked easy apache and memcache was configured.

Tried again and same thing.


So I easy apache'd back to 5.2.17. Everything works again.


Anyone else have an issue like this?

[the_ancient]

Did you Upgrade memecache as well?

[gohighvoltage]

Nope, I didn't. That would explain it. Is there an easy way to update all the extensions?

[gohighvoltage]

Thank you Ancient.

[the_ancient]

Well you can just do

$  pecl upgrade

but I dont know (never upgraded everything at once) if they will hurt any other packages

I would do a

$  pecl list-all

so see what extensions you have installed and only upgrade those you want, if that is all of them great.

upgrade indivual ones with

$  pecl upgrade {PACKAGENAME}

example

$  pecl upgrade memcache

Some people have also reported as having to uninstall then reinstall memcache after an upgrade from 5.2 to 5.3

[gohighvoltage]

Thank you so much Ancient. Worked!


Its as if memcache did not install automatically with 5.3.10 even though easy apache was set to install.

I hope I am not missing anything else. LOL

[gohighvoltage]

So far it seems like 5.3.10 is noticeably faster. Also, it seems like, even though I use suphp, that eaccelerator now works. I thought that eaccelerator was not compaticable with suphp? Maybe this was a change in PHP 5.3.10?

[the_ancient]

I know of no way for them to work together, suPHP creates a new process with each request so it would make eAccelerator pointless

[gohighvoltage]

That is really odd. I am running SUPHP, and look at this:


eaccelerator.jpg



Looks like eaccelerator is working.

[gohighvoltage]

I double checked, and I am only running SUPHP, and the fastcgi is not installed as per easy apache.

[the_ancient]

Well "working" and doing something is not really the same thing.

It could be "cache" each request over and over, which would be WORSE than just executing it

I have not found a single thing that would lead me to believe that eA and suPHP can work at the same time, they might be running together but they are working agaist each other

[gohighvoltage]

Maybe someone from Jag support can chime in and let me know how this can be? Thanks

[gohighvoltage]

Hi Ancient, I cannot explain why PHP info shows it enabled and working, so as a safeguard I went into php.ini and disabled it.

[jason]

eAccellerator runs at the PHP level, suPHP initiates PHP processes. So it is plausible that eAccellerator could be running within PHP--it doesn't necessarily know that the process will die when the script terminates. Like TA said, having it running is pointless because suPHP doesn't cache processes...but I'm not sure (but I'm not an expert in this area either) that eAccellerator has any way to tell whether a PHP process is running under suPHP, FastCGI/mod_fcgid, or just raw CGI--I think it just sees it as a CGI process (vs. a mod_php process).

--Jason

[gohighvoltage]

Hey Jason! That makes a lot of sense. For right now I turned off eaccelerator via php.ini, but do you think it would be better to just uninstall eaccelerator via easy apache?