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.

368 Name: Anonymous : 2012-02-07 06:51 ID:Heaven [Del]

>>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.

369 Post deleted by moderator.

370 Name: ss830 : 2012-05-11 22:30 ID:I+a/upJo (Image: 90x86 gif, 54 kb) [Del]

src/1336800655780.gif: 90x86, 54 kb

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. ,

371 Name: Anonymous : 2012-05-12 01:17 ID:Heaven [Del]

>>370

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

372 Name: Anonymous : 2012-05-12 21:28 ID:Heaven [Del]

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 wakaba@lurkmore.com.

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.

373 Name: Anonymous : 2012-05-13 06:03 ID:Heaven [Del]

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

374 Name: Anonymous : 2012-05-13 06:59 ID:Heaven [Del]

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

375 Name: Anonymous : 2012-05-14 02:58 ID:Heaven [Del]

>>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.

376 Name: Anonymous : 2012-05-14 08:23 ID:Heaven [Del]

>>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.

377 Name: Anonymous : 2012-05-14 11:26 ID:Heaven [Del]

>>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?

378 Name: Anonymous : 2012-05-14 12:42 ID:Heaven [Del]

>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?

379 Name: Anonymous : 2012-05-14 13:37 ID:Heaven [Del]

>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".

380 Name: Anonymous : 2012-06-17 11:19 ID:wsaSOa4u [Del]

вп

381 Name: Anonymous : 2012-07-02 15:21 ID:+2mofvGP [Del]

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.

383 Name: Anonymous : 2012-08-06 22:30 ID:gpjW6xub [Del]

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

384 Post deleted by moderator.

385 Name: Anonymous : 2012-11-20 07:09 ID:dA1EkCYy [Del]

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.

386 Name: Anonymous : 2012-11-20 14:12 ID:Heaven [Del]

>>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.

387 Post deleted by moderator.

388 Post deleted by moderator.

389 Post deleted by user.

390 Post deleted by user.

391 Name: Anonymous : 2013-01-29 15:34 ID:CcqiuBZH [Del]

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?

392 Name: Anonymous : 2013-01-30 01:48 ID:ceIAHv+j [Del]

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.

393 Name: Anonymous : 2013-01-30 02:53 ID:Heaven [Del]

>>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?

394 Name: Anonymous : 2013-03-16 23:04 ID:EHi9NVDP [Del]

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

395 Name: Anonymous : 2013-03-17 14:54 ID:EHi9NVDP [Del]

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

Help?

396 Post deleted by moderator.

397 Post deleted by moderator.

398 Name: Alan : 2014-01-08 15:17 ID:RdERnrWh [Del]

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.

399 Name: Anonymous : 2014-01-19 16:39 ID:8oABxNkD [Del]

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

400 Name: Anonymous : 2014-03-10 11:45 ID:VmM/8thQ [Del]

>200

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

401 Name: Anonymous : 2014-03-11 06:04 ID:da2YkrVi [Del]

>400

Solved. :)

402 Name: squidcats!0Fu5OhBuIE : 2014-04-21 19:14 ID:KRu4bPMG [Del]

thanks
trying it out

403 Name: Anonymous : 2014-09-16 20:12 ID:MHRs8Ptu [Del]

When I access kareha.pl through a browser, it just shows plain text and doesn't do anything. I'm a complete noob when it comes to this stuff, anyone know any causes of this?

404 Post deleted by moderator.

405 Post deleted by moderator.

406 Post deleted by user.

407 Name: Anonymous : 2016-01-27 14:57 ID:fBHv6Ioj [Del]

Alright, so I've just chmodded my Kareha directory to 777, all the subdirectories to 777, and my scripts to 755. When I run kareha.pl, It generates index.html, index.rss, and subback.html, but it spits out a 500 error afterwords.

In my Apache log, there were these two lines that generated any time I made a request for index.html or kareha.pl:

[Wed Jan 27 12:48:26.628422 2016] [cgid:error] [pid 16453] (13)Permission denied: AH01241: exec of '/var/cgi-bin/kareha/index.html' failed
[Wed Jan 27 12:48:26.631729 2016] [cgid:error] [pid 1029] [client 192.168.1.243:57408] End of script output before headers: index.html

Now, as you may notice, I'm running cgi-bin out of /var/cgi-bin/ instead of /var/www/html/cgi-bin/. Could this have something to do with my problem? Basic hello world scripts work fine.

This is driving me crazy. What's even the problem here?

408 Name: !WAHa.06x36 : 2016-01-27 17:15 ID:Heaven [Del]

cgi-bin directories are usually set to try and execute every file. This is not compatible with how kareha works, it needs to be run from a directory where only .pl files are set to use cgi-handler.

409 Name: Anonymous : 2016-01-27 22:25 ID:fBHv6Ioj [Del]

>>408
I see. So would the standard /var/www/html suffice?

410 Name: !WAHa.06x36 : 2016-01-28 00:39 ID:Heaven [Del]

>>409

You'll have to enable cgi-handler for pl files, but other than that, yes.

411 Name: Anonymous : 2016-01-28 03:07 ID:fBHv6Ioj [Del]

>>410
Alright, thanks. I've now gotten to the error that >>26 posted about, and up there you said that it would require some tweaking to work with mod_perl, which is what I'm using. What would be the easier way than that?

412 Name: !WAHa.06x36 : 2016-01-29 09:50 ID:Heaven [Del]

>>411

Use mod_cgi.

413 Name: Anonymous : 2016-01-29 14:01 ID:WTy6LpOU [Del]

>>412

Alright, thanks!

So what would I have to reconfigure to use mod_cgi instead of mod_perl?

414 Post deleted by moderator.

415 Post deleted by moderator.

416 Post deleted by moderator.

417 Name: Wakaba error : 2017-07-23 12:25 ID:RbGs79dL [Del]

While running Wakaba on my apache server I was unable to even get a proper page.

Browser page:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at bkb@cinci.rr.com to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.

ERROR LOG:
[Sun Jul 23 05:16:02.667311 2017] [cgi:error] [pid 2024:tid 1076] (OS 2)The system cannot find the file specified. : [client 98.29.204.188:47451] couldn't create child process: 720002: wakaba.pl

What can I do to fix this?

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