21
Oct
We are experiencing some issues with a few of the themes that we have available through our Wordpress site,... read more
01
Dec
As you can see, we've decorated for the season! Whatever holiday you celebrate, enjoy some time with your family... read more
29
Jul
We've just added a bunch of StudioPress themes for WordPress to the ones we already had from WooThemes. That... read more
22
Feb
Well, we're becoming quite the hipsters here! I've just setup our own YouTube channel to host tutorial videos.... read more
19
May
Even before last week's server troubles, we had been working on the process of moving our infrastructure over to... read more
25
Feb
Yep - I'm ALWAYS fiddling with stuff! When we made the switch to WordPress for our own home... read more
06
Oct
Recently, some folks had been saying they thought our system wasn't performing optimally. Â We had noticed the occasional slowness,... read more
22
Aug
We have been experiencing server downtime late yesterday and into today. We are aware of the issue and working... read more
30
Aug
We have migrated our primary database server to new hardware and reconfigured our databases. We started coming back online... read more
03
Mar
We're going to be starting something a little different with respect to Support here at ListingWare. We're opening... read more
Comments (6)
Well, it seems that the trouble may have been some sort of Denial of Service attack on our primary database server. We’re still investigating exactly what went on, but we THINK we’ve got the primary services back up and running now. More in the morning.
OK…so, the previous info seems to hold true: there was some sort of rogue Denial of Service attack wandering around the Internet yesterday and our primary database server was affected.
Denial of Service (DoS) attacks are meant simply to overwhelm server resources in attempts to either gain access to a server or prevent others from gaining access to it. Our server was not compromised to intruders – it simply got overwhelmed in a way that caused several of the large databases on it to become corrupted, causing the server to stop abruptly several times.
This caused some pretty serious disk errors. It’s basically like an 18-wheeler slamming on brakes while doing 70 MPH on the freeway: lots of speed, lots of momentum, lots of chances to lose control.
The bad news: as you saw yesterday, we were down much of the afternoon and some into the evening.
The good news: it seems that all of the databases were recovered successfully with no apparent data loss.
We are still checking the server thoroughly and will keep updating this post with what we find. Sorry again for the downtime.
Things have been intermittent all day – mostly up, but had to take the server down for a while in the afternoon to run some low-level hardware checks. Tomorrow morning, barring anything major, I should be able to send out an email to everyone with more info on the last two days of trouble.
OK, things have been up and down again today – mostly up, but I know the downtime is tough to deal with. We’re going to try to make it up to you. Details to come soon.
We did a few more tweaks last evening and then a few more this morning. There were some periodic reboots for new fixes to take effect, but not long ones.
We’re going to (hopefully) leave things alone and let them run today so you can have as little interruption as possible.
OK – fingers crossed that we’re pretty much back to normal. In fact, we’ve even been able to improve a few things. We’ll try to have a final wrap-up in the morning.
Comments are closed.