Here's the scoop.
I've been tasked by my Masonic Lodge to set up a Web presence. I've been waiting all afternoon and evening to get a VPS provisioned for the Lodge site, so I set the Lodge site up on the back side of this server. I figured as soon as the new VPS was ready, I would just transfer everything over to the new box and everything would be ready to rock and roll. About 45 minutes ago, I got the word the new VPS is up and running. But I was being lazy, after having only spent 15 hours here in the office today. I figured I would just leave the transfer until tomorrow morning and called it a day. I was enjoying my breakfast (hey, isn't the first meal of the day called breakfast?!?) when I saw RPM's number on my caller ID. He was concerned the server had been cracked, but I realized what was happening.
The problem laid in the fact all the caching scripts running on this sever were seeing this site's configuration prefixes, but they were seeing all of the other site's prefixes, as well. And since they were the same prefix (stupid Mike, stupid Mike, stupid Mike), the requests were crossing wires at every turn. Actually, it's a piece of luck any of you were getting to this site at all, because I had the other directory password-protected.
Anyway, the other database has been zipped up, downloaded and deleted, so everything should be back to normal on this one. I've run some tools on this one to reset the caching scripts and everything looks OK from here. If you notice something acting strangely, clear your browser cache and that should clean it up.
Actually, I think if someone had cracked us, I would have been ready to call it quits. It's going to take a pretty sharp cookie to get through the multiple layers of security we've built in here. So take deep breaths and relax, everything is safe and sound.
Move along folks, nothing to see here...
