<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>dev.fuzzee.co.uk &#187; bug</title>
	<atom:link href="http://dev.fuzzee.co.uk/tag/bug/feed/" rel="self" type="application/rss+xml" />
	<link>http://dev.fuzzee.co.uk</link>
	<description>stuff that pops into my head ... technical stuff.</description>
	<lastBuildDate>Sun, 18 Apr 2010 13:39:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>MySQL Replication and disappearing relay logs</title>
		<link>http://dev.fuzzee.co.uk/2009/09/mysql-replication-and-disappearing-relay-logs/</link>
		<comments>http://dev.fuzzee.co.uk/2009/09/mysql-replication-and-disappearing-relay-logs/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 19:52:21 +0000</pubDate>
		<dc:creator>adrian</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[replication]]></category>

		<guid isPermaLink="false">http://dev.fuzzee.co.uk/?p=92</guid>
		<description><![CDATA[A recent reboot of a server highlighted an issue with MySQL 5.045 on CentOS 5.3. On this particular setup, MySQL seems to place relay logs in /var/run/mysqld/. Unfortunately, this will mean that when the machine is rebooted, the relay log will get deleted.
When MySQL attempts to start up again, it won&#8217;t be able to find [...]]]></description>
			<content:encoded><![CDATA[<p>A recent reboot of a server highlighted an issue with MySQL 5.045 on CentOS 5.3. On this particular setup, MySQL seems to place relay logs in <strong>/var/run/mysqld/</strong>. Unfortunately, this will mean that when the machine is rebooted, the relay log will get deleted.<span id="more-92"></span></p>
<p>When MySQL attempts to start up again, it won&#8217;t be able to find the relay log and <strong>replication will fail</strong>. The error messages in /var/log/mysqld.log might look something like:</p>
<pre>[ERROR] Failed to open the relay log '/var/run/mysqld/[relay log filename]'</pre>
<p>The pre-emptive fix is to tell MySQL to store the logs elsewhere (/var/lib/mysql/ perhaps) using the <code>relay-log</code> configuration option. If you&#8217;ve already suffered this problem, then the most straight forward fix is to start again; do a <strong>show master status</strong>, <strong>flush logs</strong> and then a <strong>mysqldump</strong> to get a fresh starting point on the master, and then copy the new dump over to the slave.</p>
<p>More information on  <a href="http://bugs.mysql.com/bug.php?id=28850">the mysql bug report</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://dev.fuzzee.co.uk/2009/09/mysql-replication-and-disappearing-relay-logs/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
