Comments for RimuHosting Blog

Comment on PCI compliance – a basic HOWTO by Ryan

Ryan — Sun, 29 Jan 2012 17:16:03 +0000

Does anyone know why some merchants charge a PCI insurance fee? What does this insurance cover and is it necessary?

Thank you

Comment on Storage Clustering Part 2: GlusterFS by newbie

newbie — Tue, 24 Jan 2012 08:14:05 +0000

Thanks for the post. But following the instruction described above. The client would throws error

0-socket.management: reading from socket failed. Error (Transport endpoint is not connected), peer (aaa.bbb.ccc.ddd:port)

How to fix this?

glusterfs version is 3.2.5

Comment on Easy application hosting using StandingCloud and RimuHosting by December 2011 Newsletter | RimuHosting Blog

December 2011 Newsletter | RimuHosting Blog — Mon, 23 Jan 2012 02:00:09 +0000

[...] Easy application hosting using StandingCloud and RimuHosting [...]

Comment on 10 August Dallas outage report by Peter Bryant

Peter Bryant — Sat, 14 Jan 2012 23:03:43 +0000

To get more information on redundant power options see http://blog.rimuhosting.com/2011/08/25/redundant-psu-and-power-feeds/

Failover is a good option. Failover can become non-trivial when database- and file- changes occur.

Comment on 10 August Dallas outage report by Lloyd

Lloyd — Sat, 14 Jan 2012 22:36:24 +0000

I know this post is long after the power outage event, but my comments will be pertinent. I have seen the Dallas Data Center redundant power supplies fail before (several years ago there was a worse event). Rimuhosting always does a great job of responding to any outage, but they can't prevent this from happening. In my opinion, if you really want 100% uptime, just get a second "backup" VPS or dedicated server in a data center far away (mine is in the UK Rimuhosting data center). It won't be used much for failover, but you can rsync your own backups to it. Set up DNS failover such that your UK backup server is your *primary* DNS server, and your Dallas server (primary http server) runs a slave DNS server (I use bind9). Then make the UK server monitor your Dallas server, and let it trigger DNS failover when/if Dallas fails. When the UK server detects failure of your Dallas server, it changes the DNS A record to itself. That way your website won't go offline more than a couple of minutes if Dallas fails. (Dallas could *disappear* from the map and this would work.) If you set it up right, your backup web server can even take orders from customers. At the very least, you will not lose your web presence. If someone needs help with this, contact me through .

Comment on WordPress mass update script 3.3 by Liz Quilty

Liz Quilty — Mon, 09 Jan 2012 21:43:50 +0000

Great to hear!

Comment on WordPress mass update script 3.3 by George

George — Thu, 15 Dec 2011 21:38:52 +0000

Fantastic! Thanks very much Liz - your script made upgrading a piece of cake.

Comment on Checking a potentially hacked machine and reinstalling packages when you break things by Ryan

Ryan — Wed, 14 Dec 2011 07:08:37 +0000

An alternative debsum check. dpkg -l | grep ^ii | awk '{ print $2 }' | xargs debsums -s -a

Comment on WordPress mass update script 3.3 by Steve

Steve — Wed, 14 Dec 2011 01:15:52 +0000

Small spelling error: "Standerd" should be "Standard".
Your script saves me hours. Thanks!

Comment on WordPress mass update script 3.3 by Geoff

Geoff — Tue, 13 Dec 2011 20:34:32 +0000

sweet, thanks