#18533 [Opn->Fbk]: Segfault in Oracle 9.x client libs

ID: 18533 Updated by: kalowsky@php.net Reported By: thomas@fivemile.net -Status: Open +Status: Feedback Bug Type: OCI8 related Operating System: Redhat Linux 7.2 PHP Version: 4.2.2 New Comment: So does this final solution fix the problem for everyone? Solution being that mentioned by jason.mccormick Previous Comments: ------------------------------------------------------------------------ [2002-08-14 10:37:40] jason.mccormick@lexi.com I resolved my own issue. I determined that the httpd user wasn't picking up the ORACLE_HOME environment variable. Forcing that variable into the startup script has fixed the problem. ------------------------------------------------------------------------ [2002-08-13 15:11:50] quadra@demosoft.org I was getting a Seg Fault connecting to Oracle 7.3.4 -- but not on 8.0.x I had this path wrong before attempting the OCIPLogon.. putenv("ORA_NLS33=/../oracle/product/8.0.6/ocommon/nls/admin/data"); Once it was correct.. no more seg fault. sorry, no gdb on the system to check the backtrace though. ------------------------------------------------------------------------ [2002-08-02 13:34:01] jason.mccormick@lexi.com I found a core file from apache: [root@yew apache]# gdb bin/httpd ./core GNU gdb 5.0rh-5 Red Hat Linux 7.1 Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"... warning: core file may not match specified executable file. Core was generated by `/opt/apache-1.3.26/bin/httpd'. Program terminated with signal 11, Segmentation fault. #0 0x00000000 in ?? () (gdb) bt #0 0x00000000 in ?? () #1 0x4042e195 in ?? () #2 0x40069708 in ?? () #3 0x40067c48 in ?? () #4 0x40067cd7 in ?? () #5 0x40067c1a in ?? () #6 0x40067cd7 in ?? () #7 0x40078155 in ?? () #8 0x4007b46e in ?? () #9 0x4007bb4a in ?? () #10 0x0805d621 in ?? () #11 0x401b4177 in ?? () (gdb) Not sure if this is a legit core becuase I've played with a dozen combinations of configurations. ------------------------------------------------------------------------ [2002-08-02 11:38:06] jason.mccormick@lexi.com I've been experiencing this issue on a production webserver since I upgraded the client to Oracle 9i. Previously, the install worked fine when the client was Oracle 8. I tried this out on my development box and everything works fine. The production box is running: Linux 2.4.2 (early RH 7.1 or 7.2) glibc-2.2.2-10 gcc-2.96 My development box is running: Linux 2.4.18 glibc-2.2.5 gcc-3.1.4 Both machines are running Apache 1.3.26 with pthreads. Both have the Oracle 9.2 client. PHP was configured in both cases with: ./configure --with-apxs=/opt/apache/bin/axps --with-oci8=/opt/oracle --with-mysql=/opt/oracle --with-gettext --enable-track-vars --enable-force-cgi-redirect In both cases, Apache was compiled with: ./configure --prefix=/opt/apache-1.3.26 --enable-rule=SHARED_CORE --enable-module=so --enable-module=rewrite and then later recompiled with pthread w.r.t. to the OCI8 directions. I cannot seem to get a gdb dump trace from the production box (probably becuase of missing development tools) but it does generate a core file if someone is interested in me sending them output from that (e-mail me at jason.mccormick@lexi.com and give me instructions). Please advise how I can help debug this issue as it is critial to me. ------------------------------------------------------------------------ [2002-07-26 20:40:00] chs@baltic-online.de The same issue was experienced on sun-sparc-solaris2.8, with Oracle 8.0.5. Both php 4.0.4pl1, 4.0.6 and 4.2.2 are affected. Please, solve this issue as soon as possible - this is a serious showstopper. Thanks! ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/18533 -- Edit this bug report at http://bugs.php.net/?id=18533&edit=1