Hi!
I installed the new tarball now and had the same problems and even one
new segfault (but forgot to copy the backtrace and can't reproduce it
any longer), but while I was trying your workaround, I found the real
cause for this whole mess:
While debugging another problem, I recently removed the midcom-static
symlink and replaced it by an Alias in the vhost conf. As soon as I
reverted this change, both the Glib errors and the segfaults were gone,
so it seems the Alias directive is not compatible with the midgard
apache module (I also tried to disable MidgardEngine in a Location
container for the midcom-static alias, but this didn't change anything)
So I'm not sure if this is a known problem or not (I seem to remember
that some issue with alias directives existed in 1.6 or so), but it
seems it wasn't caused by my update to 1.8.6. Sorry for all the trouble!
BTW: Disabling MidgardEngine for the static directory seems like a nice
idea even outside of debugging. Maybe this should be included into the
default vhost conf, because it
a) might be a bit better performance-wise and
b) might make this Javascript bug I've been seeing for years now a
little bit less annoying: On all hosts I'm running, regardless of
browser, some script (haven't found out which one) tries to load a js
file called /midcom-static/Javascript_protoToolkit/.js every few page
loads. This will of course fail, resulting first in a MidCOM run and
then in a 404 error. If MidgardEngine was disabled in the static dir by
default, we could at least skip the MidCOM run before delivering the 404
error.
Bye,
Andreas
Piotr Pokora schrieb:
Andreas Flack pisze:
Hi!
The second one has a reproducability of 100% on certain pages, BTW.
the Glib errors are also still present, but I noticed that they don't
seem to come from Midgard requests, but rather from requests to PHP
files in the midcom-static directory (I put them there because they are
part of a frameset UI and loading them from the database would be
slower, at least it was in my tests)
Tarball:
http://www.midgard-project.org/midcom-serveattachmentguid-a372ebe8eb5f11dc8ace4510a34e2e282e28/midgard_allinone-1.8.7.tar.bz2
Tarball's md5 sum: 12c3c6a84d4ad13d1353cf9fec502697
If second segfault appears again, try this workaround in vhost's
configuration:
<Directory /path/to/static/dir >
MidgardEngine Off
</Directory>
Bye, and thanks for your patience!
Thank you for so much detailed debug!
Piotras
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
