Distance: 11.92mi. (approximately) Average Speed: 10mph Max Speed: 30mph How I feel: Winded The Route: Link
Distance: 4.09mi. (approximately) Average Speed: 10mph Max Speed: 25mph How I feel: Winded The Route: Link
Distance: 8.25mi. (approximately) Average Speed: 11mph Max Speed: 30mph How I feel: Winded The Route: Link
Distance: 6.46mi. (approximately) Average Speed: 11mph Max Speed: 33mph How I feel: MORE!!! The Route: Link
I just got hit with a minor (for now) panic attack. It's been going for about 10 minutes, and it sucks. :(
It's just like all the others: Not stress, diet, or weather induced. It just happens.
If you're wondering why I'm telling you about this, it's more of a log for me to look back on.
As you are probably aware, I've been having issues with my project servers for the last couple weeks. It seems really odd that they're all doing the same thing on different hardware at different locations, and that they all started acting up at the same time.
So tonight, I checked on one of them and found that it had been up for almost 11 days. Cool. I decided that while my clothes were in the washer, I would reload the OS on the other. Just as I had finished the installation and rebooted, the stupid thing decided to freeze on me. I was frustrated, so I shut it down and went to the grocery store.
When I got back, I was sitting at my desktop (my primary computer), watching a movie. A little ways into the movie, I heard a "beep!" I looked around to see what it was, and it was the one project server powering itself back on! I raised an eyebrow at it, and shortly thereafter the other one locked up. Nice...
After a review of my power distribution, I found that all my computers were sharing the same surge protector, and decided that was the likely cause for this headache. I went ahead and moved the one server to another power strip and powered both back up. Cool, it worked for about 10 minutes, then the one with the fresh OS on it locked up.
I just now realized that the one that locked up is on the same surge protector that both were earlier, and that the other had not locked up yet.
At any rate, this is a very odd situation, especially where the third project server is on the other side of the state and is experiencing the same issues.
I did just shy of 2 miles tonight, averaging 10mph, top speed of 15mph. I completed this in approximately 10 minutes.
Edit: The route
So tonight I asked my buddy from work if he wanted to meet me for a quick bike ride. We ended up riding 6.2 miles with about a 30 minute break at the midway point. On the way back, we did a couple nice sprints. I hit 48.6MPH down a gravel alley, and he hit 38MPH at another point.
I think we're going to try and get a group together to go riding a couple times a week. Where we all sit behind a desk all day, we need the exercise. Hopefully we can get some of the guys from the office to join us. I just need to get back in shape.
This message is for anyone who has pissed me off today:
Chill out. You are all more uptight than I am and you can't take a stupid joke. I tolerate your "jokes" of the same nature all the time, and you have never seen me retaliate as you have towards me today. I don't know what has everyone so on-edge today, but it needs to stop.
This is EXACTLY why my day has sucked so far.
Due to massive amounts of recent service outages from software-related issues, the Wildebeest is getting an OS reload sometime over the next few days. I am in the process of making a current backup of everything, but I make absolutely NO PROMISES. I'm doing all of this remotely, so it would be in your best interest to make your own backups as well.
Yeah, the Wildebeest got a bit of a strangle in the last 24 hours. I decided that since my load graphs as http://tim.gm.skudd.com/ had shown basically no activity on the three project servers that I have running, I would fix it. So, I dropped the Folding@Home client on each (as root), and fired it up. When I woke up this morning, nothing worked, the Wildebeest, Boardbox, and Shazpod were all non-responsive, and I was left looking like an idiot.
I don't think the sister unit and her husband are around today, so the 'beest is still dead-ish. I've left instructions with them on how to fix it, so it's just a matter of waiting for them to get home.
Shazpod was pretty easy to fix, since I had my KVM hooked up to it still from the initial setup. Boardbox, on the other hand, was a much different story. I don't know if it's the hardware or what, but that was the second time I saw what appeared to be a spazzed-out video card, and the system was 100% unresponsive. As such, I had to issue a hard reboot, and it's back online now.
So yeah, if you use the Wildebeest, I apologize for the downtime. Such is life of a project server.
So yeah, I'm not dead. Just kinda feeling near it this week.
I mentioned in my previous post that I had taken it upon myself to notify the appropriate individuals of the spam being hosted on their networks. I am proud to say that 3 of the approximately 7 domains that were notified have responded. The responses varied from "It's already been taken care of." to "We think it's taken care of, but please provide us with your logs."
As such, this project is going to gain new priority and it's own subdomain. I should be able to get everything in place over the next couple of weeks, and by then I hope to have the public "API" in place, so you can help track spammers.
I'll keep everyone updated as progress is made. :)
I blacklisted about 300 IP addresses in the last 4 days, which is good. The new version of the Spam Project database will actually log a lot of information about the spammer, including whatever content they've submitted. It's nice to get a bit of information to make filtering a bit easier.
Oddly enough, the content is originating from Asian-based communities, including groups of Asian students studying here in the US. I'm not saying that all Asian students are doing this, but the majority of the content is coming from these groups.
I've taken the liberty of compiling an e-mail to the public contact at these universities, informing them that such content is being hosted on their servers, and that there is a definite issue with them. Hopefully it'll get something done to bring this down a notch.
The remainder of the hits are coming from random unpatched forums or web proxies, so it's going to be hard to notify anyone.
So I had to code a weblogger for my linux administration course using perl and mysql. It took awhile, since it was my first perl project, but it's available if anyone wants the "code", which is only two cgi files and a custom logging config for apache.
screenie: http://troi.cs.wcupa.edu/~siplus/webinfo-perl-mysql.png (Will probably only be up until the end of my semester...)