Forums >Technical Support>503 Service Unavailable
Are we there, yet?
Periodically getting this error message
No server is available to handle this request.
Only started happening since the server move. Anyone else having this problem or is the problem with my ISP?
2024 Races:
03/09 - Livingston Oval Ultra 6-Hour, 22.88 miles
05/11 - D3 50K 05/25 - What the Duck 12-Hour
06/17 - 6 Days in the Dome 12-Hour.
Prince of Fatness
I have experienced this as well ever since the server move.
Not at it at all.
Occasionally yes.
Dave
Just happened between 11 - 11:15 eastern time.
MM#5991
Would this also affect my Garmin data not uploading?
I guess I will have to input it manually.
Lori
*it's Bertha or me. My money is on me.*
**"There is no growth in the comfort zone and no comfort in the growth zone".---- Sandy**
#RunEveryDay
I've been getting 503 occasionally as well.
Half Fanatic #9292.
Game Admin for RA Running Game 2023.
Connoisseur of Cookies
I've been getting it frequently as well. I've also gotten several "Error 500" and "Error 504" messages. This has all happened since the server move. Clearing cache hasn't helped.
***************************************************************************************
"C" is for cookie. That's good enough for me.
Occurrences seem to becoming more frequent, too.
I had it on and off today as well.
Damaris
As part of the 2024 London Marathon, I am fundraising for VICTA, a charity that helps blind and visually impaired children. My mentor while in law school, Jim K (a blind attorney), has been a huge inspiration and an example of courage and perseverance. Please consider donating.
Fundraising Page
not bad for mile 25
I was about to post that I only had one 503 error in the last couple of weeks, but just now I got a 504 Gateway Time-out, and then,
Also sometimes it takes an unusually long time to get a response from the server.
I am currently alternating between 503 and 504 errors.
503, 504. Whatever it takes.
Hi all,
Ever since the move, the database would encounter an occasional spike in load. I don't know the cause of it and will continue to investigate. The load is so heavy that even logging onto the db server would take minutes. The web servers end up waiting for the queries to come back, and eventually stop accepting web requests because they ran out of db connections. The load balancers in turn would stop routing traffic to the "bad" web servers until no more web servers are available, then you'll see the 503 error.
Anyway, that's probably far more technical than what most people wanted. Regardless, I'll continue digging into the db load problem in the morning.
eric
Thanks for the update, eric!