Problem setting Up EE v1.5

[wcbert]

I have installed EE v1.5 on my server and successfully ran
install.php. The mySQL database has the tables created by
the install.php

My problem is in the EE FTP SERVERS setup, I get this message
in the FTP messages window:

"get_message_lock: Access denied for user: '####@localhost' to database '####'"

I check both connect.php and preferences.php have the
correct mySQL setting.

Any ideas what I am doing wrong.

Thanks
Bill

[dscottf]

I had the same problems and am slowly tracking them down. I had a bad upgrade of mysql 4 (showed up as this and several other errors)

phpmyadmin also reported that I needed to run the update tables permission fix, but it would not run. mysql had a serious problem.

I just had to rebuild the whole server (caused by problems that may or may not be related). Most of mysql has come back, but it looks like I am not out of the woods yet. Next step will be a fresh install of mysql 4.0.16 (IIRC). you may have the same issue

I am running an OS X 10.3 server, and there are known mysql record locking issues with the OEM install

If you don't admin the server yourself, contact the admin with this problem. Pekka reports this as symptomatic of an upgrade from mysql 3 to 4. Theoretically fixable with the update tables permissions script that comes with mysql 4.

Hope this helps.

[Pekka]

I have installed EE v1.5 on my server and successfully ran
install.php. The mySQL database has the tables created by
the install.php

My problem is in the EE FTP SERVERS setup, I get this message
in the FTP messages window:

"get_message_lock: Access denied for user: '####@localhost' to database '####'"

I check both connect.php and preferences.php have the
correct mySQL setting.

Any ideas what I am doing wrong.

Thanks
Bill

EE tries to do table lock and you MySQL user name is not allowed to do it.

This situation is very common after server admins updated from MySQL 3 to 4. In MySQL 3 lock privileges were assigned by default and part of the normal privileges system, in MySQL 4 a much more complex "grant" system is in place and lock settings were moved there. Often lock privileges were "lost" in updating MySQL, as seems to be in your case. So all you need to do is give yourself lock privileges back.

Easiest way to see and grant (if you run your own server, otherwise ask admin to set the grants up for you) ) these privileges are by using latest PhpMyAdmin.

http://photography-on-the.net/ee/beta/grants.jpg

You can also remove locks from code. In all scripts but EE backup they are not required. I will remove the locks below from next release version.

In fetchsettings.php remove:


$nextmessage_lock = mysql_query(
"LOCK TABLES
ee_message WRITE
");


and


$nextmessage_unlock = mysql_query(
"UNLOCK TABLES
");


In exhibition_group_editor.php remove

$lock_groups = mysql_query(
"
LOCK TABLES
ee_exhibition_to_group WRITE
"
);

and

$unlock_grooups = mysql_query(
"
UNLOCK TABLES
"
);


In export_ftp_message.php remove

$get_message_lock = mysql_query(
"LOCK TABLES
ee_message READ
");

and

$get_message_unlock = mysql_query(
"UNLOCK TABLES
");

In ftp_message.php remove

$get_message_lock = mysql_query(
"LOCK TABLES
ee_message READ
");

and

$get_message_unlock = mysql_query(
"UNLOCK TABLES
");

There are several locks in EE Backup - if you cannot get lock grants you'll need to just tolerate the error messages. In EE Backup loosing locks may mean data loss when backing up a database which is under use, so I'd suggest stopping EE and waiting a few moments before doing a backup in this scenario.