NCSA 1.5a on Linux 1.2.13 SIGSEGV's

NCSA 1.5a on Linux 1.2.13 SIGSEGV's

Post by Jason Costomir » Sun, 19 Nov 1995 04:00:00



I compiled and installed NCSA 1.5a this morning on my Linux 1.2.13 (ELF
Slackware 3.0).  When I started it up, things seemed a bit slow on the
box.  I soon found out why.  The httpd processes keep catching SIGSEGV,
and dumping core.  I also tried the binary for Linux ELF from ncsa's ftp
site.  Same thing.  In a 7 second period between the time I started the
httpd, and when I did a 'killall httpd', I amassed an error_log that was
42k in size.

Anyone seen this and overcome it?  If not, I'm going to Apache!

--
Jason Costomiris                     | Finger for PGP 2.6.2 Public Key

My employers like me, but not enough | and genius.  We aim to erase that line"
to let me speak for them.            |                  --Unknown

                        http://www.netaxs.com/~jcostom

 
 
 

NCSA 1.5a on Linux 1.2.13 SIGSEGV's

Post by Michael W. Ho » Wed, 22 Nov 1995 04:00:00



>I compiled and installed NCSA 1.5a this morning on my Linux 1.2.13 (ELF
>Slackware 3.0).  When I started it up, things seemed a bit slow on the
>box.  I soon found out why.  The httpd processes keep catching SIGSEGV,
>and dumping core.  I also tried the binary for Linux ELF from ncsa's ftp
>site.  Same thing.  In a 7 second period between the time I started the
>httpd, and when I did a 'killall httpd', I amassed an error_log that was
>42k in size.

>Anyone seen this and overcome it?  If not, I'm going to Apache!

I'm having the exact same problem on my Slackware 3.0 Linux box.  NCSA
1.4 worked with no problems at all, but 1.5 has been giving me
SIGSEGV's up the wazoo.  Here's just a sample of the error_log:

[Tue Nov 21 17:05:19 1995] HTTPd: Starting as /usr/local/etc/httpd/httpd
[Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
[Tue Nov 21 17:05:19 1995] child error: child connection closed
[Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
[Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
[Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
[Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
[Tue Nov 21 17:05:19 1995] child error: child connection closed

And on and on and on...  I've tried using their precompiled binaries
and tried compiling my own, but haven't had any luck so far.  Has
anyone else out there had this problem and figured out how to fix it?

Thanks in advance...

    //////////////////////////////////////////////////////////////////////////
   //  Michael Holl         "Now next Friday I didn't have the rent...     //

 //                http://www.students.uiuc.edu/~m-holl/                 //
//////////////////////////////////////////////////////////////////////////

 
 
 

NCSA 1.5a on Linux 1.2.13 SIGSEGV's

Post by Douglas Sto » Thu, 23 Nov 1995 04:00:00




>>I compiled and installed NCSA 1.5a this morning on my Linux 1.2.13 (ELF
>>Slackware 3.0).  When I started it up, things seemed a bit slow on the
>>box.  I soon found out why.  The httpd processes keep catching SIGSEGV,
>>and dumping core.  I also tried the binary for Linux ELF from ncsa's ftp
>>site.  Same thing.  In a 7 second period between the time I started the
>>httpd, and when I did a 'killall httpd', I amassed an error_log that was
>>42k in size.

>>Anyone seen this and overcome it?  If not, I'm going to Apache!

>I'm having the exact same problem on my Slackware 3.0 Linux box.  NCSA
>1.4 worked with no problems at all, but 1.5 has been giving me

I WAS having this problem until I changed the owner/group settings.  I
read in other posts with other operating systems that the problem was
the group setting to #-1.  I messed around a bit and changed
owner/group settings and that;s all it took.  I made a 'www' user as
owner and kept #-1 as group and it worked find.  One of the support
people has mentioned this is a 'bug' and will be updated soon.

Just try some different settings for owner and if necessary group and
I am sure your problem will go away.

Good luck

    *************************************************************

    **  Center for Music Research *   904-644-5786             **
    **  Florida State University  *   http://www.music.fsu.edu **
    *************************************************************

 
 
 

NCSA 1.5a on Linux 1.2.13 SIGSEGV's

Post by Nicholas Sydenh » Sat, 25 Nov 1995 04:00:00


I've read that NCSA doesn't like the group being #-1. I believe (though I
haven't tried it) that if you change this, it should be okay.




>>I compiled and installed NCSA 1.5a this morning on my Linux 1.2.13 (ELF
>>Slackware 3.0).  When I started it up, things seemed a bit slow on the
>>box.  I soon found out why.  The httpd processes keep catching SIGSEGV,
>>and dumping core.  I also tried the binary for Linux ELF from ncsa's ftp
>>site.  Same thing.  In a 7 second period between the time I started the
>>httpd, and when I did a 'killall httpd', I amassed an error_log that was
>>42k in size.

>>Anyone seen this and overcome it?  If not, I'm going to Apache!

>I'm having the exact same problem on my Slackware 3.0 Linux box.  NCSA
>1.4 worked with no problems at all, but 1.5 has been giving me
>SIGSEGV's up the wazoo.  Here's just a sample of the error_log:

>[Tue Nov 21 17:05:19 1995] HTTPd: Starting as /usr/local/etc/httpd/httpd
>[Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
>[Tue Nov 21 17:05:19 1995] child error: child connection closed
>[Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
>[Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
>[Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
>[Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
>[Tue Nov 21 17:05:19 1995] child error: child connection closed

>And on and on and on...  I've tried using their precompiled binaries
>and tried compiling my own, but haven't had any luck so far.  Has
>anyone else out there had this problem and figured out how to fix it?

>Thanks in advance...

>    //////////////////////////////////////////////////////////////////////////
>   //  Michael Holl         "Now next Friday I didn't have the rent...     //

> //                http://www.students.uiuc.edu/~m-holl/                 //
>//////////////////////////////////////////////////////////////////////////

--
      .---.        .----------- Nicholas Sydenham
     /     \  __  /    ------   DRA Malvern
    / /     \(  )/    -----     B202

  //// / // :    : ---          
 // /   /  /`    '--
//          //..\\
       ====UU====UU====
           '//||\\`
             ''``
 
 
 

NCSA 1.5a on Linux 1.2.13 SIGSEGV's

Post by Robert Stockma » Tue, 28 Nov 1995 04:00:00




: >I compiled and installed NCSA 1.5a this morning on my Linux 1.2.13 (ELF
: >Slackware 3.0).  When I started it up, things seemed a bit slow on the
: >box.  I soon found out why.  The httpd processes keep catching SIGSEGV,
: >and dumping core.  I also tried the binary for Linux ELF from ncsa's ftp
: >site.  Same thing.  In a 7 second period between the time I started the
: >httpd, and when I did a 'killall httpd', I amassed an error_log that was
: >42k in size.
: >
: >Anyone seen this and overcome it?  If not, I'm going to Apache!

: I'm having the exact same problem on my Slackware 3.0 Linux box.  NCSA
: 1.4 worked with no problems at all, but 1.5 has been giving me
: SIGSEGV's up the wazoo.  Here's just a sample of the error_log:

: [Tue Nov 21 17:05:19 1995] HTTPd: Starting as /usr/local/etc/httpd/httpd
: [Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
: [Tue Nov 21 17:05:19 1995] child error: child connection closed
: [Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
: [Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
: [Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
: [Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
: [Tue Nov 21 17:05:19 1995] child error: child connection closed

: And on and on and on...  I've tried using their precompiled binaries
: and tried compiling my own, but haven't had any luck so far.  Has
: anyone else out there had this problem and figured out how to fix it?

Just try to run an a.out version. That works like a charm.
On a P100 with 32 Mb ram running 32 to 64 childs, the NCSA httpd
is the best you can get for free.

Don't blame NCSA!! Blame the libc and ELF people for letting Linux
die..

Robert

--
++---------------------------++----------------------------------------++
|| R.M. Stockmann            ||   Delft University of Technology       ||

|| phone: +31 15  784395     ||   Section Industrial Catalysis         ||
|| home:  +31 1620 36177     ||   Julianalaan 136                      ||
|| fax:   +31 17  784452     ||   2628 BL Delft  The Netherlands       ||
++---------------------------++----------------------------------------++

 
 
 

NCSA 1.5a on Linux 1.2.13 SIGSEGV's

Post by Jason Costomir » Tue, 28 Nov 1995 04:00:00



: Just try to run an a.out version. That works like a charm.
: On a P100 with 32 Mb ram running 32 to 64 childs, the NCSA httpd
: is the best you can get for free.

: Don't blame NCSA!! Blame the libc and ELF people for letting Linux
: die..

What does this have to do with the libc and ELF people??  Did they sneak
something into the libc and ELF code to specifically look for NCSA 1.5a?  
Come on, that's just a bit too much of the "Grassy Knoll" stuff for me...

A couple of questions...

1) How are these people letting Linux "die"?  It sure seems to be alive
and well to me!

2) How is this a Linux only problem, in light of a post I saw yesterday
describing the exact same problem on Solaris?  Did the big bad libc guys
hack Sun's libc too?

--
Jason Costomiris                     | Finger for PGP 2.6.2 Public Key

My employers like me, but not enough | and genius.  We aim to erase that line"
to let me speak for them.            |                  --Unknown

                        http://www.netaxs.com/~jcostom

 
 
 

NCSA 1.5a on Linux 1.2.13 SIGSEGV's

Post by Eastlig » Wed, 29 Nov 1995 04:00:00


Hi,
Just follow the new 1.5a 'conf' guidlines at the NCSA site and all
will become clear....

As the first response said you need to set up a www user/group for it
to work - its also more secure this way.


 
 
 

NCSA 1.5a on Linux 1.2.13 SIGSEGV's

Post by Jason Hei » Thu, 07 Dec 1995 04:00:00






>>: >I compiled and installed NCSA 1.5a this morning on my Linux 1.2.13 (ELF
>>: >Slackware 3.0).  When I started it up, things seemed a bit slow on the
>>: >box.  I soon found out why.  The httpd processes keep catching SIGSEGV,
>>: >and dumping core.  I also tried the binary for Linux ELF from ncsa's ftp
>>: >site.  Same thing.  In a 7 second period between the time I started the
>>: >httpd, and when I did a 'killall httpd', I amassed an error_log that was
>>: >42k in size.
>>: >
>>: >Anyone seen this and overcome it?  If not, I'm going to Apache!

>>: I'm having the exact same problem on my Slackware 3.0 Linux box.  NCSA
>>: 1.4 worked with no problems at all, but 1.5 has been giving me
>>: SIGSEGV's up the wazoo.  Here's just a sample of the error_log:

>>: [Tue Nov 21 17:05:19 1995] HTTPd: Starting as /usr/local/etc/httpd/httpd
>>: [Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
>>: [Tue Nov 21 17:05:19 1995] child error: child connection closed
>>: [Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
>>: [Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
>>: [Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
>>: [Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
>>: [Tue Nov 21 17:05:19 1995] child error: child connection closed

>>: And on and on and on...  I've tried using their precompiled binaries
>>: and tried compiling my own, but haven't had any luck so far.  Has
>>: anyone else out there had this problem and figured out how to fix it?

The problem is trying to run the server as nobody.  Although this worked
with previous versions, it for some reason does not for 1.5.  The solution
is to create another user to run the server as.  For example, I run mine as
www.  Just add a line to /etc/passwd that looks roughly like the line for
nobody except pick a different UID, say 65534.

Jason

 
 
 

1. NCSA 1.5a on Linux 1.2.13 SIGSEGV's


: : I'm having the exact same problem on my Slackware 3.0 Linux box.  NCSA
: : 1.4 worked with no problems at all, but 1.5 has been giving me
: : SIGSEGV's up the wazoo.  Here's just a sample of the error_log:
: :
: : [Tue Nov 21 17:05:19 1995] HTTPd: Starting as /usr/local/etc/httpd/httpd
: : [Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
: : [Tue Nov 21 17:05:19 1995] child error: child connection closed
: : [Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
: : [Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
: : [Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
: : [Tue Nov 21 17:05:19 1995] HTTPd: caught SIGSEGV, dumping core
: : [Tue Nov 21 17:05:19 1995] child error: child connection closed

: I'm having the same problem with Solaris 2.4 x86. Apparently it's not
: Linux specific.

  I've found at least two places in the code where the error logging
functions try using a null pointer (hostname that hasn't been filled in).

util.c -- Around line 604

    sprintf(errstr,"timed out waiting for %s",
                gCurrentRequest->remote_name ? gCurrentRequest->remote_name : "-"); /* BWA */

http_log.c -- Around line 213

    sprintf(str,"%s %s %s [%s %c%02d%02d] \"%s\" ",
            (reqInfo->remote_name ? reqInfo->remote_name : "-"), /* BWA */

  I've stopped getting those SIGSEGV messages since making these two changes.

--
Brian W. Antoine         "Do all the males around here have trouble with their
Senior Networking Eng       hearing," I asked my new friend as shey watched me
Olivetti North America \|/    and the idiot who had demanded I dance for him.
E. 22425 Appleway     --*--   "Only the ones who don't have mates," said Sarah
Spokane, WA 99019      /|\     as I let my shields flare into life around us.
http://tau-ceti.isc-br.com/ =========== From the Stories of the Family nas Kan

2. Serial Sniffer under Linux

3. help to analyse

4. NCSA 1.5a on Linux 1.2.13: can't allocate buffer

5. in.timed

6. Java for NCSA 1.5a on Linux 1.2.13

7. Problem With CD-ROM

8. NCSA 1.5a running as root on Linux 1.2.13?

9. Virtual Hosts on NCSA 1.5a and Linux 1.2.13

10. NCSA 1.5.1 SIGSEGV (Linux 1.2.13)

11. NCSA-1.5x on linux 1.2.13: SIGSEGV/500 Server Error

12. NCSA 1.5a compatible w/Linuc 1.2.13?