Kevin's Watch

It's no problem if that's all it is.

haha nah it's something I need to consider having done properly because it will only get worse as tie progresses. Now if only I had access to a whizzkid with time on their hands

I keep getting Syl's profile whenever I click on anyone elses link to "veiw all posts by this user"

I wonder if Syl is actually everyone else on here...

That's weird. It works for me.

Try clearing your cache?

--A

Yes - most Watch problems are actually cause by user error

Vain wrote:Yes - most Watch problems are actually cause by user error

it's fall back position - isn't it?

sgt.null wrote:

Vain wrote:Yes - most Watch problems are actually cause by user error

it's fall back position - isn't it?

Fine.

Most Watch problems, other than allowing null as a member, are actually cause by user error.

Feel better now?

___ wrote:

sgt.null wrote:

Vain wrote:Yes - most Watch problems are actually cause by user error

it's fall back position - isn't it?

Fine.

Most Watch problems, other than allowing null as a member, are actually cause by user error.

Feel better now?

you have all had your chances to get rid of me. i was actually banned at one point.

Though you clearly have the mark of corruption upon you, we bear with you, hoping to one day cure you. We know our forbearance leaves the Watch vulnerable to desecration, but we feel that our decision, having been born of compassion, cannot be warped into desecration, unless THOOTP does the unspeakable and resurrects dANdeLION.

by the whispered name of Phil Cobb - you will not convert me!

Avatar wrote:That's weird. It works for me.

Try clearing your cache?

--A

Seems to have worked...

that was freaky.

The crit errors are back with a vengeance.

Murrin wrote:The crit errors are back with a vengeance.

can we assign intent to such things?

It's become routine for me to see the DB errors about 5:30-6:00 PM EST. Could be traffic related?

Why has the board been so glitchy lately? It's very slow to load and gives me "critical php errors" on a regular basis.

Don't have much loading probs, but I do get the various errors every now and then. Likely to be size and activity related...no way around as far as I know...

--A

It seems to be an issue around 5-6pm EST time, I will see criticial DB errors, almost every night. I bet a dollar to a donut there's a database backup or some other routine maintenance going on at that time, interfering with the service.

It's about 11:30 EST. I just tried to post, had to try 3 times before the post was made and during the second attempt I got this:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster@kevinswatch.ihugny.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

So that theory's not holding much water in my book, wf.

I think what's happening is that the server is so busy that it's taking extra long to process the request for a new post. And there must be a time limit set for replying to the poster that their post was successful. Because I can almost always find my post when I go back into the forum after a server error. It might not show up on the "orange dot tree" right away, but it does eventually. That tells me that the server is still processing the request, but sends the "server error" message because the time limit for the response to the poster has run out.

Oh computer geeks with more knowledge of these things than I, am I explaining it correctly?

MsMary wrote:It's about 11:30 EST. I just tried to post, had to try 3 times before the post was made and during the second attempt I got this:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster@kevinswatch.ihugny.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

So that theory's not holding much water in my book, wf.

When you get these errors the post you were making almost always has gone through, and it's just the next page breaking. For example, you've actually posted three times in that thread in Malory's.