title: Typo3 won't connect to mysql
body: <p>Just installed Typo3 Version 6, Government package on Linux Mint 14. Installed latest version of PHP &amp; MYSQL. Compiled PHP with:</p>
  
  <pre><code>./configure --with-apxs2=/usr/local/apache2/bin/apxs --with-mysql  --with-openssl --with-zlib --enable-soap --enable-hash --with-pcre-regex --with-curl --with-gd --with-mysqlih-mysql  --with-openssl --with-zlib --enable-soap
  
  make
  
  make install
  </code></pre>
  
  <p>Typo3 installer gives the following error: </p>
  
  <blockquote>
    <p><em>There is no connection to the database!<br>
    (Username: typo3, Host: localhost, Using Password: YES)<br>
    Go to Step 1 and enter a valid username and password!</em></p>
  </blockquote>
  
  <p>The username and password that I entered are correct. I am able to connect to mysql using these credentials with</p>
  
  <ol>
  <li>phpMyAdmin web interface</li>
  <li>mysql -u typo3 -p typo3db</li>
  </ol>
  
  <p>Did Google search and found some people had this problem and the cause was one of the three things:</p>
  
  <ol>
  <li>underscore in DB name - as up can see by my db name, it doesn't apply to my case</li>
  <li>config not allowing persistent connections to mysql - doesn't apply to my case,since I am currently allowing persistent connections.</li>
  <li>permissions of typo3 files - suggested fix was set all files to 755 or 777 (way to permissive in my opinion), but I tried this to rule out permission issue. Didn't resolve the issue in my case.</li>
  </ol>
  
  <p>I enabled general logging for mysql. When I enter username and password for mysql user in the typo3 installer, it immediately gives the error that it can't connect, but mysql logs show no login attempt. Conversely, when I login with phpMyAdmin it does show the success and when I type in a wrong password on purpose, the log shows it is being denied.</p>
  
  <p>This all implies to me that no connection from Typo3 to mysql is being initiated, but I don't now why. </p>
  
  <p>Any thoughts on what the issue could be or what I should check next?</p>