I’m a bit proud of myself on this one… I setup a simple, but clean and configurable, MySQL Master/Slave Replication Monitoring PHP Script:
http://code.google.com/p/php-mysql-master-slave-replication-monitor/ (docs)
It’s Open Source and free, I welcome comments, suggestions, and questions.
I think this will be quite useful for anyone who is setting up a pair of MySQL servers as master/slave and want to be sure their replication works as it should.
I love this fanout script for running the same command on multiple servers, just in case you’re interested:
http://www.stearns.org/fanout/fanout
[root@199564-6 scripts]# fanout "$SERVERS" "cp /root/.ssh/authorized_keys /home/user/.ssh/"<br /> Starting root@db1<br /> Starting root@db2<br /> Starting root@nas<br /> Starting root@www1<br /> Starting root@www2<br /> Starting root@www3<br /> Fanout executing "cp /root/.ssh/authorized_keys /home/user/.ssh/"<br /> Start time Wed Dec 23 23:45:35 EST 2009 , End time Wed Dec 23 23:45:47 EST 2009<br /> ==== As root on db1 ====
Sometimes, I want something only if it’s on the cheap, second hand, and easy… that’s usually Craigslist.
Often what I want isn’t available when I think of it… but it might show up sometime… I don’t want to have to look at craigslist every day (because I wont).
Google Alerts to the rescue.
If I’m in Louisville KY and I’m looking for an iPod (for example) I just setup an alert for: “site:louisville.
So the website has been down from Oct 21st to Nov 23rd. The old server got hacked (or really, a sister-server) and due to security concerns, we didn’t know what got owned and what was safe. We already had a different server hardware to put in place, just had to set it up. So we got that installed and up and running, but it took me a few more days to get around to implementing something on my site.
So I’ve just fought a battle w/ SVN merge and thought I’d post the solution in case others might find it…
Scenario
Our stable code is in trunk svn://svn.domain.tld/repository/trunk
I’ve got a branch of trunk svn://svn.domain.tld/repository/branches/dev
Changes have been made to my branch and changes have been made to trunk, since I branched.
I’m ready to merge my branch back into trunk.
Approach / Overview
Basically, to be safe, I need to first update my branch with the changes from trunk and resolve any conflicts.