Todays most confusing error message award goes to MySQL, for this error(?) message of mysqld_safe when trying to start the mysqld daemon:

db1:/usr/local/mysql# bin/mysqld_safe --user=mysql
Starting mysqld daemon with databases from /usr/local/mysql/data
STOPPING server from pid file /usr/local/mysql/data/db1.pid
070713 14:16:50  mysqld ended

Finding the problem was easy...

db1:/usr/local/mysql# ldd bin/mysqld
        librt.so.1 => /lib/librt.so.1 (0x00002b43be382000)
        libdl.so.2 => /lib/libdl.so.2 (0x00002b43be48b000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x00002b43be58f000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x00002b43be6a4000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x00002b43be7d8000)
        libm.so.6 => /lib/libm.so.6 (0x00002b43be8f0000)
        libstdc++.so.5 => not found
        libc.so.6 => /lib/libc.so.6 (0x00002b43bea72000) …

Like an invincible psycho with a knife, Log Buffer is back, with a Friday the 13th issue (”Larry’s Revenge!”). Daniel Fink of OptimalDBA is the lucky one to do this 53rd edition of the weekly review of database blogs. Please read Log Buffer’s homepage and drop me a line if you’d like to [...]

Todays most confusing error message award goes to MySQL, for this error(?) message of mysqld_safe when trying to start the mysqld daemon:db1:/usr/local/mysql# bin/mysqld_safe --user=mysql
Starting mysqld daemon with databases from /usr/local/mysql/data
STOPPING server from pid file /usr/local/mysql/data/db1.pid
070713 14:16:50  mysqld ended
Continue reading "Confusing error message"

To deal with Drupal's growth, we're adding a second database server to drupal.org which is useful for at least two reasons. First, we'll be able to handle more SQL queries as we can distribute them between multiple database servers (load balancing). Secondly, this new server can act as a "hot spare" that can immediately take over if the other database server fails (high availability / fail-over).

The current plan is to configure both database servers in master-slave configuration, which is the most common replication model for websites. This model provides scalability, but not necessarily fail-over. With a master-slave configuration, all data modification queries (like INSERT, UPDATE and DELETE queries) are sent to the master. The master writes …

To deal with Drupal's growth, we're adding a second database server to drupal.org which is useful for at least two reasons. First, we'll be able to handle more SQL queries as we can distribute them between multiple database servers (load balancing). Secondly, this new server can act as a "hot spare" that can immediately take over if the other database server fails (high availability / fail-over).

The current plan is to configure both database servers in master-slave configuration, which is the most common replication model for websites. This model provides scalability, but not necessarily fail-over. With a master-slave configuration, all data modification queries (like INSERT, UPDATE and DELETE queries) are sent to the master. The master writes …

The Certified MySQL Associate certification that we’ve mentioned a few times by now will be available in all Pearson VUE testing centers as of Wednesday, July 18 2007.

Yay!

It’s not an exam that will impress hard-core DBAs with years of experience, but I actually expect quite a lot of this certification. The Developer and DBA certifications are pretty tough, and in many cases go beyond what you need, at least for an entry-level position. With the Associate certification, you get good proof that you know the basics of MySQL without straining yourself or your wallet.

The exam has 50 questions, and lasts for one hour. It’s also somewhat less expensive than the other exams. Unlike other MySQL certifications, the Associate exam does not carry a version number and is regarded as perpetually valid once you have obtained it (we do, however, …

Many times you need to produce XML output from your MySql database. MySql has no built-in support for creating XML in it's SQL implementation but you can easily add support using the stored function feature.

To make xml output easier I have made three small stored SQL functions. They produce xml fragments, which you can easily put together to get a complete xml:

xml_escape(value) replace characters not allowed in xml with the escape sequences
xml_attr(name, value) create an xml attribute
xml_tag(tagname, tagvalue, attrs, subtags) create a tag, optionally with


Lets see some examples. First a real simple one:

select xml_tag('table',table_name,null,null)
from information_schema.tables
where table_schema = 'INFORMATION_SCHEMA'

Gives you something like:

<table>CHARACTER_SETS</table>
…

MySQL, like most software companies, has a complex organization to deal with the creation and improvement of its products.
There is a well oiled machinery that evaluates the needs and decides where to invest resources to create new products or to expand or change existing ones.
Ultimately, what affects the decision is the users satisfaction.
However, funnily as it may sound, the best organized activity in our company is bugs processing i.e. the one dealing with users dissatisfaction.
I would like to see more positive input from the users, and thus I put together the guidelines for a Usability Report.
What is is?
In short, it is the account of a user first impression with a product or a feature. If you decide today to start testing, say, …

Today I’ve started moving (actually copying) all information I have about MMM to the project’s wiki.

If someone is interested in adding some information there or modifying my descriptions (yes, I know about by awful English and I hope someone will fix my mistakes), ping me (contacts are here) and I’ll add you to the project members list.

Thanks all for participation and support.

A little while ago now, I did some tech reviewing of a book called Backup & Recovery… specifically MySQL related things (and MySQL Cluster). Curtis was kind enough to send me a copy of the book as well - and I’ve been reading the rest of it bits at a time since I got it.

I’m rather impressed… it gives a good mix of overview and digging deeper on just about every way to back up and recover systems. It also discusses several products that I didn’t know about (and have partly investigated now because of it).

It also has good sections on process: as in how to decide what to backup, encouraging the use of checklists and all that. Heck… recently when doing a restore I realised I never backed up /boot (annoying, not catastrophic… as I know my way …