Women in Technology

Hear us Roar



Article:
  Apache Web-Serving with Mac OS X: Part 2
Subject:   Internal Server Error
Date:   2002-02-02 11:45:00
From:   rtevans
I get the Internal Server Error when I set my browser to http://127.0.0.1/cgi-bin/test-cgi


/var/log/httpd/error_log provides the following message.


[Sat Feb 2 13:49:58 2002] [error] [client 127.0.0.1] malformed header from script. Bad header=bootstrap_look_up() failed (ip: /Library/WebServer/CGI-Executables/test-cgi


I am running
Server version: Apache/1.3.22 (Darwin) on Mac OS X 10.1.2


I have not made any changes to test-cgi.


Excited about the web-server possibilties, but confused about this stumbling block. Any help is appeciated.



Full Threads Oldest First

Showing messages 1 through 5 of 5.

  • Morbus Iff photo Internal Server Error
    2002-02-03 13:36:58  Morbus Iff | O'Reilly Author [View]

    That's a new one to me. I know what the error message means ("bad header"), but not where that "bootstap_look_up" is coming from. There's another CGI script within that same directory called "printenv". Can you run that one at all? Does it give you the same error message? If you edit the test-cgi script, do you see anything in there about bootstrap_look_up?
    • Internal Server Error
      2002-02-19 18:03:22  pbates [View]

      I too get this error. Printenv runs fine. I don't see anything about "bootstrap_look_up" in the test-cgi file. Here is the text of the test-cgi file:

      Thanks.
      Pete Bates

      #!/bin/sh

      # disable filename globbing
      set -f

      echo Content-type: text/plain
      echo

      echo CGI/1.0 test script report:
      echo

      echo argc is $#. argv is "$*".
      echo

      echo SERVER_SOFTWARE = $SERVER_SOFTWARE
      echo SERVER_NAME = $SERVER_NAME
      echo GATEWAY_INTERFACE = $GATEWAY_INTERFACE
      echo SERVER_PROTOCOL = $SERVER_PROTOCOL
      echo SERVER_PORT = $SERVER_PORT
      echo REQUEST_METHOD = $REQUEST_METHOD
      echo HTTP_ACCEPT = "$HTTP_ACCEPT"
      echo PATH_INFO = "$PATH_INFO"
      echo PATH_TRANSLATED = "$PATH_TRANSLATED"
      echo SCRIPT_NAME = "$SCRIPT_NAME"
      echo QUERY_STRING = "$QUERY_STRING"
      echo REMOTE_HOST = $REMOTE_HOST
      echo REMOTE_ADDR = $REMOTE_ADDR
      echo REMOTE_USER = $REMOTE_USER
      echo AUTH_TYPE = $AUTH_TYPE
      echo CONTENT_TYPE = $CONTENT_TYPE
      echo CONTENT_LENGTH = $CONTENT_LENGTH
      • Internal Server Error
        2002-03-03 07:20:56  philocon [View]

        Same problem, same error messages, printenv works fine ...

        Everything worked fine from the end of 2001 up to now. And now this!

        • Internal Server Error
          2002-03-03 14:50:55  philocon [View]

          Problem "solved".

          I took a look at System Preferences' Network panel . Strange things must have been going on there. My IP address was 555.555.555.555 etc etc. So I simply restarted my machine, and everything worked fine again, except for this: In the window's title bar, it still says: 500 Internal Server Error.

          Although I don't understand these things very well, I very much enjoy the articles about Web-Serving.

          • Internal Server Error
            2002-04-03 15:46:52  danastasi [View]

            Your problem seems to have been solved only because you restarted your machine. But, it may crop up again. I just replied to someone else's post about this, so here it is...

            That error will only occur if you start apache while logged in to the terminal. Sometimes when starting a daemon from the terminal, OS X will "forget" who started it and/or where. This will happen with daemons other than Apache, too. I've had the same problem with MySQL.

            One solution is to make sure that the Apache daemon is being launched on startup, not from the Terminal.