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.
I've always wondered how shared hosting does that. Do they run their webserver software as root or something?
No. You can spawn FastCGI servers which run with different UIDs to achieve the same security benefits, though.
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.
Apparently this is how it works on nginx
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..
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?
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.. :/
...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.
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:
"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..
Could it be that the webserver is configured to block large uploads?
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;
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. ,
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:
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@example.com.
This sounds more like a recipe for disaster, if you ask me.
>>373 Simply, that shows how much you know about anything.
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.
>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.
>heavily tweaked Apache
>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 220.127.116.11.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.
<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.
config_defaults.pl-- You shouldn't ever do that unless you really know what you're doing.
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).
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.
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.