Aditya Dhekney wrote:
> Sorry...the "page cannot be displayed" error (from browser page) is actually
> a "cannot find server" (displayed on head title). i don't think this makes a
> difference, but just in case it does, you know it.
Might be significant, but it could be you're using IE. IE is vague (oh
sorry, 'user friendly') in it's error messages.
> If i comment out midgard from httpd.conf (and keep php4), leave midgard.so
> in php.ini, apache starts, but php files give page cannot be displayed
> error. (no seg fault)
And the patch I sent you logs nothing. Hmm. Just thinkin out loud, but
that means midgard-php is influencing PHP, way before it gets
initialized. But I don't think there's even anything it can do before
being initialized. Aditya, could you try going back to to CVS as of
July 8th? The last major change introduced were the destructors on the
9th.
> If i leave midgard uncommented in httpd.conf, then seg fault.
This one is just weird. We haven't changed anything significant in mod
for months. But as you go back to the 8th, even the minor changes we
did should be gone.
> I'm assuming that commenting out php stuff shouldn't matter as long as
> midgard.so is concerned in php.ini, because php.ini wouldn't get read in
> that case..
Sorry, I don't understand.
> Just to recap (all assuming no server running, server started with
> 'httpd -X'
>
> >- no mod_midgard, no midgard-php: server starts and regular PHP pages
> >work OK
> Yes...as long as in php.ini midgard.so is commented out..i think that's what
> you mean..
> by midgard-php, you do mean midgard.so is enabled in php.ini correct? that's
> what i'm basing these answers on.
Yes.
> >- no mod_midgard, midgard-php enabled: server segfaults at startup. The
> >patch does not log anything to stdout or the error log.
> NO...if mod_midgard is disabled(httpd.conf), midgard-php(php.ini) is
> enabled, then get page cannot be displayed error for php files. nothing in
> error_log
And nothing on stdout? But pages do not parse, and apache keeps
running?
> >- mod_midgard enabled, no midgard-php: server segfaults at startup, no
> >text to stdout or error log.
> Yes...but...stdout?? that's just the ouptut from httpd -X? if yes, then
> yes, you are correct...no text to stdout (other than Segmentation fault
> (core dumped) )
Yes, stdout is text to the screen. So mod_midgard dies instantly,
leaving no trace in the log. OK, I'll look for potential troublespots,
and create a logging patch.
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
