By Matt Simpson on

Not an upgrade. Is a new installation in a different directory within /html.

I have checked and rechecked the settings.php 20 times over and am using the same line & syntax known to work on a 4.5.2 installation of Drupal (was in conf.php) on this VPS provider.

$db_url = 'mysql://myusername:myusernamepassword@localhost/mydatabasename';

My host provider (websitesource) offers MySQL server 3.23. I access it using HSPcomplete control panel + phpMyAdmin 2.5.2.

Within phpMyAdmin, I set ALL privs on myusername available within the UI. However, I notice this difference...

INSTALL.mysql.txt says to make sure that the database username is set with

GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX,ALTER, CREATE TEMPORARY TABLES, LOCK TABLES

However, CREATE TEMPORARY TABLES, LOCK TABLES does not seem to be supported in MySQL server 3.23 (per online documentation & per the phpMyAdmin UI & per a failed syntax when I try to execute a SQL query to grant permission.)

According to INSTALL.mysql.txt...

Note: Unless your database user has all of the privileges listed
above, you will not be able to run Drupal.

I have requested that I get an upgrade of MySQL. The provider will do it for $75 per hour. However, I don't understand if this is necessary. I'm seeing elsewhere in the Forums that people are able to run Drupal 4.7 on MySQL server 3.23. How can people do this when "Unless (our) database user has all of the privileges listed above, (we are) not able to run Drupal?"

If it can be run on MySQL server 3.23, what can I possibly be missing?
- the username it right
- the database name is right
- the password is right

I loaded the tables using database.4.0.mysql
I did this - FLUSH PRIVILEGES;

What could I be missing?

⋅ Categories: Drupal 4.7.x

Comments

vm’s picture

vm commented

lowest mysql version drupal runs on per http://drupal.org/requirements is 3.23.17.

any reason why you are trying to maintain using such an outdated verison of MySQL ?

Matt Simpson’s picture

Matt Simpson commented

note - I verified that I have mysql Client API version 3.23.56

This is what they offer - http://www.websitesource.com/hosting/vps-applications.shtml (see MySQL server 3.23.) I've been shopping yesterday and today for a new provider. But I really like this service. I like the VPS. The storage, bandwidth, support, performance, reliability, and price is decent. If it turns out to be the mysql version and I can't find another provider I prefer (the hosting discussions on this forum are a great resource, by the way) then I may bite the bullet and pay for them to upgrade if I can't convince them to do it as a basic part of the service.

nb - I did ask them to make sure I have Mambo, phpNuke, and PostNuke as the offering promises. I'm sure paying for it.

Matt Simpson’s picture

Matt Simpson commented

It's amazing what posting here in the Forums does... So I posted... and then I realize that I'm working with 4.7.0 instead of 4.7.4 and that maybe this has some impact on my problem. How could I have gotten 4.7.0? Oh... http://drupal.org/drupal-4.7.4 references "For more information about the Drupal 4.7.x release series, consult the Drupal 4.7.0 release announcement" from which I pulled my download.

Let's see if getting the right version helps.

Matt Simpson’s picture

Matt Simpson commented

so... I tried again using the 4.7.4 code... it didn't work...

vm’s picture

vm commented

you host does not specifiy that they are using 3.23.17 only that they support 3.23 logging into phpmyadmin should provide for you, the full version of mysql being used. If you are running 3.23 and not 3.23.17 you will have to find a way to get to that minimum requirement.

Matt Simpson’s picture

Matt Simpson commented

I verified that I have mysql Client API version 3.23.56

cog.rusty’s picture

cog.rusty commented

What is the error message and how do you get it?

"Unable to connect to database server" does not sound like a compatibility issue.

Matt Simpson’s picture

Matt Simpson commented

Unable to connect to database server
This either means that the username and password information in your settings.php file is incorrect or we can't contact the MySQL database server. This could mean your hosting provider's database server is down.

The MySQL error was: .

Currently, the username is (databaseusername) and the database server is localhost.

Are you sure you have the correct username and password?
Are you sure that you have typed the correct hostname?
Are you sure that the database server is running?
For more help, see the Installation and upgrading handbook. If you are unsure what these terms mean you should probably contact your hosting provider.