http://www.perlmonks.org?node_id=297555

Nik has asked for the wisdom of the Perl Monks concerning the following question:

This node falls below the community's threshold of quality. You may see it by logging in.

Replies are listed 'Best First'.
Re: help with an error 500 messge...
by davido (Cardinal) on Oct 08, 2003 at 22:42 UTC
    Once again, Nik, your enthusiasm is exceeding the level of care in your methodology.

    First, in developing a CGI script, you surely, by now, understand that there is an error log file on your webserver that will contain a more detailed description of the problem. 500 server errors should be seen as simply a flag telling you that you ought to look at the error logs to find out why your script is failing. What is the error log telling you? We need to know to help.

    Better yet, use the CGI::Carp module (documentation on how to use it is provided along with this core module). With Carp you can send the "fatals" (error messages that result in program termination) to the browser so you don't have to go digging through an error log. Then tell us what fatal message is getting sent to the browser.

    Next, this being your umpteenth (ok, 23rd or so) post, and having already graced the "Worst Nodes of the Week" list a couple of times, by now you should understand that for us to help we need real, concrete specifics. If you found Abigail II's quip unhelpful consider the reason; the question was similarly unhelpful. We know nothing about your script. We know nothing about the environment in which it is running (other than the fact that it's Apache 2.0.40 for Red Hat Linux), and we don't know what mistake you made any more than you do if we aren't given better clues. Just as we can't read your mind, we can't read your server's error log for you.

    You are getting this error because you've instructed the server to do something it can't. That's as much as I can tell you without more information.

    Come back and tell us what the error log says. Give us an example of the code that causes the error (not the whole thing, narrow it down). Then maybe we can begin to provide suggestions that assist YOU in hunting down the problem.


    Dave


    "If I had my life to do over again, I'd be a plumber." -- Albert Einstein
Re: help with an error 500 messge...
by bradcathey (Prior) on Oct 08, 2003 at 12:45 UTC
    Did you check permissions (chmod 755)? Is your localhost running any modules that your remote host is not? Are there any file path issues? Did you check the error log? Add:
    CGI::Carp qw(fatalsToBrowser);
    to the beginning of your script and see what it returns.

    These are frustrating errors, but there are ways to hunt them down. It's probably something really simple that you overlooked.

    Carry on!


    Follow up:
    I ran a quick Google on "perl error 500" and came up with two ostensibly helpful sites here and here.

Re: help with an error 500 messge...
by Abigail-II (Bishop) on Oct 08, 2003 at 13:08 UTC
    You have a bug on line 17.

    Abigail

      Abigail,
      Just curious. Where do you see this code?
      Thanks.

      Redfaced bradcathey sees he's been had.
      Time to lighten up.

        He's being sarcastic. There's absolutely no way of knowing what the problem is because the OP question was so vague.

        -- vek --
        :)

        $Abigail += $bradcathey; $bradcathey = undef;
Re: help with an error 500 messge...
by PodMaster (Abbot) on Oct 09, 2003 at 07:37 UTC
    I'm a little disappointed nobody pointed you to Tutorials yet, so i'm doing it The tutorial in question is very thorough.

    MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
    I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.

    A reply falls below the community's threshold of quality. You may see it by logging in.
Re: help with an error 500 messge...
by rdfield (Priest) on Oct 08, 2003 at 13:32 UTC
    Are you running Apache2 on "your localhost"? If you're not then all bets are off.

    rdfield

    A reply falls below the community's threshold of quality. You may see it by logging in.