The datacenter is working on the issue with kiwi. As soon as its back up we will notify everyone.thanks for your patience.

update : kiwi is backup – we are monitoring it to determine the issue

Update : We have identified an issue with a portion of the file system and are working to resolve it. You may be unable to post to your website and have some email delivery issues for the moment.

Update : Kiwi is going up and down while we attempt to fix the issue. Please bear with us.

Update : All of the accounts on kiwi have been transferred over to a temporary server while the new server is being provisioned. We apologize for the delay but it turns out that kiwi was not salvageable from an operating perspective however ALL data was recovered thanks to the nightly backups we take for “just in case” moments such as these.

9/25 We have transferred all of the accounts from Kiwi over to our Pinki server, which may cause somewhat of a slow down while that happens, overnight.  Starting Friday morning, we’re transferring those accounts back to the newly provisioned server and at that point, things should calm down.  Clients on both Kiwi and Pinki may experience intermittent periods of slow load times today while our techs get this issue sorted out – - it shouldn’t be for long and we super appreciate your patience!

This notice is for clients on the PINKI (76.74.236.95) Server only *

Yesterday, 8/23/09, we experienced a sudden (without warning) hard drive failure on the Pinki server. Usually, we get notifications that the hardware is having some sort of issue that we need to look into, which gives us time to diagnose and troubleshoot. This time, however, there were no warnings – it just happened without notice…one minute the drive was functioning, the next minute not. Machines are not infallible – - and web servers are machines, after all. It’s frustrating and scary all at the same time!

We discovered this problem late yesterday afternoon and immediately went to work with our DataCenter (and hardware providers) at ServerBeach and commissioned a new server. The great news is that we do full adn complete backups of all client accounts on a nightly basis and store them on a separate drive for safekeeping. Once the new server was up and running with a new copy of the Operating System – we began the account restore and things are about 99.9% back to normal right now.

We do continue to work on the new server configurations, however your sites are in working order at this time. Some people have reported a few items that are off – - a couple missing posts, template tweaks that are not there anymore, etc. We are currently working on those issues on an individual basis.

Because our own web site was down during this time, as well – - we’ve been providing updates on our Twitter account as much as we possibly could during this outage. If you do not follow us on Twitter – it’s probably a good idea to do so at times like these: http://twitter.com/BlogsAbout

We want to thank everyone for their patience, and for those of you who write and Twittered words of support and encouragement – we are grateful. We realize that times like these are frustrating for everyone – including ourselves. So, thank you for your patience and understanding during this time. PLease know that we continue to work on smaller issues on a case by case basis and are getting through them as quickly as we can.

One thing that we have noticed, for WordPress users – when you go to update a plugin, or update your WordPress installation – WordPress is asking you for your FTP login information. It has never done this before and this is a function of our server configuration that we are working to resolve. In the meantime, you can just input the information as requested – or, there is a work around for individual sites that you can read about in the WordPress Support forums here: http://wordpress.org/support/topic/242686#post-1180641 (RESOLVED)

* – If you do not know what server your account is currently on – you can locate the IP number of your server in the left menu of your CPanel. Compare your IP number with the three I’ve listed above to find out which server your account is currently hosted on. Or, leave a comment on this post and I’ll do my best to help you determine your server assignment. Thanks!

Server Alerts: for those clients whose accounts are on the following servers (*):

• OZ - 72.51.46.32
• TALIS - 72.51.38.154
• BUBBA - 72.51.34.113

We are performing a server migration to new, more powerful server system.  Skipping all the geek speak – basically it means more RAM (memory), more processors (CPU) – which means better, faster and more powerful, overall.  Accounts backups to an offsite location have been completed and we expect very minimal (if any) downtime for accounts on those three servers.  If you experience any problems with your site, please understand that the server migration is necessary to upgrade the equipment across all our server systems to better serve our clients and improve performance, and ultimately your hosting experience.  The migration will be taking place in the wee hours of the night/morning – we chose these times because they are the lowest in terms of web traffic and readership (when *most* people are sleeping..except me, I’m always awake when the rest of the world sleeps.  heh)

Currently, we are having an unrelated hardware problem on the TALIS server that our techs are working on, as I type this.  The migration of the accounts off TALIS to the new server will remedy the problem – however, we are working on getting TALIS fixed to remedy server load issues in the meantime.  As always, we appreciate your patience and your support!

Over the next 24 – 48 hours, our techs will be prioritizing questions and requests for support on an ‘urgent‘ basis only.   Questions and support requests requiring urgent attention will be attended to immediately.  General inquiries, requests for design assistance, upgrades to software, etc will be attended to starting Monday morning.  This weekend, our focus is on making the migration go smoothly for everyone and emerging on Monday morning with some powerful new systems over here!

* – If you do not know what server your account is currently on – you can locate the IP number of your server in the left menu of your CPanel.  Compare your IP number with the three I’ve listed above to find out which server your account is currently hosted on.  Or, leave a comment on this post and I’ll do my best to help you determine your server assignment.  Thanks!

The WordPress team announced a security upgrade to 2.6.5 that fixes an exploit only affects IP-based virtual servers running on Apache 2.x.  Fortuanately, for Blogs About clients, this only affects our clients on only one of our servers.  If you are hosted on our Kiwi server (IP 76.74.159.114), and are running WordPress on your account, you will want to upgrade to WordPress 2.6.5.  Our Kiwi server is running Apache 2.2.9.  ( The IP of the server you are on is listed in your account CPanel, in the left menu – if is 76.74.159.114 – you’re on Kiwi)

The security issue is an XSS exploit discovered by Jeremias Reith that fortunately only affects IP-based virtual servers running on Apache 2.x. If you are interested only in the security fix, copy wp-includes/feed.php and wp-includes/version.php from the 2.6.5 release package.

2.6.5 contains three other small fixes in addition to the XSS fix. The first prevents accidentally saving post meta information to a revision. The second prevents XML-RPC from fetching incorrect post types. The third adds some user ID sanitization during bulk delete requests. For a list of changed files, consult the full changeset between 2.6.3 and 2.6.5.

Get the WordPress 2.6.5 files from the official WordPress site.

This alert is for clients on our Jingles server – IP: 66.135.55.41

( The IP of the server you are on is listed in your account CPanel, in the left menu – if it matches the one listed above, your site is on Jingles)

We are upgrading the RAM on this machine today.  The server is functioning fine right now – although we did experience a minor 5 minute outage earlier this morning.  The RAM upgrade will occur overnight – during times of lower traffic and readership.  The integrity of all backup files will be maintained in our system, but you may experience some maintenance downtime in the very late hours of the night tonight, if you’re like me and are still awake at that hour!

Grab a book.  Catch up on the news.  Relax – have a good night of sleep, you probably won’t even notice.  Will provide updates here when it’s done and dusted!

UPDATE: 11:15 PM (CST/GMT -6) -> We’ve confirmed the time of the hardware maintenance on this server to be between 12:00AM (Midnight) – 4:00AM (CST/GMT -6).  That’s not to say the server will be down for the entire 4 hours – - but that is the window of time that the maintenance is scheduled for.  Will update here again with progress as it happens!  Hang tight – we’re getting there!

UPDATE #2: 10/21 – All is well and good in the land of Jingles!  Our Jingles got herself some brand new, shiney RAM – as well as a new chassis because we suspected the box had some I/O issues, as well.  Pretty much everything was replaced except for the hard drives and she is running smooth and we expect to hear ZERO whining out of her!  If you even noticed the downtime last night between 12:00AM (Midnight) and 4:00AM CST – we thank you very very much for your patience.  If you didn’t notice – all the better!  The intermittant problems we’ve had with Jingles are resolved and we expect smooth sailing out of her from here on out.  Yay!

Update 10/21 - We have worked with the fine folks at CPanel about a licensing issue for the CPanel software.  During/after the repairs to Jingles, our authorized license did not get transferred and access to CPanel was limited for a small amount of time.  The license has since been transferred over and we’ve not experienced any CPanel access issues since then.  If you have, or continue to experience problems accessing your CPanel – <a href=”http://tickets.blogs-about.com”>please file a ticket in our Help Desk</a> and let us know so we can get it resolved for you.  Thanks!