FineTunedMac is now up and running on its new home. The transfer to the new server was rougher than I anticipated, as the database is now quite large indeed, so the transfer took a lot longer than I expected and produced some weird errors along the way. Sorry about that!
The new server gives us considerable room to grow, so I hope this is the last move.
FineTunedMac is now up and running on its new home.
Indeed it is. And with none of the access glitches which you suggested might occur (although I did clear my DNS cache in anticipation of such).
Mazel tov.
The new server gives us considerable room to grow, so I hope this is the last move.
I hope we outgrow it by next year!
I'm finding that the new server is responding a bit more slowly than the previous one did...not major...a second or two...but definitely noticeable and quite annoying.
I'm finding that the new server is responding a bit more slowly than the previous one did...not major...a second or two...but definitely noticeable and quite annoying.
I see that also.
I'm finding that the new server is responding a bit more slowly than the previous one did...not major...a second or two...but definitely noticeable and quite annoying.
I see that also.
Interesting. I'm finding just the opposite, albeit only slightly so. But then it may be due to my dialup connection's slow speeds. Who knows?
I just tried disabling content blockers to no avail.
Really terribly annoying!
To quantify, even when I've seen "Generated in 1.493 seconds", it has often taken as many as 5 seconds to get to that screen.
Update: It's faster in the dead of night.
Interesting. I'm finding just the opposite, albeit only slightly so. But then it may be due to my dialup connection's slow speeds. Who knows?
I spoke too soon. I too am finding significant slowdown (compared with FTM's previous server and other websites').
Curiouser is that every so often — and the fact that it happens at all is disconcerting since I've rarely seen such — access crashes with the warning: Firefox can't find the server. Since the new server came on line, that's popped up about a half dozen times.
Curiouser is that every so often — and the fact that it happens at all is disconcerting since I've rarely seen such — access crashes with the warning: Firefox can't find the server. Since the new server came on line, that's popped up about a half dozen times.
I haven't seen that at all in Safari.
I spoke too soon. I too am finding significant slowdown (compared with FTM's previous server and other websites').
I'm noticing delays when submitting new posts. Sometimes it's fine, other times there's a 5-10 second lag before it takes me to my successful post, and on rare occasions the page times out.
Me being the paranoid person that I am, I try to copy my post before hitting submit, so if it eats it, I have it on my clipboard to try again. If I forget, unfortunately the bbs locks the edit field from copying and I have to hit the browser STOP to unlock it, then select-all/copy, then load the thread again to see if it's there. (it usually is) If not, I try again. But at least I don't lose my diligent work
Huh. I'm not seeing that. I'll keep an eye on the logs and see if anything shows up. It might be coincidence, or it might be that there's network connection (the new server is on the east coast).
I spoke too soon. I too am finding significant slowdown (compared with FTM's previous server and other websites').
I'm noticing delays when submitting new posts. Sometimes it's fine, other times there's a 5-10 second lag before it takes me to my successful post, and on rare occasions the page times out.
Me being the paranoid person that I am, I try to copy my post before hitting submit, so if it eats it, I have it on my clipboard to try again. If I forget, unfortunately the bbs locks the edit field from copying and I have to hit the browser STOP to unlock it, then select-all/copy, then load the thread again to see if it's there. (it usually is) If not, I try again. But at least I don't lose my diligent work
I see the same thing.
I too see delays in posting of the same durations mentioned.
I am seeing massive delays in posting, some with freezes and no indication that the post went through (except to see it later in the forum).
I just got this error message:
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 am seeing massive delays in posting, some with freezes and no indication that the post went through (except to see it later in the forum).
I just got this error message:
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.
Yup. All that and more.
You might want to check out the doubling of your response (posts #49397 and #49398) in
The Death of "lie" thread. That's happened to me several times since server turnover.
And it just happened again while trying to submit 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@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.
(
Look familiar?!)
How about this one ... which also pops up with the new server (and not with previous servers):
Hmm. We’re having trouble finding that site.
We can’t connect to the server at
www.finetunedmac.com.
Generated in 3.521 seconds in which 3.117 seconds were spent on a total of 40 queries.......
Saw the above on initial logon this morning.
Worse than that, encountered the following when I tried to submit this post the first time:
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.
FWIW, I had good internal and external ping speeds and throughput speeds both up and down when I checked my end....
edited to add the error message that occurred on submission....the post had gone through properly despite the error message received.
All of the above except I haven't seen the error messages yet.
I Spoke too soon when I submitted the previous i 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.
UPDATE:I am now getting the error message with every submission and have to re-enter the site to find the post has been made.
The increasing frequency of internal and other server errors manifesting across a variety of platforms and browsers leads one to believe that HAL-like insanity has gripped the new server.
And we all know how
that problem was resolved.
(
Can you say "lobotomy"?)
Ugh. I've been tangling with this problem for days.
According to what I'm reading on the UBB.threads developer forum, UBB.threads does not play nice with the newest versions of PHP and with the security modules installed on this new server I've rolled back to an earlier version of PHP and tried to work around the security mods problem. I hope (fingers crossed) that fixes the slowness and the Internal Server Error problems.
If it doesn't, I'll keep tinkering. I'd hate to have to disable the added security modules, but if I have to, I have to.
I don't know if it's pertinent, but I've found that I experience the "error" problem only when posting a new post; editing an existing one goes through more or less smoothly, i.e. with only a several second delay.
More: Nothing had changed when I posted this.
I've taken to waiting a few seconds after hitting "Submit" and logging out/in. (...which has now stopped working, so I quit/relaunch Safari...GIANT PIA!.
)
Add this issue to the list of problems to be addressed:
Several (new) threads now have replies but zero views, eg —
Mac OS X Applications > Mail Junk mail: Replies 3 Views 0
Networking > Removing Facetime History from Mac: Replies 3 Views 0
So, latter-day HAL continues to flip out.
I've never figured out what "Views" actually means.
Is a poster (also) counted as a viewer or is a viewer someone who's done no more than look?
More to the point, have you viewed those threads (which still show -0- Views)?
Is a poster (also) counted as a viewer or is a viewer someone who's done no more than look?
The original poster (ie, the original post) doesn't count. See some of the new threads that read: Replies 0 Views 0.
Anyone who clicks on the thread normally (ie, in the past, prior to this latest 'error') gets registered as a View; if that person then replies, it gets registered as a Reply.
More to the point, have you viewed those threads (which still show -0- Views)?
Yes, and none of them has changed despite repeated views.
Yeah, so far I've had to remove two duplicate posts from Networking caused by this issue....Rita saw the first attempt using Safari "hang" and so went to Firefox to submit, then found that both attempts had gone through.
I'm still seeing the "hang" on submission as of this morning, but it no longer generates an error response. Attempting to re-submit using Safari results in the ubb message that the submit button is disabled now because the post has already been submitted.
Hope this additional info is helpful.
I wonder if it's significant that my first four posts in this thread were processed slowly but were NOT affected by the error problem?
Add this issue to the list of problems to be addressed:
Several (new) threads now have replies but zero views, eg —
Mac OS X Applications > Mail Junk mail: Replies 3 Views 0
Networking > Removing Facetime History from Mac: Replies 3 Views 0
So, latter-day HAL continues to flip out.
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 ErrorThe 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.
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.
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!
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 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.
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?
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.
My last post went through instantaneously, with no sidesteps. So did this one.
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:
Gateway Time-out
The gateway did not receive a timely response from the upstream server or application.
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.
I thought Tacit had it nailed but I just got:
Gateway Time-out
The gateway did not receive a timely response from the upstream server or application.
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:
Generated in 1.646 seconds in which 1.239 seconds were spent on a total of 14 queries. Zlib compression enabled.
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....)
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.[/i]
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?
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!!!
Well, I don't know about that. I just submitted a post and gave up on seeing the submission go through. However, when I went back to that forum's home page and reloaded the page, my post appeared.
Post-post: the above post happened normally, but the one in the Audio, Video, Photography Forum was greatly delayed.
This "bouncing" back and forth is most annoying!
I just posted in the Lounge, and my post didn't appear until 80 seconds after I clicked "Submit".
Update: And this post appeared after only 11 seconds!
I just went through a series of 4 “Server guilt responding†attempting to access this thread 🤬
I too still see delays in posting. So far, since my last post here, I have not seen any server errors.
I just went through a series of 4 “Server guilt responding†attempting to access this thread 🤬
That'd be something if a server could feel "guilt".
"guilt" is what happens when I use the keyboard on my iPad in a darkened room.
Server guilt or innocence notwithstanding, I'm still getting an occasional
"Gateway Time-out
The gateway did not receive a timely response from the upstream server or application."
screen.