Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:0

Installation: Apache seg faults on perl scripts

posted by Krow on 02:11 AM October 22nd, 2002   Printer-friendly   Email story
I've read many, many posts on google, etc. about this problem, but no real solutions that have worked for me.

I've downloaded the latest apache, mod_perl and slashcode. I can install everything, but when I try to access a perl script the browser sends a couple of requests, and then I get a "Document contains no data error" and the general server error log has

child pid 3305 exit signal Segmentation fault (11)

I can access the shtml files just fine and the slash daemon is running no problem.

Thank you for your help,
Sean Forman ---------------------------------------
[root@ns1 root]# /usr/local/apache/bin/httpd -V
Server version: Apache/1.3.27 (Unix)
Server built: Oct 22 2002 02:22:46
Server's Module Magic Number: 19990320:13
Server compiled with....
-D HAVE_MMAP
-D HAVE_SHMGET
-D USE_SHMGET_SCOREBOARD
-D USE_MMAP_FILES
-D HAVE_FCNTL_SERIALIZED_ACCEPT
-D HAVE_SYSVSEM_SERIALIZED_ACCEPT
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D HARD_SERVER_LIMIT=256
-D HTTPD_ROOT="/usr/local/apache"
-D SUEXEC_BIN="/usr/local/apache/bin/suexec"
-D DEFAULT_PIDLOG="logs/httpd.pid"
-D DEFAULT_SCOREBOARD="logs/httpd.scoreboard"
-D DEFAULT_LOCKFILE="logs/httpd.lock"
-D DEFAULT_ERRORLOG="logs/error_log"
-D TYPES_CONFIG_FILE="conf/mime.types"
-D SERVER_CONFIG_FILE="conf/httpd.conf"
-D ACCESS_CONFIG_FILE="conf/access.conf"
-D RESOURCE_CONFIG_FILE="conf/srm.conf"

[root@ns1 root]# perl -v

This is perl, v5.6.1 built for i386-linux

Copyright 1987-2001, Larry Wall

[root@ns1 root]# mysql -V
mysql Ver 11.18 Distrib 3.23.51, for
pc-linux-gnu (i686)

I did not compile perl or mysql myself as they were already on the server

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • In case anyone needs to see this.

    Compiled-in modules:
    http_core.c
    mod_env.c
    mod_log_config.c
    mod_mime.c
    mod_negotiation.c
    mod_status.c
    mod_include.c
    mod_autoindex.c
    mod_dir.c
    mod_cgi.c
    mod_asis.c
    mod_imap.c
    mod_actions.c
    mod_userdir.c
    mod_alias.c
    mod_access.c
    mod_auth.c
    mod_setenvif.c
    mod_perl.c
    suexec: enabled; valid wrapper
    /usr/local/apache/bin/suexec

  • Do you, at the bottom of the Apache httpd.conf file have a line that says:

    include /usr/local/slash/httpd/slash.conf

    This is needed by slash. Did you follow the INSTALL instructions to the letter?

    --

    --
    It's either on the beat or off the beat, it's that easy.
    • Thank you for the help.

      Yes, to both questions.

      After digging a bit more. It is looking like an apache problem. Apache failed in some of its tests, and I'm guessing that formatting apache is the issue. There was/is a previous version of apache on the server (though I'm certain I'm running the new copy).

      Is it necessary for Apache to pass all of the tests? I don't have all of the results available at the moment.

      thanks,
      sean

      • If you follow the directions in INSTALL, and build Apache with Mod_perl like it says, it shouldn't fail.......
        --

        --
        It's either on the beat or off the beat, it's that easy.
  • I am not sure if your situation is the same or not, but there was a similar thread this week on the mod_perl list.

    The consensus seemed to be that there was faulty memory in that case - have your tried dropping/swapping out your ram one stick at a time?
    --
    www.i18n.com News | Tools | Process for Global Software
  • In case anyone stumbles upon this looking for help.

    It turns out that the old apache install was causing the problems. The header files were messing up the new install.

    To get it to work I (first backed up) and then nuked the /usr/lib/apache folder that was previously installed. I also had to nuke some perl files. /usr/lib/perl5/site_perl/5.6.1/i386-linux/auto/Apa che /usr/lib/perl5/site_perl/5.6.1/i386-linux/auto/lib apreq /usr/lib/perl5/site_perl/5.6.1/i386-linux/Apache

    After doing the last one, I