oracle 9.2 + php 4.3.2 == occasional apache seg fault

[bsj]

I've run into a curious problem. I have two linux boxes, both running Oracle 9.2 and php 4.3.2 ( both redhat 7.3 ). On one box everything works perfectly. On the other box, apache occasionally seg faults whenever I try to do database writes to Oracle, as well as an occassional read - but if I try the same action a second later it works fine.

php configure : './configure' '--with-mysql' '--with-apache=../apache_1.3.28' '--with-oci8=/mnt/aa/u01/app/oracle/product/9.2.0' '--enable-track-vars' '--enable-sigchild' '--with-png-dir=/usr' '--with-jpeg-dir=/usr' '--with-zlib-dir=/usr/local' '--with-freetype-dir=/usr' '--with-gd'

I set the following env variables in a wrapper script which starts apache :
ORACLE_SID
ORACLE_BASE
ORACLE_HOME
NLS_LANG
TNS_ADMIN
ORA_NLS33

( I've also set them through putenv(), but that made no difference )

I've tried linking php statically as well as dynamically.

I can't find any information on the net about it, tearing my hair out! Anyone have any suggestions on where the problem lies?

Thanks!

Brian

[Sxooter]

Are these sig11 faults? If so, check your memory (memtest86.com)

[bsj]

Originally posted by Sxooter
Are these sig11 faults? If so, check your memory (memtest86.com)

Hi Sxooter,

Yes, these are sig(11) faults. Per your suggestion I downloaded and compiled memtest86, but it did not find anything wrong with the installed memory.

Barring any other suggestions, I'm going to recompile the kernel and tweak some stuff in there; the next course of action is a rebuild of the system, which I would really rather not do - anyone have any other suggestions for me?

Thanks for the help, Sxooter.

Brian

[bsj]

In case anyone is interested, I solved the problem by upgrading php to 4.3.3, and recompiling apache without expat. I also increased the shmmax kernel param.

I had some putenv() calls in the execute_query function I wrote which conflicted with the calling enviornment's variables, namely NLS_LANG.

The combination of the above fixed the error I was having.

Brian