Checking database:Could not connect to the mysql server. What now?

Quote from: ross259 at Mar 17, 2010, 12:30 AM

Revolution would not install on my hosting but Evolution installed on my server with no problems.

If you’re using PHP 5.3, try my suggestion of using "127.0.0.1" instead of "localhost" for the DB hostname.

Sigh....

I let this rest for a while and now I really want to get this to work.

I placed the line that was supposed to do the trick into the php.ini file.

; Local Variables:
; tab-width: 4
; End:
extension=pdo.so
extension=pdo_sqlite.so
extension=sqlite.so
extension=pdo_mysql.so
pdo_mysql.default_socket=/tmp/mysql.sock

Cleared the cookies and cache.

But it is not working....

-----


http://www.bluewinddesign.com/modx/setup/index.php?action=database

I can put any value in the database info and test it:

→ Test database server connection and view collations.

Connecting to mysql server: Success!

---------

Even after clearing cookies and cache nothing changes. I get success whatever database info I put into it.




----

I even e-mailed support at bluehost, and received this reply: "I have ensured that the pdo_mysql extension is enabled for your account.

Here is the Phpinfo page that confirms the pdo_mysql is enabled:
http://www.bluewinddesign.com/phpinfo.php"

---

I am still getting the Could not connect to mySQL Server. I feel lost in the forest and confused dazed and dishearted. I need a elf to guide my way to a nice colorful sunny path I can walk. Please help me to a watering hole where I can get refreshed. Thanks..:)

Then your problem likely isn’t the sock file; perhaps you are doing something else wrong. Database user perhaps doesn’t have proper privileges. Regardless, RC1 will be available very soon and you can try that. If you still have problems, then it’s definitely still something in your environment that needs to be identified.

Good to hear that RC1 will be available soon!

I’ll wait for that then.

Have a great day!

It’s out now (for a couple of hours).

I see you’re still not reporting the actual PDOException message if and when it occurs.

For example, rather than
[tt]Connecting to mysql server: Could not connect to the database server. Check the connection properties and try again.[/tt]

Don’t you think something like this would be much more informative?

[tt]Connecting to mysql server: Could not connect to the database server. Check the connection properties and try again.
Details: SQLSTATE[HY000] [2002] Can’t connect to local MySQL server through socket ’/tmp/mysql.sock’[/tt]

Even if the "details" were initially hidden and made available by clicking a "more details" link or similar.

Quote from: Phil at Mar 23, 2010, 05:18 PM

I see you’re still not reporting the actual PDOException message if and when it occurs.

For example, rather than
[tt]Connecting to mysql server: Could not connect to the database server. Check the connection properties and try again.[/tt]

Don’t you think something like this would be much more informative?

[tt]Connecting to mysql server: Could not connect to the database server. Check the connection properties and try again.
Details: SQLSTATE[HY000] [2002] Can’t connect to local MySQL server through socket ’/tmp/mysql.sock’[/tt]

Even if the "details" were initially hidden and made available by clicking a "more details" link or similar.

Agreed 100% Phil; this will be addressed before GA. Because of the way xPDO initially supported PHP 4 and 5, exception handling was avoided until a couple of months ago, and now this needs some attention since xPDO 2.0/MODx 2.0 are now only supporting 5.1.1+ with working PDO/PDO_mysql configurations. A few simple adjustments in xPDO should take care of it.

Thanks for the suggestion.

Man good timing with the release of RC1...:) Atleast for me...:)

Great! I got the database check working!

What should the connection character set be?
and the Collation?

What are the default values (that work the best with English and other languages, I might use some Norwegian in it) that I should keep in the back of my mind?

I made some changes and then it did not work.

Puh....
I got it working with these values
swe7
swe7_bin

and I noticed that
utf_8
utf_8_unicode_ci
also works.

---

I got an ok on all the checks and am installing now. This feels good! Thanks...:)

We recommend utf8 and utf8_unicode_ci