On Fri, Jul 24, 2015 at 01:29:59AM -0400, Benjamin
Lees wrote:
On Wed, Jul 22, 2015 at 6:29 PM, Jim Long
<james(a)umpquanet.com> wrote:
... or ways to produce a verbose logging trail?
I would expect something in the Apache error log for this But I would
also expect MediaWiki to whine or just give you a white screen right
away, so this is pretty strange. Is Postgres executing a query while
Apache is hung?
If it were, I would sort of expect to see postgres soaking up all
the CPU, but it is httpd (apache) that is doing that, so I'm unclear
on what is going on.
Nothing significant in the logs. All PHP Mediawiki interaction
previous to that goes fine, including Mediawiki giving the green
light that the environment is satisfactory to begin installation.
I want Mediawiki to run in a FreeBSD jail eventually, so I'm going
to start over testing it inside a jail. I'll report back with more
detail.
Is there any way to get Mediawiki to give me a verbose debugging log
of the installation process? Then even if I can't see exactly what
it's doing, I can report that it hung after doing X. Right now
I'm not getting any clues at all about what's causing the hangup.
Thanks for the reply!
Jim
You might be able to hack the profiler to dump a list of profile in-out
calls to a file so you can see whereabouts it halts.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [