Loading...
 
Features / Usability

Features / Usability

Forum List Topic List

Forums » Features / Usability » "HTTP 500 Internal Server Error" when submitting wiki or article pages
 
Thread actions
PDF Print this page
  • Print all pages

    • "HTTP 500 Internal Server Error" when submitting wiki or article pages

    Posted by Gu Lianhua posts: 7

    Hi,
    I'm running tiki-7.0, and everything went all right for a week.
    but I found "HTTP 500 Internal Server Error" from today, every time when submitting wiki pages or articles.

    I'm wondering how to debug? any config would help?

    I can see some "php error message" after every page bottom:


    PHP (5.2.9-2) ERROR (E_WARNING):
    File: D:\vhost\wwwroot\embmapftp\www\tiki\lib\smarty\libs\internals\core.write_file.php
    Line: 44

    Type: unlink(D:\vhost\wwwroot\embmapftp\www\tiki\templates_c\en
    %%1B
    1B7^1B7C5A03%%tiki-plugin_help.tpl.php) function.unlink: No such file or directory



    I'm not sure whether it is causing this matter,
    here's my virtual host's phpinfo:
    http://www.embmap.com/tiki/tiki-phpinfo.php

    please help!

    Reads: 2565
    Link
    Posted by Rick Sapir / Tiki for Smarties posts: 3665 United States

    Internal Server 500 errors are almost always due to some type of server misconfiguration. You said that things were working fine until recently.

    • Has you webhost changed or upgraded anything recently?
    • Have there been changes made to your htaccess or php.ini files?



    HTH,

    - Rick | My Tiki Blog | My Tiki UserPage

    Tiki for Dummies Smarties, the best (and only) Tiki beginner's guide! Learn more...

    Tiki Essentials, the best-selling book for Tiki! Learn more...

    Need more help? Try Tiki for Dummies Smarties: A beginner's guide and Tiki Essentials: What all Smarties need to know about Tiki Wiki CMS Groupware.

    Link
    Posted by Gu Lianhua posts: 7

    Hi ricks99,

    my web host is rented from an internet service provider, they said that no maintaining work was done recently.
    so there's nothing wrong in PHP server, or configuration.

    Strangely that after replacing all tiki-7.0 files in the webserver (only keep the database unchanged), this problem is gone. But nothing is changed in my previous tiki files...

    still have no idea, but this problem is worked-around.

    thanks!

    Link
    Posted by Gu Lianhua posts: 7

    oh, bad luck...

    after using the workaround for only a week, this "HTTP 500 Internal Server Error" happened again!

    and I can do nothing to fix, but to delete the whole tiki7.0 files and re-upload fresh new tiki7.0 files, reconnect to the existing database.

    this workaround works again.

    but I'm worrying that bad things will come after the next week...

    anyone knows what might be the matter?

    Link

    Posted by tvader posts: 2

    I have tracked down the problem but don't know how to fix it yet.
    if you look in your temp folder
    there is a folder called "unified-index"
    if you delete all the files in there, you will get redirected properly and you won't get a 500 error
    however after a few days, those files fill back up and you will have to delete them again.
    i'm not sure what the problem is, but it's something to do with those files and them not getting processed correctly.

    Link
    Posted by Gu Lianhua posts: 7

    Hi tvader,

    that's exactly the thing!
    I've tracked this problem for months, and the "HTTP 500 Internal Server Error" happened every 1~2 weeks, and I can work it around by deleting all files or most files in temp/unified-index/ every time.

    it's annoying, although not quite blocking...

    Link

    Posted by larryg posts: 69

    My website has suffered from the dreaded 500 Internal Server error several times, and each time the problem was related to my website exceeding the resources allocated by the ISP - either a server timeout (a process ran too long) or insufficient server memory (multi-print required too much memory and the server crashed). I solved my problem - temporarily - by adjusting parameters in PHP.INI; but when my website grew too large I eventually had to abandon my ISP (GoDaddy.com) and find an ISP that provided more server horsepower.

    Do you know what server issue you solve by deleting the files in that /temp directory? Perhaps as your website grows you exceed some parameter set by your ISP - max file limits (either file SIZE or file COUNT)?

    -larryg

    Link