Home Forums FineTunedMac Community FineTunedMac Feedback Back up and running!

Just checked another forum and found this:

Networking > Removing Facetime Call History from Mac Replies 17 (15) Views 0

So, what was once correct (for Views) has now been 'corrected' to be wrong. HAL may require ECT.

And every new submission (including this one) seems to result in the following

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@finetunedmac.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 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

This in turn requires repeated attempts to re-submit.

Ain't nobody got time for that.

You must be feeling masochistic as all get-out today!

You've already posted and deleted pretty near the same post three times...presumably having endured the error process in all three instances.

Indeed. By the time you got there, I had already deleted another couple of the same post, leaving only the last attempt.
(I also advised tacit about same via another channel.)

I was getting so frustrated by the posting process that I was ready to quit posting until tacit fixes it, but I thought of a neat possibility, and...it works!

If I type my post and click "Submit" in Firefox, it appears immediately in Safari!

More: If I want to post again, I've got to quit/relaunch Firefox.

Not surprising. At least for the moment I'm finding that, as soon as the 500 error message pops up, going back into the forum finds the post posted.

You deleted three earlier posts (that I saw) before posting the remaining one.

Thanks guys, I'm guessing that we've all generated enough new info for Tacit for now with our Feedback Forum troubleshooting observations.

I've collated and summarized your results and added some of my own for him in the Staff Forum so until he has a chance to pull all of our combined info into his repair process, I would recommend we ease back a bit on our post submissions for now.

FWIW, an "EDIT" or "MOVE" action to an existing post or thread does not result in the same "hang" we've been seeing when pushing the Submit button with a new post or reply.

I plan to use the modified approach of having two browsers open to keep from making duplicate submissions until we get this resolved.

I hope tacit gets to the bottom of this quickly!

In the meantime, though, maybe someone can clear me up on one aspect of this problem that's confusing me...

Since this seems to be a server-side problem, since the server seems to be choking on new posts, why does it reflect in only one browser?

Why does a post on which Firefox is choking render immediately in Safari?

It seems to be choking in Firefox but when it does, I just open another tab/window into Firefox et voilà the post is in fact there.

Hmmm... I don't think that happens in Safari.

Just tried, and the new window hung as the original was hanging...wouldn't load.

Sometimes quitting Safari works for me, and sometimes simply logging out of FTM and back in works, but neither is guaranteed.

I just hit submit and, after a lng wait, got:

"Internal Server Error

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

Please contact the server administrator, webmaster@finetunedmac.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 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request."

I tried to go back a page and hit Submit again but got a message saying the button was disabled. I was about to tried your quite-restart Safari idea when the post appeared.


EDIT: Same thing happened with this post.

ryck: Look back at the previous posts in this thread ... for the observations which are identical to yours.

Here's a new one, sidestepping the 500 Internal Server Error — and also not preventing the post from being posted:

Gateway Time-out
The gateway did not receive a timely response from the upstream server or application.

My last post went through instantaneously, with no sidesteps.
So did this one.
Amazing?! Mayhap we're out of the morass?
Seems so. This is the third edit of this post with no bugs.

Likewise!!!

Update: I'm still finding FTM to be slow to react, though.

A recent post, a few minutes ago, required a quit Safari/restart Safari procedure.

EDIT: But not this one....although it took several seconds.

I thought Tacit had it nailed but I just got:

It might have been nailed, but now it seems screws or even lag bolts may be needed to keep it going.

ADDENDUM this post went through in ~5 seconds. Whatever the problem is it is inconsistent which makes it a lot harder to nail or bolt down.

... as I noted (in post #49486) just before things seem to have been sorted out.

Earlier (in post #49355) tacit remarked that it might have something to do with the new east-coast server. I think that that's pretty obvious. The question is what's wonky with that server and how can the wonkiness be addressed.

I'm testing this out away from my dialup connection using Internet Explorer on a Windows platform with broadband access.

Access and entries are running slickly as a goose sliding in its own excrement (so to speak).

Page generation times still indicate a slowdown (compared to the previous server) of at least double.

EDIT: That message took 40 seconds to be posted after hitting the Submit button

oh this is interesting... I did my usual cmd-click of the the forums that had active threads, and started cmd-clicking threads. I was jogging along fine reading them, till suddenly a cmd-click stalled. And so I just shrugged and went to look at another one while that one loaded.

And it stalled too.

and so did the next, and the next.

finally, all of them unstuck and loaded almost simultaneously.

So it's not just affecting things on a random and isolated basis, these are windows of time where I assume the database isn't responding.
(or the VM is rebooting, or something is defragging or purging ram, etc)

It's a bit like when you do a disk check and your whole computer hangs for 10 seconds while DU has frozen the filesystem for the check. Or when you use the Purge command in terminal.

There's still something going wrong in the submit process when making a post....I just ran a test in the sandbox that took 53 seconds to return me to the thread following pushing the "Submit" button.

EDIT: ...and although the UBB message at the bottom of the completed page for this post read:



it was still over 10 seconds to get back to the thread after pushing the button. Much better than 53 seconds, but not as good as it used to be. (the Edit process gets it done in less than 5 seconds....)

That's my continuing experience with original posts. I find it faster to quit Safari and log back in. Replies to posts, and edits to posts, are fairly quick.

I just posted a new post and followed it up with a now-deleted test post, and both went through in three-four seconds after I clicked on "Submit".

YAY, tacit!!!

Edit: Well, ten-fifteen seconds, anyhow.

We're getting there.

YAY, tacit!!!

Let's see...

"Generated in 1.563 seconds in which 1.161 seconds were spent on a total of 14 queries. Zlib compression enabled."

7 seconds by the clock.

Aside: Huh? I posted this as a reply to a post by joemike that's since been deleted; I thought a post couldn't be deleted once it's been replied to?