php 4.3.8

[toml]

Looks like php 4 has been updated as well, due to a few security issues.
http://www.php.net/release_4_3_8.php

[DirectAdmin Support]

Wow, they sure have a high turnover :) I'll update the customapache build script now.

John

[neorder]

well, i updated to 4.3.8, and httpd failed to start, here is the error quote

[Wed Jul 21 14:41:00 2004] [error] Cannot remove module mod_security.c: not found in module list
PHP Warning: [Turck MMCache] This build of "Turck MMCache" was compiled for PHP version 4.3.7. Rebuild it for your PHP version (4.$
in Unknown on line 0


i can see it's MMCache problem, but i also recompiled MMCache after seeing that error, but it didn't help.

in the end, i had to roll back to 4.3.7 and httpd resumed normal operation.

any idea? thanks.

[toml]

Did you remember to run the phpize command before recompiling MMCache?

[jmstacey]

Yes, you must do complete recompile following the instructions. You can always comment out the lines in the php.ini file until you get it working properly that way at least httpd is online.

[neorder]

of course i did run phpize, i've installed MMCache quite a number of times, so i'm sure my installation was okay.

i remember i had the same problem when upgarde 4.3.6 to 4.3.7, it's the same MMCache problem, but i was unable to bring back httpd even after rolled back to 4.3.6. i gave up that server in the end.

i think MMCache really makes trouble sometimes.

[jmstacey]

When you updated php it moved the php.ini file back to its original location. After updating php, reinstall zend using customapache so the php.ini is back in the Zend directory and then finally reinstall turck mmcache. This is because turck mmcache is probably installed as a zend extension and not as a php extension. As such you must also make sure you have zend upto data and installed correctly.

[neorder]

many thanks, i will remember what you told.

i lost quite a few hundred dollars USD due to last time my server failure, i think after i've read this, the same problem will never happen again.

i'm heading to upgrade my php later tonight, let's see if i can make it;)

[neorder]

Originally posted by jmstacey
When you updated php it moved the php.ini file back to its original location. After updating php, reinstall zend using customapache so the php.ini is back in the Zend directory and then finally reinstall turck mmcache. This is because turck mmcache is probably installed as a zend extension and not as a php extension. As such you must also make sure you have zend upto data and installed correctly.

btw, according to what you are saying, php.ini back to its original location after update, then if i roll back my php, the php.ini will also roll back to the Zend directory automatically? :confused:

anyway, when i rolled back my php, everything backed to normal.

[jmstacey]

I'm not sure about that. All I know is that if I update php without also reinstalling zend it won't work because the update puts the installation back in the original location whereas when you install zend with ./build zend it puts the php.ini file back in the Zend directory.

[neorder]

erm...maybe i should wait until DA support has comfirmed this issue...

[neorder]

here is the reply i've got

Hello,

There is a check in the script that prevents it from overwriting the older php.ini if it exists. You could always just make a backup of the file before you update and restore it after if it is no longer there.

Thank you,

John

so, would it be okay if i set php updating not to update my php.ini location?

i don't want to try my server until it's comfirmed by someone else whose server also installed MMCache and Zend. :(

[DennisCitus]

How do I use the build-script to update to php 4.3.8?

[l0rdphi1]

DennisCitus,

This should do it:cd /usr/local/directadmin/customapache
./build clean
rm -f configure.php
./build update
./build php
Phi1.

[deltaned]

Originally posted by DennisCitus
How do I use the build-script to update to php 4.3.8?

cd /usr/local/directadmin/customapache
./build clean
./build update
./build php or ./build all

[wdv]

Just to let you know,

I succesfully upgraded to PHP 4.3.8 on two machines.

[rhoekman]

(FreeBSD 5.x)

Zend is not working after upgrading php..

This is what I've done:

cd /usr/local/directadmin/customapache
./build clean
./build update
./build all
./build zend

Now my zend encoded application is not working anymore. Also the httpd child process is exiting when calling the zend encoded file from the browser:

siteserver kernel: pid 878 (httpd), uid 1003: exited on signal 11

html and php pages render without any problems..

[motobrandt]

Originally posted by rhoekman
(FreeBSD 5.x)

Zend is not working after upgrading php..

This is what I've done:

cd /usr/local/directadmin/customapache
./build clean
./build update
./build all
./build zend

Now my zend encoded application is not working anymore. Also the httpd child process is exiting when calling the zend encoded file from the browser:

siteserver kernel: pid 878 (httpd), uid 1003: exited on signal 11

html and php pages render without any problems..
Which version are you uprading from? PHP that is...

[rhoekman]

Thanks for the reply.. I've just got it working.. I've deleted any config files that where still present in the build directory and repeated the steps I mentioned in my earlier post. (version of php was 4.3.7 I think :) I suffer from short term memory loss I guess..)

[mdoens]

I do not have a custom built apache system jet, and 'm running 4.3.7 with all the modules i need.

Can i upgrade to 4.3.8 with just:

cd /usr/local/directadmin/customapache
./build clean
./build update
./build php

(redhat 9 o.s)

[vincenzobar]

got mine updated

all i had to do was

cd /usr/local/directadmin/customapache
./build clean
rm -f configure.php
./build update
./build php

./build zend

and hit yes/ok through zend wizard

it failed to restart apache that way so i just restarted it manually and it all worked great


THANKS