Re: Getting random "Internal Server Errors"

It can always be a problem with the request being sent to the server. Are your sure it is your perl-script that is receiving the request instead of it going somewhere else? I mean it could be trying to call a different script than what you thought, or possibly a different web server. There is also a possibility that there is a problem with a proxy server.

Chances are that this is probably not a perl script issue as it is an environment issue.

Comment on Re: Getting random "Internal Server Errors"

Replies are listed 'Best First'.
Re^2: Getting random "Internal Server Errors" by polki (Novice) on May 05, 2009 at 19:15 UTC
I agree, this is most probably an environment issue, but i just don't know where else to search, that's why i'm asking and appreciating every single answer... I can quite surely exclude a wrong script or wrong server. I called the prototype-ajax-object with the full URL to the perl script that should handle the request. I can also exclude a proxy since i'm only testing this on my home server within my local network. The requests don't pass any proxies on their way...	[reply]
Re^3: Getting random "Internal Server Errors" by przemo (Scribe) on May 05, 2009 at 19:25 UTC
If the browser is Firefox, install LiveHTTPHeaders add-on and take a look at outgoing requests seeking for (not-you-server?) ones, which result in error 500.	[reply]
Re^4: Getting random "Internal Server Errors" by polki (Novice) on May 05, 2009 at 19:34 UTC
All the requests (regardless of status 200 or 500) that show up in LiveHTTPHeaders have the right destination...	[reply]
Re^2: Getting random "Internal Server Errors" by polki (Novice) on May 05, 2009 at 19:25 UTC
One more thing that proves that the request is sent to the right script: As i wrote the script gets executed EVEN in the cases i get the error! The script starts/stops some services and even if i get the error, i can see that the services have been started/stopped just as they should. In other words: The script is executed EVERY time it is called, it just randomly exits with the appearance of not having been successful...	[reply]