Database connection problems on beta-3 install

69 Posts

markhurd Reply #1, 14 years, 8 months ago

Using MAMP Pro on OS X 10.5.7, MySQL 5.0.41, and PHP5.

Starting a brand new installation, when I click the ’Test Connection’ button I receive the following error:

Could not connect to the database.

Array
(
    [database_type] => mysql
    [database_server] => localhost
    [database_user] => (redacted)
    [database_password] => (redacted)
    [database_collation] => utf8_unicode_ci
    [dbase] => modx
    [table_prefix] => modx_
    [https_port] => 443
    [cache_disabled] => false
    [site_sessionname] => SN4a8dc149b118b
    [inplace] => 1
    [unpacked] => 1
    [database_charset] => utf8
    [database_connection_charset] => utf8
)

I am 100% sure my credentials are correct, as I just tried re-installing Evo 1.0.0 with the same username/password and it connected just fine.

Here is the mysql log after restarting:

090820 16:37:09  mysqld started
090820 16:37:09 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/living-e/MAMP PRO/db/mysql/ is case insensitive
090820 16:37:09  InnoDB: Started; log sequence number 0 668193
090820 16:37:09 [Note] /Applications/MAMP/Library/libexec/mysqld: ready for connections.
Version: '5.0.41'  socket: '/Applications/MAMP/tmp/mysql/mysql.sock'  port: 3306  Source distribution

24,544 Posts

BobRay Reply #2, 14 years, 8 months ago

Did you try creating an empty database for MODx to use before running setup?

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

69 Posts

markhurd Reply #3, 14 years, 8 months ago

Quote from: BobRay at Aug 20, 2009, 10:01 PM

Did you try creating an empty database for MODx to use before running setup?

I read the "If you there is no database yet, the installer will attempt to create a database for you. This may fail depending on the MySQL configuration or the database user permissions for your domain/installation." and my selective attention filtered out the second sentence. wink

Evolution (1.0.0 and 0.9.3) has successfully created the database for me each time on installation so I (incorrectly!) assumed Revo would do the same as the mysql configuration is identical.

Creating the empty database first fixed the problem, thanks Bob.

The only problem post-installation was that the setup directory was not deleted, although I specifically selected the checkbox asking the installer to do so. Look forward to playing around with it.

24,544 Posts

BobRay Reply #4, 14 years, 8 months ago

Glad you got it sorted. Revo seems to have more trouble with file and database permissions. I’m not sure why. On my Vista machine, the SVN version doesn’t delete the files and directories it says it’s deleting during the build, and I suspect it of not clearing the cache completely.

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

☆ A M B ☆
24,524 Posts

sottwell Reply #5, 14 years, 8 months ago

Oddly enough, the first time I installed yesterday it didn’t remove the setup directory, but the couple of times I went through a setup after that it did.

Studying MODX in the desert - http://sottwell.com
Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
Join the Slack Community - http://modx.org

51 Posts

paz Reply #6, 14 years, 8 months ago

I could be wrong, but I believe that there’s a JIRA bug report for this already.
So it’s a known problem.
I’m 100% sure that I did read about this error before.

MODX Staff
10,725 Posts

opengeek Reply #7, 14 years, 8 months ago

My database is created properly by the installer on fresh installs every time, so I’m not sure what specific known issue we are discussing here. And file permissions are generally the issue with files not getting deleted automatically. One known issue is the smarty cache is not being cleared, but otherwise, we need to explore these issues individually in detail to determine proper solutions.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

24,544 Posts

BobRay Reply #8, 14 years, 8 months ago

Quote from: OpenGeek at Aug 21, 2009, 03:40 PM

My database is created properly by the installer on fresh installs every time, so I’m not sure what specific known issue we are discussing here. And file permissions are generally the issue with files not getting deleted automatically. One known issue is the smarty cache is not being cleared, but otherwise, we need to explore these issues individually in detail to determine proper solutions.

I always create the DB myself, so I can’t speak to that one. For a long time transport.core.php would report having deleted core/packages/core and core/packages/core.transport.zip when it actually failed to delete them. Haven’t checked lately.

Clearing the cache with Site | Clear Cache works intermittently for me (FF/Vista/XAMPP). About half the time, I get an empty console window with an active OK button but the cache hasn’t been cleared. Sometimes I have to do it three times before I see the list of deleted files in the console.

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

69 Posts

markhurd Reply #9, 14 years, 8 months ago

Quote from: paz at Aug 21, 2009, 07:19 AM

I could be wrong, but I believe that there’s a JIRA bug report for this already.
So it’s a known problem.
I’m 100% sure that I did read about this error before.

I found MODX-849 in JIRA, although it’s geared more to handling the UX (a great idea!) rather than the error itself.