>Number: 5227 >Category: mod_cgi >Synopsis: mod_php with Solid RDBMS support causes conflicts with mod_cgi >-> apache will not start >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Nov 1 02:50:01 PST 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.9 >Environment: Linux 2.2.5-15smp #1 SMP Mon Apr 19 22:43:28 EDT 1999 i686 unknown gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) >Description: When compiling Apache with shared core and DSO support the module order affects the way Apache behaves. When installing PHP (3.0.12 in this case) with support for the Solid RDBMS, inserting the PHP module _before_ mod_cgi in the module list creates no problems. Inserting the PHP module _after_ mod_cgi results in Apache not starting at all (but no core dumps). This problem exists _only_ when PHP is compiled with Solid RDBMS support (versions 2.3 and 3.0 tested), thus making it a problem that may or may not be with Apache - it also might have something to do with PHP. I am submitting this report to the PHP development team as well. >How-To-Repeat: Compile Apache (1.3.9) with --enable-module=all --enable-shared=max --enable-rule=SHARED_CORE --enable-rule=SHARED_CHAIN; Compile PHP (3.0.12) with --with-apxs=<path to apxs> --with-solid=<path to solid includes/libs>; the PHP module gets installed as the last one in the module list by default - Apache will not start. Move mod_php above mod_cgi in the module list and Apache starts nicely. >Fix: N/A >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]
