Hi Sergio,
On Mon, 23 Jul 2001, Sergio Bruder wrote:
> > > Now that our major problem is resolved, there is another problem: Our
> > > apache is dying with sig11's semi-randomly. Any clues about that?
> >
> Turned up logging level to DEBUG, got this (if you want more than
> that, just ask):
>
> tail -f error_log | grep -B 1 -i "segmentation fault"
> [Mon Jul 23 17:01:05 2001] [debug] mod_midgard.c(136): [client 209.202.148.40]
>Midgard: locating blob=[41]/snapshot
> [Mon Jul 23 17:01:06 2001] [notice] child pid 21672 exit signal Segmentation fault
>(11)
<snip>
> --
> [Mon Jul 23 17:04:48 2001] [debug] /usr/include/midgard/select_db.h(8): [client
>200.251.250.42] Midgard: select_database kept current (midgard)
> [Mon Jul 23 17:04:49 2001] [notice] child pid 21805 exit signal Segmentation fault
>(11)
Hmmm, I'm sorry, but that did not give me any idea on where to start. I
did notice that those seqfaults are very frequent, looking at the
timestamps. I was until now thinking along the lines of 'every now and
then'.
I hope I'm not wasting your time with a couple of wild guesses:
- verify that you don't accidently have multiple versions of the
libmysqlclient library lying around. I've seen lot's of segfaults in the
past when libmidgard apparently used a different lib at runtime than at
compile time.
- verify that you don't accidently are using a php that is compiled with
the built-in mysql support. If there is mysql support in your php is
should be compiled in using a --with-mysql=/path/to/mysql or
--with-mysql=/path/to/mysql,shared. When I made this mistake, my apache
simply wouldn't start, but I've seen reports where is would run, but
produce unreliable results. You can check the compile options by looking
at the output from <? phpinfo(); ?>
- same goes for the version of expat that comes bundled with php. By the
number of reports less likely to be the cause than the ones above.
and further:
- check if mysql reports errors at the time of the segfault,
- turn on mysql logging and find out what query midgard may be trying to
do at the time of the segfaults.
- please list the versions of the various midgard components you installed
(release version, snapshot names or cvs date).
There. Now that is a lot of 'homework', and there is a good chance that I
am barking up the wrong tree completely. Anyway, we need to find some
indication of what is causing the segfaults. The frequency of the
segfaults leads me to believe that the cause is an install error rather
then a bug, but we need to find out either way.
--
'The joy of my life is in Zion - Lauryn Hill'
Armand A. Verstappen * <[EMAIL PROTECTED]> *
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
