Re: Segfault problems

On Thu, Oct 14, 2004 at 02:07:11PM -0400, Vsevolod (Simon) Ilyushchenko wrote:
> Hi,
> 
> I am running skunkweb 3.4 on a Fedora 1 box with apache 2.0.49-4 (from 
> RPM) and python 2.2.3-7. Every time I try to access any URL, apache 
> segfaults. It does not happen if I do not include the skunk config file 
> into httpd.conf. The skunk logs do not show anything.
> 
> What can you suggest?

I'd suggest, first of all, compiling apache from source and seeing if
you get the same problem; if you don't, but very much want to use the
RPM, then try building apache from the source RPM with the same
compiler you are using to compile mod_skunkweb.  If you can't get a
working configuration simply by starting clean, then you need to
investigate a bit by turning up apache logging all the way (what does
it log before it crashes?) and looking at a core file in a debugger to
see where apache is blowing up.  

I have used that apache version, by the way, and that shouldn't be the
problem.  If you are right that skunkweb doesn't log anything and
doesn't actually get the request from apache, then the python version
doesn't matter (although I wonder why you are using 2.2).

 
> My skunk.conf is: *** LoadModule skunkweb_module
> /usr/lib/httpd/modules/mod_skunkweb.so <Location /> SetHandler
> skunkweb-handler </Location> SkunkWebSocketAddress localhost:9888
> SkunkWebRetries 3 ***

Looks OK.

> My sw.conf is:

Actually, I doubt that the sw.conf matters, since it is apache
segfaulting, not skunkweb.

Good luck!

js
-- 
Jacob Smullyan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBbuJ3uqamFyFXXLIRAjQxAJ4/0GgOmvNuE6ZaZPKdb2Xvl14KywCbByxe
zUd1FVuM5mMXrVlTwWdjrZM=
=ZdW8
-----END PGP SIGNATURE-----