502 Bad Gateway, and website slow

  • ChargedCreeper
    2nd May 2015 Member 0 Permalink

    Is anyone else having trouble connecting to the website lately? I've been off and on getting 502 Bad Gateway, and slow loading, sometimes timeout too. I'm completely sure it isn't my own network at fault, as this is the only site I have such issues with.

    Edited once by ChargedCreeper. Last: 2nd May 2015
  • Sylvi
    2nd May 2015 Moderator 2 Permalink

    @ChargedCreeper (View Post)

     The server tends to do that. For some reason it has been slowly increasing in frequency over the last few years.

  • KydonShadow
    2nd May 2015 Member 0 Permalink

    This has been a problem for a long time.

  • NF
    2nd May 2015 Member 0 Permalink

    502 Bad Gateway/ 504 Bad Gateway, happens to everyone. Blame @Simon for that. The website tends do this to me at night.

    Edited 3 times by NUCLEAR_FOX. Last: 3rd May 2015
  • io
    3rd May 2015 Member 0 Permalink

    If I am not wrong (probably I am) main tpt website delegates some things to other servers like catserv.powdertoy.co.uk or secret servers, if the powdertoy server recives a wrong or invalid answer it will reply with 502 error. Maybe the server recives a little overload and sends a little error and powdertoy.co.uk, to no leak or send weird responses ends connection with error 502 meaning the gateway (powdertoy.co.uk) had an error.

  • jacob1
    3rd May 2015 Developer 1 Permalink
    @io (View Post)
    The actual problem (i'm going to use all the wrong words here) is most likely just disk lag. When it can't read/write to the disk it goes down until the disk lag goes away. That's because all the http workers freeze waiting to finish and there are no new ones to handle any requests, so you get 502 (or 504 / timeout sometimes). That's also why sometimes things like comments or posts did really go through if you get that, it does eventually finish one of the requests (as long as you didn't get 502)
  • ChargedCreeper
    3rd May 2015 Member 0 Permalink

    jacob1:

    @io (View Post)
    The actual problem (i'm going to use all the wrong words here) is most likely just disk lag. When it can't read/write to the disk it goes down until the disk lag goes away. That's because all the http workers freeze waiting to finish and there are no new ones to handle any requests, so you get 502 (or 504 / timeout sometimes). That's also why sometimes things like comments or posts did really go through if you get that, it does eventually finish one of the requests (as long as you didn't get 502)

     

    So basically, an I/O bottleneck? 

  • jacob1
    3rd May 2015 Developer 0 Permalink
    @ChargedCreeper (View Post)
    Yes. And there is nobody to fix it ):
  • Factorial
    3rd May 2015 Banned 0 Permalink
    This post is hidden because the user is banned