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.

>>300
300get :D

At first, Wakaba was giving me an SQL error, but I solved that (took me a while to figure out that I did), but now it's giving me a 500 error. Apache2 works just fine, all my other CGI scripts and HTML pages work juuust fine. Permissions are at 755, all the hashbangs are intact, so all that leaves are the .htaccess junk (I don't have .htaccess) and mod_suexec.

I have no idea where the install put the mod_suexec stuff.

P.S. Using. Ubuntu 9.10

>>303
I can access the Admin panel successfully and have made my first post, but it's fraught with 500 errors whenever I try to go to another page.

>>303
>>305

ZOMG! I found how to make this work! Yusss. . . Now then! Time to work more on it.

>>307-308
why are you spamming this board with pictures of ugly women?

I can only run perl on cgi-bin, and can't run any other thing not there. Admin.pl works but Kareha.pl and test.pl do not, they give me 500 errors. What can I do?

>>310
Get a better host. You get what you pay for.

[Sat Apr 17 13:13:20 2010] [error] Can't locate config.pl in @INC (@INC contains: . /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 /etc/httpd) at /var/www/vhosts/mysite.com/wakaba.pl line 16.\nBEGIN failed--compilation aborted at /var/www/vhosts/mysite.com/httpdocs/wakaba.pl line 16.\n

I'm trying to run wakaba from my win7 system. I've got Apache Perl PHP and MySQL and they seem to be getting along with each other but I'm running into the Error 500 problem which is almost certainly because of my permissions but I made an observation which confuses me.

Why are there html files in the cgi-bin folder and why does wakaba link directly to them instead of placing or redirecting or including that content from HTML files in the htdocs folder?

I know that its some sort of permissions problem but more like an apache setting that I either can't change or I really don't want to for security reasons. Everything in the cgi-bin folder is treated like a server script and not sent to the client but since wakaba puts them in the cgi folder it manifests as a permission problem.

I did find a variable in the internal paths section of the config.pl file that looked promising but I have found that changing the values prevents it from giving me a 500 error but it won't update the html files.[variable called HTML_SELF]

I know I'm doing something wrong but hopefully someone can point me in the rite direction...

-Ryo

p.s. help =(

>>315
There is no "cgi-bin folder". You are definitely doing it wrong.

>>316
Excuse me but, yes, there is. Dir folder what ever you want to call it, its there. It's part of the default instillation of Apache. You just have to activate it to use any cgi like perl

I'd like to apologize for sounding snippy with >>316. I think i understand what you mean but you could have gone into a bit more detail. there should be no cgi-bin folder because the scripts shouldn't be executed from that directory on the server. since the cgi generates HTML local to the scripts in sub directories if the files are in the cgi-bin folder any referenced files are assumed to be server script and not sent to the client.

that said the cgi has to be in the htdocs folder and the question then becomes how do i set up apache to execute the cgi from there without getting 403(forbidden)/500(permission) errors?

>>318
Right. You don't put Wakaba into the cgi-bin folder, at all. Incidentally that folder is a terrible idea in general.

The example.htaccess supplied with Wakaba is all the configuration you need, presuming Apache is configured to allow .htaccess files. (Rename it to .htaccess)

opps. i had the +ExecCGI on the wrong directory. that fixed it. i think i'm going to write a tutorial on how to get this running on windows for my fellow newbs... heh thanks for the input guys!

>>313
I'm getting this same error.. :(

when i set the permissions to 777 i get a 404 error and when i set them to 755 i get a error: could not write to directory...what do??

[Tue Jul 06 05:26:38 2010] [error] [client 172.17.0.132] File does not exist: /f5/33chan/public/wakaba/wakaba.html, referer: http://33chan.nfshost.com/
[Tue Jul 06 05:26:41 2010] [error] [client 172.17.0.144] [Tue Jul 6 05:26:41 2010] config.pl: Constant subroutine main::DISPLAY_ID redefined at /usr/local/lib/perl5/5.8.9/constant.pm line 115., referer: http://33chan.nfshost.com/
[Tue Jul 06 05:26:44 2010] [error] [client 172.17.0.144] File does not exist: /f5/33chan/public/wakaba/wakaba.html, referer: http://33chan.nfshost.com/
[Tue Jul 06 05:27:57 2010] [error] [client 172.17.0.144] [Tue Jul 6 05:27:57 2010] config.pl: Constant subroutine main::DISPLAY_ID redefined at /usr/local/lib/perl5/5.8.9/constant.pm line 115., referer: http://33chan.nfshost.com/

this is constantly my error log, i feel as if i am missing something obvious but i can not tell

even when i set the permissions to 755 i still get the could not write to directory error

well i got some problems with my wakaba :/
i got that far, that i can run the wakaba.pl but it fails at line 3 and says,
[Tue Aug 31 10:16:20 2010] [error] [client 127.0.0.1] Can't locate CGI/Carp.pm in @INC (@INC contains: .) at C:/xampp/cgi-bin/wakaba/wakaba.pl line 3.\r
and yeah i know dont put it into the cgi-bin dir -.- but idk how to change the xampp settings to compile .pl files in /htdocs :/
any ideas whats wron wit CGI/Carp.pm? i wonder if xampp comes with it :O

> xampp

Just don't use xampp. It seems to be horribly broken.

>>325
CGI/Carp.pm is a core part of Perl, and xampp is shit. (See >>105-109, and http://www.google.com/search?q=site:wakaba.c3.cx+xampp)

dfg

After hours of fighting i have finally hit the wall, perl is supposedly working as test.pl outputs coherently, mysql is propably up and running correctly as even the tables have been created, folders and .pl files are correctly 755 and others 644, apache has ownership of the folders, and the wakaba.pl does not generate any 403 or 500 errors anymore. Only one small thing, when I go to the wakaba.pl and it generates .html and redirects me there, the .html gives me 500 error with apache error log saying [error] [client *] (13)Permission denied: exec of '/var/www/imgboard/wakaba.html' failed
[error] [client *] Premature end of script headers: wakaba.html

>>329
You should only have Apache set up to execute Perl scripts, not all files. Particularly it shouldn't be in a cgi-bin directory or any similar sort of configuration.

#!/usr/bin/perl

print "Content-Type: text/html\n\n";
print "<html><body><h1>Perl is working!</h1></body></html>";

Well I fixed my first error and got it up. However if I chmod 777 res it redirects to wakaba.html which is 404 not found. Leaving as it is the dir is not writable.

Any thoughts?

>>332
Is your base directory - with wakaba.pl in it - writable?

I'm using kahera with mode_image and it works fine except that I get the 500 Internal Server Error when trying to post an image.

Does anyone know of a fix?

>>334
set permissions to 755 and make sure the owner of the all the directories and files is the user that the script is running as.

>>336
I did, I think it's just a shitty server, I've switched hosts.

why is it forbiden?
what should i do?

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

i can not acces admin page,please help me...here the error

Bareword "ADMIN_SHOWN_POSTS" not allowed while "strict subs" in use at admin.pl line 297, <FILE> line 7.
Bareword "ADMIN_SHOWN_LINES" not allowed while "strict subs" in use at admin.pl line 297, <FILE> line 7.
Bareword "ADMIN_BAN_FILE" not allowed while "strict subs" in use at admin.pl line 374, <FILE> line 7.
Bareword "ADMIN_EDITABLE_FILES" not allowed while "strict subs" in use at admin.pl line 267, <FILE> line 7.
Execution of admin.pl aborted due to compilation errors.

I fixed my problem on my Linux server by using Dos2Unix on all the files because of the http://en.wikipedia.org/wiki/Newline#Common_problems.

And I also made apache the owner to the root document folder and as well: res, src, thumb.

GOOD LUCK

No-one ever posted a solution for this:
A directory of 777 recieves an error as the built in security prevents the script from running.
A directory of 755 prevents a file being written and so no posts can be made.

How can one setup the permissions allowing writting without an error being produced?

>>346

Turn off the security, or configure things to run as the correct user.

>>347
I've always wondered how shared hosting does that. Do they run their webserver software as root or something?

>>348
http://httpd.apache.org/docs/2.2/suexec.html

>>349
Is there anything like this in nginx?

>>350
>>349
And is there any reason not to use this?

>>350
No. You can spawn FastCGI servers which run with different UIDs to achieve the same security benefits, though.

>>351
Yes, it's a bitch and is (in my opinion) unnecessarily strict on how you set things up. mpm_itk does pretty much the same thing, but is easier to set up, lets you use crap like mod_php (so you won't have to dick around with getting PHP to run under FastCGI on Apache) and doesn't whine because you use mode 775 instead of 777 on your CGI scripts.

Err, I meant 755, not 777.

>>348-357
Apparently this is how it works on nginx
http://wiki.nginx.org/Faq#What_about_support_for_something_like_mod_suexec.3F

Ugh.. this is confusing the crap out of me.. I did everything as it said and I am getting this error.. "error when writing CGI reply" When posting an image. Message board works fine otherwise.. Also, how do I create new boards?? Sorry for being a newfriend..

>>355
Can't really help with the first problem, but to create new boards you just install Wakaba in another directory.

Okay well, here can you help me about this.. http://www.flizzop.net/forum.html and try to reply.. How do I fix this?

>>357
Check your nginx config. I think you aren't forwarding the pages to fastcgi or whatever properly.

Where do I access that? I don't see it on my cPanel.. :/

>>359
Does your host support Perl?

>>360
...Well, they obviously do if you were able to make threads in the first place... Maybe its a permissions error?

I set them all at 755. Perhaps it is because I am using Kareha hahaha, I wanted to use Wakaba but, it seems a lot more confusing to set up.

>>362
It might need to be 775 depending on what fastcgi is running as. Don't blame yourself; its your host's fault.

I will try it, I will report back in a few minutes.

Fuuu- now I'm getting this:

Software error:

"use" not allowed in expression at config.pl line 164, at end of line
syntax error at config.pl line 164, near "use constant "
Compilation failed in require at /home/flizzop.net/public_html/kareha.pl line 12.
BEGIN failed--compilation aborted at /home/flizzop.net/public_html/kareha.pl line 12.

For help, please send mail to this site's webmaster, giving this error message and the time and date of the error.

But, anyway, I am going to restart.. Just wipe my /public_html/
and do the steps again.

Woo! Got my site to work for the most part! The only issue I am having now is those pesky replies... I am still getting this odd CGI error..

>>366
Could it be that the webserver is configured to block large uploads?

>>367
I don't think text replies can be considered large... Try changing the group of the files to whatever fastcgi is running as. I'm assuming the problem is still permissions related.

i got this error after i finished with a previous error;
how fix??

Error message:
Malformed prototype for ModPerl::ROOT::ModPerl::Registry::C_3a_xampp_htdocs_kareha_kareha_2epl::raw_html_format: $4 at C:/xampp/htdocs/kareha/kareha.pl line 470, line 4. ,

>>370

1. Don't use XAMPP.
2. Don't use mod_perl.

Want to fix all of your issues, have a super fast site, and never have problems again? I run the LURKMORE Wiki, CHANSLUTS, intern3ts, Male General, TranCHAN, TEXTCHAN, and another 10 sites with this:

1. Get a 128MB RAM Xen VPS with Debian 6 x86, it'll cost you something like $15-$25 per year.
2. Install Apache, PHP, MySQL (if you need it) and ImageMagick.
3. Set up your VirtualHost with your web root as something like /home/user/site.com
4. Extract the software to your web root, or a sub folder
5. Set permissions on the following files with the group being your PHP user (since we didn't use suexec): wakaba.pl/kareha.pl as 754, the folders where the software writes to is 755. You will need to set admin.pl and captcha.pl to 754 as well (if you use them).
6. Configure passwords, secret, database, title, everything else.
7. Enjoy your new software.

If you need more help, want to make a donation for fixing your issues, want suggestions on where you get your VPS (I have a very long list of where not to get them, especially), want me to set everything up for you (for a very small fee), want more information or advanced information (suexec, multiuser environment), or anything else, you can contact me at [email protected].

Feel free to visit all of my sites and imageboards every day (easy portals: http://www.scriptin.us or http://www.greedbox.com/top/), as well - preferably with ad blocking disabled.

>>372
This sounds more like a recipe for disaster, if you ask me.

>>373 Simply, that shows how much you know about anything.

>>374
Oh really? Assuming you're >>372, you don't mention the explicit need to enable CGI in Apache, and there is no such thing as a "PHP user" in Debian. Why are you even mentioning PHP in the first place, when it has nothing to do with Wakaba?

Furthermore, Debian's default Apache configuration is a turd and will guarantee shit-poor performance unless you tweak the MPM, especially on a VPS with 128 MB RAM. Coupled with the fact that Debian's MySQL configuration is a memory hog by default, and you have a hosting setup which is worse than free hosting and which will crash your server during heavy load.

>>375 s/PHP user/Apache user

MySQL runs perfectly well by default, not sure where you're getting that it doesn't.

Nobody said that we were using the default Apache config, you just assumed that we were.

I also didn't mention how to actually set up a VirtualHost, which would include enabling CGI to run. Did you want me to hold your hand while you pee, as well?

The above are the steps to get it running, if anyone wants more info, they can search online or contact me. You're just as bad as the retards who try to run Wakaba on free webhosts that are lacking the necessary functions.

>>376

>MySQL runs perfectly well by default, not sure where you're getting that it doesn't.

MySQL uses 40 MB RAM on my 2 GB RAM dedi with a default Debian configuration. That would be ~30% RAM on a system with 128 MB RAM. I'm not able to pinpoint how much RAM my heavily tweaked Apache uses, so I'll just point to Google where there's lots of whining about Debian and Apache's memory usage: http://www.google.com/search?q=debian+apache+memory. On a busy site, this will translate to lots of swapping, which is especially bad on VPSes because of their reduced I/O capabilities. Google "xen i/o performance" for more information on that.

>Nobody said that we were using the default Apache config, you just assumed that we were.

I am not criticising your setup, which I know nothing about. I am criticising your half-assed attempt at creating some sort of magic formula that will somehow automatically "fix all issues". Mind you, you're probably only posting it so you have an excuse to beg for donations on this board.

>I also didn't mention how to actually set up a VirtualHost, which would include enabling CGI to run. Did you want me to hold your hand while you pee, as well?

But you do go into details such as mentioning what packages to install and what permissions to set. Installing software and choosing file permissions requires much more basic knowledge than setting up virtual hosts in Apache. If you assume that the reader already knows how to set up virtual hosting with CGI, then why don't you assume that he doesn't know what software to install or what file permissions to set?

>The above are the steps to get it running.

No, they aren't. See above.

>You're just as bad as the retards who try to run Wakaba on free webhosts that are lacking the necessary functions.

That's the second time you insult me. Are you unable to debate without resorting to ad hominem attacks?

>MySQL uses 40 MB RAM

It can use 20-40MB RAM, yes. Reading the MySQL documentation will lead you to basic information such as turning off InnoDB and setting sort_buffer_size to 1M, bringing MySQL server down to ~11MB.

http://dev.mysql.com/doc/refman/5.0/en/server-parameters.html

>heavily tweaked Apache

lol

>excuse to beg for donations on this board.

You say that as if I expected anyone here to have money.

>But you do go into details such as mentioning what packages to install

No, I didn't.

>Installing software and choosing file permissions requires much more basic knowledge than setting up virtual hosts in Apache. If you assume that the reader already knows how to set up virtual hosting with CGI, then why don't you assume that he doesn't know what software to install or what file permissions to set?

I stated some information that is already stated on this site many times. It's a necessary step that people tend to ignore. The rest of it is for people to fill in themselves, using their brains. If they don't care enough to search for the answers to what I left out, they don't care enough to moderate their imageboard after it's running.

>Are you unable to debate without resorting to ad hominem attacks?

Are you too mentally challenged to be able to ignore it?

>It can use 20-40MB RAM, yes. Reading the MySQL documentation will lead you to basic information such as turning off InnoDB and setting sort_buffer_size to 1M, bringing MySQL server down to ~11MB.

I'm well aware of that, but that's not my point. I'm pointing out that your guide is lacking essential information and you shouldn't have posted it in the first place because it's so incomplete and will lead to nothing but trouble for the naïve people who might follow it. At least mention that CGI has to be enabled (see the next point) and that the server has to be tweaked to run on low amounts of RAM.

>I stated some information that is already stated on this site many times. It's a necessary step that people tend to ignore.

... and enabling CGI is probably the most ignored step, yet the most important one. There are countless posts here from people having problems with wakaba.pl "being downloaded".

>If they don't care enough to search for the answers to what I left out, they don't care enough to moderate their imageboard after it's running.

The same could be applied to everything in your guide.

>Are you too mentally challenged to be able to ignore it?

I tend to hear this when I point out that someone's argumentation is flawed. Anyway, the answer is "no".

вп

I am having trouble with the wakautils.pl I can reach the admin board at 192.16.8.1.2/cgi-bin/kareha/admin.pl but when I try to reach 192.168.1.2/cgi-bin/kareha/kareha.pl I get a message displaying the following: "Software Error: Couldn't write to file "index.html" at wakautils.pl at line 1013.

If it can't write it seems like it would be a permissions issue but I can't pin point where it would be exactly.

> /cgi-bin/

https://www.google.com/search?q=%22cgi-bin%22+site:wakaba.c3.cx+inurl%3A%2Fsup%2F

Content-Type: text/html\n\n
<html><body><h1>Perl is working!</h1></body></html>

syntax error at config_defaults.pl line 8, near "XXXADMINPASSXXX"
BEGIN not safe after errors--compilation aborted at config_defaults.pl line 125.
Compilation failed in require at wakaba.pl line 17.
BEGIN failed--compilation aborted at wakaba.pl line 17.

Can someone help me please? the perl is wrking fine.

>>385
You either:

• edited config_defaults.pl -- You shouldn't ever do that unless you really know what you're doing.
  or
• created a syntax error when you put in your admin password, probably by putting in an unescaped quotation mark -- Fix it.

I'm trying to install Kareha on Nearlyfreespeech, but get:
An error has occurred while handling your request. The most common reasons for this are:

A malfunctioning script or CGI application.
An invalid or inaccessible .htaccess file.
Please contact the site administrator for assistance.

If you are the site administrator:

Enable and check your site's error log for more information.
Check to make sure CGI scripts are set properly executable.
Make sure CGI scripts are uploaded in Unix text file format (newline-only).

Any ideas?

Turns out I'd disabled the error log and forgotten about it. With the error log on, it tells me:

[Wed Jan 30 09:17:26 2013] [error] [client 172.17.0.141] CGI ERROR: A system problem prevented your request from being completed.
[Wed Jan 30 09:17:26 2013] [error] [client 172.17.0.141] Premature end of script headers: kareha.pl

I tried opening kareha.pl in vi and changing the format to Unix, as I had been editing it to fix another problem (turning off strict subs) in an odd little iOS app, but no such luck.

>>392
Well, there you go, you probably messed up the script somehow. Try running it in the command line and see if it spits out errors, perhaps?

Could someone please provide complete instructions on how to get this script running. Perl/GGI is a pain in the ass.

Couldn't write to file "index.html" at wakautils.pl line 1013.

Help?

for some reason, no perl scripts are working for me.

tried a simple test script as well, using the hashbang my host says to use, although I've tried many different hashbangs, and I've tried all the scripts at permissions 755 and 777

#!/usr/bin/perlml

print "Content-Type: text/html\n\n";
print "<html><body><h1>Perl is working!</h1></body></html>";

When I attempt to access the .pl, any of them, my browsers want to download the file and thats it. I am assuming that somehow I am flubbing up the executable, but I haven't found any info yet.

are you hosting this yourself? if yes, i have no idea what's wrong (except maybe the perl dir being incorrect).
else: check that you are allowed to perl (check the host's website (maybe you'll find something in the FAQ or packet options), maybe send the support an email); check perl dir is correct

>200

Same problem. couldn't create child process: 720002: kareha.pl
Trying to host it myself.