folding.extremeoverclocking.comNews and Updates - Folding@Home Stats - EXTREME Overclocking

| Reviews | EOC Forums | File Downloads | Folding Stats Contact Us FAH Stats Update: Current 05.14.24, 12am CDT Time Now: 2:50am Next Run: 9 min Stats Home/News - All Summary - All Users List - All Teams List Stats FAQ Stats Export Info Stats Database Info Stats Sig Images Official Folding@Home F@H Support Forum F@H Server Status EOC F@H Forum Team / User Search: TeamID Team Name User Name UserID Help All Donations Help With Server Expenses & Future Features dr EOC Folding@Home Stats - News & Updates [ 1 ] 2 3 4 ... 18 Next » Sorry for the recent downtime. 03.14.23, 11:58am CDT Just recently I finally nailed down a bug with the firewall and DNS that was causing some people random connection issues these past couple months. If you are still experiencing issues please let me know (via the contact us page). Then Sunday (March 12th) the server was hit with a DDoS attack and brought things to a grinding halt. Unfortunately I wasn’t around when it happened and didn’t return home until late that day, so things didn’t get resolved until Monday (yesterday) morning. I was working on updating the color rankings to bring the numbers more inline with current production, but now that things are out of whack from the downtime I’ll have to wait a week for everything to settle. That’s about all I can think of right now. Work has been grinding me into the ground and I just don’t have much energy to do anything else. Holy cow I just realized it has been a whole YEAR since my last post. Where has the time gone?!?!?! Thanks everyone and a small update! 03.07.22, 6:35pm CST First, I just wanted to say a huge thanks to everyone that has sent in a donation recently. It was totally unexpected and you guys are the best! I did pick up an 8-port controller card on eBay, a reflashed IBM M5110 now running in IT mode (based on the classic LSI SAS 2308 chip). I moved my hard drives over to it and ZFS didn’t miss a beat. Now I can put the SSD on the motherboard SATA port and move forward with that. Thank you again so much everyone, your generosity is greatly appreciated and helps keep me motivated to keep working on the site. Second, there have been a few people emailing me about missed updates. Well, glad I coded in that lock file to keep the update cycles from running over each other. It appears that Microsoft’s BingBot has decided to misbehave lately. I don’t know why but it has been crawling at a very excessive rate despite me setting the crawl speed to the lowest possible. Likewise it has been crawling pages that have been explicitly stated not to crawl in the robots.txt file! Pages like the overtakes, futures, and milestones require querying quite a bit of data and doing a lot of on-the-fly processing. Not a big deal for humans browsing the site at a normal request speed, but when a bot decides to pound at it for hours at a time it slows things down significantly! So I’ve decided to go scorched earth on the bots since they can’t behave. Now the web server will block pages bots shouldn’t be crawling (with a 403 access denied error) if their user agent matches the bot list! Hopefully this will once and for all resolve the load issue and updates should go back to their normal times. This is why we can’t have nice things. Yes, I’m still here! 02.21.22, 4:10pm CST Figured I would give a little update since there’s been a number of recent developments requiring my attention. I noticed the other morning the server was under severe load, and checking the logs it started happening late Thursday (Feb-17th) through early Friday (Feb-18th). Digging around it appears to be some sort of bot / crawler that was hitting the site at an ungodly rate of speed from dozens of different IPs (I believe MS Azure cloud). I don’t think it was an intentional malicious act since there was no attempt to obscure / randomize any of the info (beyond utilizing multiple IPs), just some idiot with very poor coding skills and bad judgement. As a quick and dirty temporary fix I just blocked a bunch of Microsoft subnets and also a very specific user agent bit until I can code in a more fine-grained filter. Typically Nginx’s throttling module would catch this type of bad behavior, but I had the matching set to a /24 subnet. The IPs coming from the Azure network were spread out much more, so I adjusted the filter to match based on /16 which should catch it if/when I unblock the subnets from the firewall. Another consequence of the heavy load was the FAH processing scripts seemed to overlap and cause a little oops for one cycle. So I tweaked a few things and now it checks to make sure an existing update isn’t running before starting a new update cycle. While digging through the logs trying to resolve the above issue, I also noticed there were a fair number of queries that for some reason had a slash (/) at the end of the URL query string like literally after the teamid or userid number. This results in the server responding with a 400 (bad request) response since there is more than just the number for that field. I’m going to code in a fix to strip out the slashes so while technically a bad request it will process and return what the user expects. I was trying to get my little development box here at home back up and running as I really don’t like rolling out changes to the production server without testing thoroughly first. If you recall a couple years ago I had the bad RAM stick causing issues, which finally got resolved via RMA. Then sometime last year the hard drives decided to take a major dump. Even though it was two drives in RAID-1, one totally died and the other wasn’t far behind causing the system to freak out. I was able to copy off all the critical files from the dying HD. Fortunately the database is on a separate SSD which was fine. So recently I put in an old spare HD I had laying around (probably a bad idea as it’s just as old as those that died, but it’s all I had) and reinstalled the OS and have been trying to get it configured and back up and running to how things were before. What would really be nice is if I could just throw the SSD in my Proxmox VE server and run the FAH development in a container, but unfortunately I don’t have any spare SATA ports. If anyone knows of a good and cheap PCIe controller that plays nice with Proxmox (debian) and supports SSD trim/discard please drop me a line! So anyhow, once I get the development environment back up and running I vaguely remember that I was in the middle of working on an OS stats page (which the main server has been collecting the data each update, just have to create the pages to display it). Also I was thinking of adding a yearly points / wus table to the teams summary page, much like the aggregate summary. Things appear to be working again... 01.24.22, 11:52am CST It appears the F@H team has fixed their HD issue. First update was a huge jump catching up, and subsequent updates have been pretty steady numbers. It will take a week or so for some numbers and graphs to settle down. Fingers crossed no more issues! Yes, we all know the stats are down! 01.23.22, 9:07am CST It’s not on my end, the stats feed hasn’t updated due to an upstream issue with the F@H servers. According to a twitter post from yesterday ( @foldingathome ): We had a failed drive on the machine that hosts the points database that we are troubleshooting. Apologies for the poor performance right now. The data is safe, and we’ll get things running smoothly ASAP! So we all just have to be patient and let them fix the problem. Unexpected Downtime... 08.08.21, 10:47am CDT Sorry for the downtime these past 24hrs. The datacenter had their main fiber trunk cut in not one, but TWO places! It took the crews a while to find both breaks and they worked non-stop through the night re-splicing. I believe it was like a 150-200 bundle cable (x2 breaks), and re-splicing fiber is a slow and tedious process. Server Move Successful! 07.17.21, 5:40pm CDT As you can already tell since the site is back...