500 Internal Server Error (417)

1 Name: !WAHa.06x36 2005-02-21 17:46 ID:FqgLpoAw (Replies) [Del]

Since 500 Internal Server Errors aren't ever really caused by Wakaba or Kareha themselves, but are still a big problem for lots of people, I'm setting up this thread to discuss various problems and solutions related to them.

105 Name: Anonymous : 2007-04-18 04:58 ID:r2MBDqqJ [Del]

[Wed Apr 18 19:41:48 2007] [error] [client 127.0.0.1] Can't locate CGI/Carp.pm in @INC (@INC contains: .) at C:/Program Files/xampp/htdocs/wakaba/wakaba.pl line 3.\r, referer: http://localhost/wakaba/
[Wed Apr 18 19:41:48 2007] [error] [client 127.0.0.1] BEGIN failed--compilation aborted at C:/Program Files/xampp/htdocs/wakaba/wakaba.pl line 3.\r, referer: http://localhost/wakaba/

^ I'm on windows using xampp and I get 500 internal server error with that in the error.log when I run wakaba.pl.
I set the hashbang to #!C:/Program Files/xampp/perl/bin/perl.exe

Any idea what's wrong?

106 Name: Anonymous : 2007-04-18 05:36 ID:Heaven [Del]

>>105
it looks like your perl installation is broken.

107 Name: !WAHa.06x36 : 2007-04-18 08:55 ID:sQ1Tof14 [Del]

Yes. You'll probably be better off grabbing ActivePerl and installing that directly.

108 Name: Shiroki : 2007-05-12 08:43 ID:ubmrViya [Del]

Errr, I'm having some trouble with getting this to work.
When I run wakaba.pl, I get a 500 error and this in the error log:

[Sat May 12 23:38:16 2007] [error] [client 192.168.0.139] Can't locate CGI/Carp.pm in @INC (@INC contains: .) at C:/Program Files/xampp/htdocs/wakaba/wakaba.pl line 3.\r, referer: http://192.168.0.139/wakaba/
[Sat May 12 23:38:16 2007] [error] [client 192.168.0.139] BEGIN failed--compilation aborted at C:/Program Files/xampp/htdocs/wakaba/wakaba.pl line 3.\r, referer: http://192.168.0.139/wakaba/

I tried all the other cgi tests and they work too except for a .pl one it seems, though I did have .pl next to the addhandler for cgi. Any idea what's wrong?
I am using xampp btw.

109 Name: Anonymous : 2007-05-12 18:39 ID:Heaven [Del]

>>108

Somebody posted the exact same question just above you.

Seems xampp is just horribly broken.

Name: Link:
Leave these fields empty (spam trap):
More options...
Verification: