<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: MySQL error message in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/mysql-error-message/m-p/3380756#M70803</link>
    <description>This usually means that the mysqld hasn't been started.&lt;BR /&gt;&lt;BR /&gt;The other possiblity is that the 'mysql-bench' is looking for the local-socket file in a different place.  '/var/lib/mysql/mysql.sock' in this case, where as your mysql server is quite possibly putting it in a different place ('/tmp/mysql.sock' is not uncommon).&lt;BR /&gt;&lt;BR /&gt;You'll need to verify that your mysql daemon is started, and see where it's putting it's socket file.  If it's not '/var/lib/mysql/mysql.sock', then make a symbolic link to it at that location:&lt;BR /&gt;&lt;BR /&gt;ln -s /real/path/to/mysql.sock /var/lib/mysql/mysql.sock&lt;BR /&gt;&lt;BR /&gt;This should allow everything to work.</description>
    <pubDate>Thu, 16 Sep 2004 18:10:56 GMT</pubDate>
    <dc:creator>Stuart Browne</dc:creator>
    <dc:date>2004-09-16T18:10:56Z</dc:date>
    <item>
      <title>MySQL error message</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mysql-error-message/m-p/3380755#M70802</link>
      <description>I am setting up a MySQL server and I wanted to run some benchmark tests. When I tried to run the run-all-tests script under mysql-bench, I got the following error message:&lt;BR /&gt;&lt;BR /&gt;DBI connect failed: Can't connect to local MySQL server through socket '/var/llib/mysql/mysql.sock' (2)&lt;BR /&gt;&lt;BR /&gt;What do I need to change to correct this? Thanks.</description>
      <pubDate>Thu, 16 Sep 2004 16:01:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mysql-error-message/m-p/3380755#M70802</guid>
      <dc:creator>Andrew Kaplan</dc:creator>
      <dc:date>2004-09-16T16:01:32Z</dc:date>
    </item>
    <item>
      <title>Re: MySQL error message</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mysql-error-message/m-p/3380756#M70803</link>
      <description>This usually means that the mysqld hasn't been started.&lt;BR /&gt;&lt;BR /&gt;The other possiblity is that the 'mysql-bench' is looking for the local-socket file in a different place.  '/var/lib/mysql/mysql.sock' in this case, where as your mysql server is quite possibly putting it in a different place ('/tmp/mysql.sock' is not uncommon).&lt;BR /&gt;&lt;BR /&gt;You'll need to verify that your mysql daemon is started, and see where it's putting it's socket file.  If it's not '/var/lib/mysql/mysql.sock', then make a symbolic link to it at that location:&lt;BR /&gt;&lt;BR /&gt;ln -s /real/path/to/mysql.sock /var/lib/mysql/mysql.sock&lt;BR /&gt;&lt;BR /&gt;This should allow everything to work.</description>
      <pubDate>Thu, 16 Sep 2004 18:10:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mysql-error-message/m-p/3380756#M70803</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2004-09-16T18:10:56Z</dc:date>
    </item>
    <item>
      <title>Re: MySQL error message</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mysql-error-message/m-p/3380757#M70804</link>
      <description>if mysqld is running,&lt;BR /&gt;see if you have a /var/lib/mysql/mysql.sock and if so, whether it has access rights to mysql:daemon&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 17 Sep 2004 08:17:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mysql-error-message/m-p/3380757#M70804</guid>
      <dc:creator>Suresh Pai</dc:creator>
      <dc:date>2004-09-17T08:17:46Z</dc:date>
    </item>
  </channel>
</rss>

