Originally posted by Ernest Friedman-Hill: There's another recent thread about people seeing a lot of 503 errors; surely these two facts are related. I've been seeing them myself; many in succession around 3:30 EST today.
Yep, they probably are. We may be outgrowing our hardware. Ack!
Awesome, record. No wonder I got so many 503s yesterday, I had to give up in the end.
Joined: May 05, 2000
Apparently at least some of the 503's (probably most of them) were caused by an attack on JavaRanch. Someone was running some kind of utility to copy the entire saloon and was simply overwhelming our servers. We don't know if it was a delberate attack or just someone wanting their own copy of JavaRanch but we have blocked that users IP address and we will be keeping a closer watch on things to look for this kind of assault in the near future.
author and iconoclast
Another record: 22816 Of course, the down side is that we're seeing lots of the 503 messages. The folks at EJIP are now setting up another box compete with the latest version of Linux, all the memory and the dual CPU's (The linux upgrade was required in order to take advantage of the dual CPU's). They're then going to move all of the servers over to this other box, make sure it is all working okay and then .... On the morning of Saturday the 16th, JavaRanch will be brought down, all the current data will be copied over and then JavaRanch will be up and running on the new box. EJIP says it will take about half an hour for this last step. Not bad at all. Thanks to Paul Little at EJIP for managing this transition to the new hardware! And thanks to all of the donors that made it possible!
On the morning of Saturday the 16th, JavaRanch will be brought down
Just out of curiosity, is this planned time the result of analysis on when JavaRanch is least active? (Anecdotally this seems to be the time that the SCJD forum becomes least active.) A few years back, I was asked to cut new software into production at 5am one morning. I was able to successfully prove that this was the worst time to do it (highest traffic) and that the best time was at 11am on a Tuesday morning. It was just counterintuitive to everyones expectations, so noone had ever checked on what traffic was really doing. Regards, Andrew
If you click on that little globe at the bottom of each page including this one, you can drill down to this page: http://extremetracking.com/open;unique?login=jranch This shows that Sat is indeed the slowest day of the week, and shows which times of day are slowest.
The weekends are about three times slower than weekdays, so the weekend sounds like the sure bet. As for morning: Paul Little of EJIP.net is the guy that does all of this sort of work. I suspect that he will have to physically be sitting in the server room to do it. I think morning is better than evening because your brain is fresh and if there any problems, you have a lot of the day to try and fix them. Saturday is better than Sunday because if there are any further problems, you can resolve them over the next day while bothering even fewer people.
author and jackaroo