<?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>Irma L. Olguin Jr. &#187; Geek Archives  &#8211; irms&#8217; blog, geekwise</title>
	<atom:link href="http://blog.irmsgeekwork.com/category/geek/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.irmsgeekwork.com</link>
	<description>Professional Geek.  Decent Human Being.</description>
	<lastBuildDate>Tue, 17 Jan 2012 06:56:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Can&#8217;t connect to local MySQL server through socket</title>
		<link>http://blog.irmsgeekwork.com/connect-local-mysql-server-socket</link>
		<comments>http://blog.irmsgeekwork.com/connect-local-mysql-server-socket#comments</comments>
		<pubDate>Fri, 26 Aug 2011 11:11:55 +0000</pubDate>
		<dc:creator>irms</dc:creator>
				<category><![CDATA[Geek]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[ubuntu]]></category>

		<guid isPermaLink="false">http://blog.irmsgeekwork.com/?p=876</guid>
		<description><![CDATA[CAUTION: Very nerdy stuff below. Non-nerds need not continue. Short answer: Check your disk space. Problem If you&#8217;ve ever had this error: Warning: mysql_connect(): Can&#8217;t connect to local MySQL server through socket &#8216;/var/run/mysqld/mysqld.sock&#8217; or it&#8217;s command line cousin: ERROR 2002 (HY000): Can&#8217;t connect to local MySQL server through socket &#8216;/var/run/mysqld/mysqld.sock&#8217; You&#8217;ll know that googling the problem turns up a number of suggestions to recreate the symlink or to reinstall MySQL. Solution For me, the problem was disk space. One of my log files was HUGE and MySQL wouldn&#8217;t start because of it. So I just had to locate the offending file, get rid of it, and MySQL fired right up.  If you&#8217;re running Ubuntu you can do a little du -s -m * to see a listing of files in any directory that&#8217;ll have the file size (in MBs) right next &#8230; <a href="http://blog.irmsgeekwork.com/connect-local-mysql-server-socket" rel="nofollow">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>CAUTION: Very nerdy stuff below. Non-nerds need not continue.</p>
<p><a href="http://blog.irmsgeekwork.com/wp-content/uploads/console1.png" rel="lightbox[876]"><img class="aligncenter size-medium wp-image-883" title="console" src="http://blog.irmsgeekwork.com/wp-content/uploads/console1-300x281.png" alt="Cant connect to local MySQL server through socket geek" width="300" height="281" /></a></p>
<h2 style="text-align: center;">Short answer: Check your disk space.</h2>
<h3 style="text-align: center;"></h3>
<h3>Problem</h3>
<p>If you&#8217;ve ever had this error:</p>
<p><span style="font-family: 'courier new';">Warning: mysql_connect(): Can&#8217;t connect to local MySQL server through socket &#8216;/var/run/mysqld/mysqld.sock&#8217;</span></p>
<p>or it&#8217;s command line cousin:</p>
<p><span style="font-family: 'courier new';">ERROR 2002 (HY000): Can&#8217;t connect to local MySQL server through socket &#8216;/var/run/mysqld/mysqld.sock&#8217;</span></p>
<p>You&#8217;ll know that <a href="http://www.google.com/search?q=Can't+connect+to+local+MySQL+server+through+socket" rel="nofollow" title="Google Search: Can't connect to local MySQL server through socket"  target="_blank">googling the problem</a> turns up a number of suggestions to recreate the symlink or to reinstall MySQL.</p>
<h3>Solution</h3>
<p>For me, the problem was <strong>disk space</strong>. One of my log files was HUGE and MySQL wouldn&#8217;t start because of it. So I just had to locate the offending file, get rid of it, and MySQL fired right up.  If you&#8217;re running Ubuntu you can do a little <span style="font-family: 'courier new';">du -s -m *</span> to see a listing of files in any directory that&#8217;ll have the file size (in MBs) right next to the name. Starting at the root, you can pretty quickly see which directories are too  large for their own good, and drill down to the problem file. (Mine was a 8.1 GB file [8149 MB], and <a href="https://manage.slicehost.com/customers/new?referrer=9582a32331ca1c0007fa8e822dfb915f" rel="nofollow" title="Slicehost 256MB Slice"  target="_blank">the slice</a> I was working on had 10GB total space.)</p>
<p>Who knows, maybe this&#8217;ll help someone one day.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.irmsgeekwork.com/connect-local-mysql-server-socket/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

