Okay, I'm having some problems. I'm testing out kareha (3.0.9) on my Linux home server with Apache 2 before actually making a proper site. I was having some permission-related 500 errors, and now all dir permissions are fixed. I can view kareha/ and its subdirectories as well as look at non-executable files in them as text, like example.htaccess and the css templates. Running kareha.pl from a broweser, however returns a 500 error still, though not because it cannot write or read a certain directory. Here's some relevant info from error_log:
[Wed Mar 01 12:27:12 2006] [error] [client 192.168.1.68] File does not exist:
/var/www/localhost/htdocs/favicon.ico, referer: http://192.168.1.68/kareha/
[Wed Mar 01 12:27:14 2006] [error] Can't locate config_defaults.pl in
@INC(@INC contains: . /home/httpd/perl /etc/perl /usr/lib/perl5/site_perl/5.8.7/
i686-linux /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl /usr/lib/perl5/
vendor_perl/5.8.7/i686-linux /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/
vendor_perl/5.8.6/i686-linux /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/
vendor_perl /usr/lib/perl5/5.8.7/i686-linux /usr/lib/perl5/5.8.7 /usr/local/lib/
site_perl /usr/lib/apache2) at /var/www/localhost/htdocs/kareha/kareha.pl
line 13.\nBEGIN failed--compilation aborted at /var/www/localhost/htdocs/
kareha/kareha.pl line 13.\n(Hope that formats correctly.)
This seems related to the path specified in kareha.pl: use lib '.';. I assume it isn't expanding . to the dir in which kareha.pl is situated. If I edit kareha.pl and input the full path, it still doesn't work. I didn't really think it would. Disabling suexec does nothing as well. test.pl works in kareha/, so mod_perl seems to be fine.
I apologise if I'm missing something obvious, but I'm sort of at a dead end at the moment. Help would be appreciated :)
Your problem is most likely that you're using mod_perl, if I read that correctly. It is theoretically possible to run Kareha on mod_perl, but it requires some tweaks, and I've never gotten around to testing it properly.
Same error in the error_log too? That's pretty weird.
Wakaba doesn't work with mod_perl, but maybe if you installed it and didn't actually use it, just so that it could find that damn file... Hell, I dunno, that's all mighty strange.
That's not a 500 Internal Server Error.
Also, that references mod_perl, which Wakaba does not support, and also sounds sort of like all files are not in place.
I try to run wakaba script on a Debian Sarge vServer with root access. Apache/2.2.3 (Debian) PHP/4.4.4-8+etch4 mod_perl/2.0.2 Perl/v5.8.8 Server
I keep on getting Internal Server Errors but i am able to run your and other perl test-scripts.
The apache error.log says this:
-------------------------------
[Mon Sep 10 17:51:59 2007] [error] Can't locate config.pl in @INC
(@INC contains: . /etc/perl
/usr/local/lib/perl/5.8.8
/usr/local/share/perl/5.8.8
/usr/lib/perl5 /usr/share/perl5
/usr/lib/perl/5.8
/usr/share/perl/5.8
/usr/local/lib/site_perl
/etc/apache2)
at
/var/www/web1/imgboard/wakaba.pl line 16.\nBEGIN failed--compilation aborted at /var/www/web1/imgboard/wakaba.pl line 16.\n
-------------------------------
Any Ideas? Is it possible that this error accurs because im using mod_perl? And if, what schould i use instead of mod_perl?
You should definitely not use mod_perl, just plain CGI.
>>141
I have a new question now.
How do I disable mod_perl and use just CGI.
I'm using xampp with a perl add-on that gives me 5.2.3 mod_perl/2.0.3 Perl.
This is my first time using perl and shit is confusing me.
Ask the xampp people. I have no idea.
You might want to not run xampp. I haven't heard anything but problems with it. I think it uses mod_perl by default? Disable that to start with.
Posting this because I checked my hashbang, made sure +ExecCGI was added as an option, and .pl is an addedhandler, and the .htaccess file should be fine as well. That being said, I get the following from apache, even if the scripts are in /cgi-bin:
[Mon Mar 02 20:45:12 2009] [error] Can't locate config.pl in @INC (@INC contains: . C:/xampp/perl/site/lib/ C:/xampp/perl/lib C:/xampp/perl/site/lib C:/xampp/apache) at C:/xampp/htdocs/kareha/kareha.pl line 8.\nBEGIN failed--compilation aborted at C:/xampp/htdocs/kareha/kareha.pl line 8.\n
Line 8 is:
BEGIN { require 'config.pl'; }
Working with a fresh install of xampp w/ perl addon, activestate's perl exec is in the directory that the scripts are looking for but even if I use the one from xampp I get the same results. Oddly, I get the same results even if I delete the hashbang line.
Nevermind.
Apparently (for anyone else in the future) mod_perl may be installed extraneously by xampp. Kill apache and run setup_xampp.bat, and tell it to reconfigure without mod_perl. Then start apache again.
Whatever you are doing, it is completely wrong. I really can't recommend using xampp at all, it seems half the problems in this thread are caused by it. You really should use a plain Apache and plain Perl. You especially should not use mod_perl, which xampp seems to be fond of installing.