From nobody@hyperreal.com Thu May 22 10:28:36 1997 Received: (from nobody@localhost) by hyperreal.com (8.8.5/8.8.5) id KAA14707; Thu, 22 May 1997 10:28:36 -0700 (PDT) Message-Id: <199705221728.KAA14707@hyperreal.com> Date: Thu, 22 May 1997 10:28:36 -0700 (PDT) From: christopher@hyperreal.com, neitzert Reply-To: chris@razorfish.com To: apbugs@hyperreal.com Subject: binary fails to get socket on any port X-Send-Pr-Version: 3.2 >Number: 605 >Category: os-solaris >Synopsis: binary fails to get socket on any port >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu May 22 10:30:01 1997 >Last-Modified: Sun May 25 14:27:00 PDT 1997 >Originator: chris@razorfish.com >Organization: >Release: 1.2b10 >Environment: SunOS tank 5.5 Generic sun4m >Description: I RTFM, and UTFM (understand) and do the do per instructed. I then kill off all of my httpd processes and restart using new binary. my logfiles report this: [date/time/year] socket: Protocol not supported [date/time/year] - Failed to get a socket, exiting child the only solution from the obvious is that for some reason apache will not let got of the port even after i've killed it. though upon testing it on a higher port i still receive the same error... so maybe not. >How-To-Repeat: i'd be glad to mail a copy of my source though its barley modified >Fix: no, i am reporting it in hopes that you have a solution. %0 >Audit-Trail: State-Changed-From-To: open-analyzed State-Changed-By: marc State-Changed-When: Sat May 24 17:05:21 PDT 1997 State-Changed-Why: Did this behavior persist after you reboot the server? Did you kill the old server properly, ie. by sending a -TERM to the parent (and only the parent) process? Were there any Apache processes still hanging around? State-Changed-From-To: analyzed-closed State-Changed-By: marc State-Changed-When: Sun May 25 14:27:00 PDT 1997 State-Changed-Why: See PR#620. >Unformatted: