Image the following scenario:
cd /etc
chown root.root * -R
OOPS
You have just destroyed the server.
This, and other similar mishaps (i.e. chmod 777 / -R) occur more often than one would imagine.
If you are in luck like me, you have access to more than one linux server, and in most cases these servers are similar enough in order [...]

 ::  (Read the rest of this)

It has become quite commonplace today, for high traffic sites to require more than one web server.
Here is a small script in charge of synchronizing the server configuration files (/etc/httpd in this example).
In this case, I will be using apache as the web server of choice, simply because of its prevalence and popularity, however the [...]

 ::  (Read the rest of this)

As promised, here is short example of the Daemon in operation.

 ::  (Read the rest of this)

The problem that this program was designed to solve is a rapidly changing MySQL table in use by a high-traffic website.
For instance, stock quotes on the front page of a bank’s or investments firm’s site.
The data is constantly updated by a service on the backend, and is referred to by some ajax widget or by [...]

 ::  (Read the rest of this)

Don’t ask me why scripting in batch is still necessary on the verge of the year 2010, however, what can you do when some clients still use Windows to host their MySQL servers…
REM Simple MySQL backup script per database
@echo off

REM Set some variables
set mysqlcmd="C:\Program Files\MySQL\MySQL Server 5.0\bin\mysql.exe"
set mysqlpwd=amazingsecretsamplepassword
set mysqlconnect=%mysqlcmd% -u root –password=%mysqlpwd%
set mysqldumper="C:\Program Files\MySQL\MySQL Server [...]

 ::  (Read the rest of this)

Setting up a MySQL fail over Master-Master replication system is something one can find many guides for.
However, monitoring and recovering from a failure of the system is not as well documented, according to a quick Google search.
The top items from that search were:

Something called: MYSQL master-master replication monitor shell script that mainly included the following [...]

 ::  (Read the rest of this)

When managing a large number of servers, it is most likely that you will come across a server that makes use of a RAID controller, and as such you will need to know the status of the disks and the disk array.
As these are usually proprietary controllers, normal tools like ipmiutil, lshw, lspci, etc. aren’t [...]

1 comment  ::  (Read the rest of this)

Not getting into the whole which engine is the best debacle, since obviously, like most important questions in life the answer is: “It depends.”

In addition, most of what is written here can be used to convert from any engine to any engine, and thus answering any specific needs your might have.
I needed to convert MyISAM to InnoDB so here it is.

Without further ado…

As far as I know, there are two basic ways to accomplish this:

1.  ALTER TABLE 'tablename' ENGINE = InnoDB

   For each table in the database.

2. Dump the table, edit the dump file where it says “CREATE TABLE” and fix to the preferred engine, and then reload the data back into the DB

Obviously, these methods are ok when you are dealing with a few tables, however a while ago we had a client with a huge database with over 50 tables, so of course, a script was in place.

2 comments  ::  (Read the rest of this)