Loading...
 
Skip to main content

Features / Usability


Internal Server Error 500

We've been wrestling with this error for several months.

At first, we thought it had to do with the length of documents or reserved words or special characters. All of that may still be true, but what I find after exploring the Web a little is that it has to do with script failure. Apache thinks something is screwy in the PHP being fed to it.

Most recently, I tried to get the sql module to work. I set up the DSN per the instructions on doc.tw.o then created a test page. I inserted one line SQL(db=>memberlist) SE LECT count(*) FROM members SQL
then hit Preview and got the Error 500 message.

We have previously gotten the Error 500 message when words like 'up load' and 'se lect' were in the text of the page. When those words are removed or altered, the page works.

It tends to happen more often when pages are long (that may be psychological. You remember the BIG failures.) which, of course, just means the odds are greater that a reserved word is used, if that's the case.

One on-line source suggests that the path to php.exe may not be correct. I assume that, if it isn't correct, it doesn't work at all.

Surely, others are having this same issue.

Funny. I just got the message from THIS message! I'll alter the suspect words and try again.

That didn't do it. I'll alter the sql statement taking out the curly braces.

Nope. I missed a suspect word in the sql statement.

> Nope. I missed a suspect word in the sql statement.

I also tried this AFTER giving myself authority (Admin->Groups->Gold key) to use db memberlist.

Still blew up.



I tried once to reply to your post and got the 500 error when I had "se lect" in the text (with no space), and then the submit went smoothly when the space was added. A few minutes later I submitted that test post, with "se lect" intact and it also went fine. Meanwhile I found 469 instances of the word at this site, including in wiki pages and forum posts, so obviously a lot of the time having "reserved words" in posts doesn't stop the submit.

It seems like there may be something intermittent thing going on, maybe depending on how the submit coincides with other server activity. I don't have a clue how that could be checked.

I've also gotten the 500 error here trying to submit a post, once in a while, but waited a little while and then could submit exactly the same post with no error. Do you consistently have trouble submitting the same post (i.e., always fails)?

I rarely get the error at other Tiki sites I use pretty intensively, but am not sure if my pattern of use just avoids the pitfalls.

-- Gary

> It seems like there may be something intermittent thing going on, maybe depending on how the submit coincides with other server activity.

My suspicion is that there may be a combination of "suspect" words that crosses a threshold and drops the error message on us.
>
> I've also gotten the 500 error here trying to submit a post, once in a while, but waited a little while and then could submit exactly the same post with no error. Do you consistently have trouble submitting the same post (i.e., always fails)?

Using the SQL statement causes failure every time. That could mean there's something wrong with the statement, I suppose. One of our install team took apart \lib\adodb\adodb-pear.inc.php and found that it may be looking for unix to be part of the string as the protocol.

When I get one of these, I start reducing the up load by halves, previwing a portion at a time, until I get failure. Once I get failure, I always get failure (see below for exception).

>
> I rarely get the error at other Tiki sites I use pretty intensively, but am not sure if my pattern of use just avoids the pitfalls.

I don't think patterns of use can account for it. We've up loaded (copy/paste) pages of documents in which one line would cause the failure. By taking the suspect portion and putting it into a comment, all went well. It can usually be limited to just one sentence or a few words. Once the offenders are removed, all's well. I have taken out one sentence of 10 or so words (none of which was reserved) and had success.

It's very puzzling.

Bill

>
> I don't think patterns of use can account for it. We've up loaded (copy/paste) pages of documents in which one line would cause the failure.

This, I believe, is the key. I've experienced problems in the past when copying/pasting from an application that uses a different encoding than the Tiki.

HTH,

-RickQuestion
Now Available: TikiWiki for Dummies SmartiesQuestion — A beginner's guide to using ))TikiWiki((.

> This, I believe, is the key. I've experienced problems in the past when copying/pasting from an application that uses a different encoding than the Tiki.

The pages we've been copying were taken from HTML generated by a PC, pasted using a Mac into a wiki page being run on Unix. I guess there's a little room there for something to happen.

I wrote a little script to see if there were any high-bit or control characters in the text being copied. Nothing. Just plain text.

Note that I'm not saying some text encoding issue isn't a part of it. In fact, I kind of suspect there is more than one culprit.

Thank you all for helping sleuth this thing out. It is really irksome.

Bill


Today, I had this error when trying to load a document with this paragraph:

Finally, I mounted 12 LED lights (uses 0.06amp) and a rocker switch above the door to illuminate the controls and contents. The LED lights are from Autozone and are made to light a license plate. After about three months on the road I will know if it was worth the work.

I isolated the error to the word "from." Without it, it loaded just fine. As you can see, isolated from the rest of the document, the words "from AutoZone" don't cause a problem. Perhaps this means there's an unclosed or incorrect set of quotation marks that leaves this bit exposed as a raw SQL command?


I can not add new topic to this forum
500 error

> I can not add new topic to this forum
> 500 error

Does what you are trying to add include any of the reserved words mentioned above? If so, put a space in the middle of them (as in up load) and try again. I'd like confirmation that it's not just me against the world. 😀 😀