wolstech Posted December 8, 2015 Posted December 8, 2015 It appears from the large number of posts I've been seeing that the renewal script is broken for accounts on Stevie. When I tried it myself on a few reported inactives, it only worked on 1 of the 3, and the others stayed "Searching for account" forever and had to be manually unsuspended. Can this be looked at?
Krydos Posted December 9, 2015 Posted December 9, 2015 Only on Stevie, or are Johnny accounts doing the same thing?
wolstech Posted December 9, 2015 Author Posted December 9, 2015 Mostly Stevie, but I have done a Johnny account or two. The accounts are all posted over in the S&Q board. Only one there was Johnny IIRC.
Krydos Posted December 9, 2015 Posted December 9, 2015 Are there certain accounts that it always fails on? Certain browsers that it always fails with? I have yet to be able to reproduce the problem.
wolstech Posted December 9, 2015 Author Posted December 9, 2015 It didn't work on chrome 47 when I last tried it (this actually broke some non-heliohost stuff of mine too at the update...). Pale moon worked but it took several minutes to move beyond searching. I don't have much more info on it. I just notice the tons of users reporting they can't renew all of a sudden. Happened the morning after the Johnny maintenance and appears to be continuing. I'll ask users what browser they used when it happens again. I'm wondering if this is related to load or something...
Krydos Posted December 9, 2015 Posted December 9, 2015 The renew script is just as broken as it's ever been. Since Johnny was rebooted it is translating into a lot more load on Cody too. If Cody has too high of load for too long it breaks httpd, and apache has to restart. The higher the load on Cody the longer it takes to reactivate an inactive account. The longer it takes to reactivate the higher the chance of Cody httpd restarting during the reactivation which leads to the searching message never updating into an error or a success message since the request times out. The only thing that has changed was I added a single line of javascript to prevent people from submitting the form over and over. That's the only thing I can think of. I'll leave this thread open for a while in case someone has some information to add to this discussion.
wolstech Posted December 10, 2015 Author Posted December 10, 2015 I was going to suggest an error callback if it timed out since I know some of our stuff is jquery, but just realized the renew form is a form in an iframe and not ajax... Thanks for looking into it anyway.
Recommended Posts