When saving cron settings at admin/build/cron/settings, I get the following entry repeated dozens of times in my dblog:
Access denied for user 'drupal'@'localhost' to database 'drupal_live' query: LOCK TABLES variable WRITE in /var/www/live/drupal/includes/database.mysql.inc on line 328.
Every time cron runs I get a similar error:
Access denied for user 'drupal'@'localhost' to database 'drupal_live' query: LOCK TABLES variable WRITE in /var/www/live/drupal/includes/database.mysql.inc on line 328
These don't seem to impact the actual performance of the module, but are filling up my logs... any ideas?
Comments
Comment #1
Dane Powell CreditAttribution: Dane Powell commentedNevermind... I didn't notice that the drupal user needed to have lock privileges...
Comment #2
venusrising CreditAttribution: venusrising commentedHello-
Can someone please clarify. We cannot find any documentation on the Installation and settings portion.
We are getting tons of the same DB logs as above and are not sure how to correct this.
We do not have any settings filled it where it says key etc.
We did change crontab to be every minute.
We also set some tabs to fire by module.
Thanks for any help.
Comment #3
Dane Powell CreditAttribution: Dane Powell commentedDoes your database user have LOCK privileges?
Comment #4
venusrising CreditAttribution: venusrising commentedYes we made sure our host just added lock table permissions.
We are getting
User admin
Location http://www.oursite.com/admin/build/cron/execute/statistics_cron
Referrer http://www.oursite.com/admin/reports/event/1096025
Message Access denied for user 'oursite'@'localhost' to database 'drupal_oursite' query: LOCK TABLES variable WRITE in /home/oursite/html/includes/database.mysqli.inc on line 336.
Severity error
Oursite is used for our db name
Comment #5
venusrising CreditAttribution: venusrising commentedAfter the permission were given we still see the log errors
Comment #6
venusrising CreditAttribution: venusrising commentedComment #7
venusrising CreditAttribution: venusrising commented@Dane Powell We enabled lock privileges but it is still showing DB log errors. Is there a way to make sure lock privileges are set right. We had the host do it and use phpmyadmin
Comment #8
Dane Powell CreditAttribution: Dane Powell commentedHey venusrising- just FYI, I'm not the maintainer of this module, so all I can really do is tell you what worked for me, which was to make sure that the Drupal user had LOCK TABLES permission. Judging by your error, your Drupal database (DB) user still does not have that perm. You'll want to go to your DB in PHPMyAdmin and click on the privileges tab to see if that's the case.
Comment #9
krishanchandra CreditAttribution: krishanchandra commentedI am also facing this problem :-
user warning: Access denied for user '' to database '' query: LOCK TABLES variable WRITE in includes/database.mysqli.inc on line 336.
Comment #10
gotheric CreditAttribution: gotheric commentedThis has nothing to do with elysia_cron, it is a generic Drupal problem caused by a bad database configuration.
Look at this:
http://www.zyxware.com/articles/3168/solved-drupal-errors-drupal-6-lock-...
(Just for example, use google to find other solutions)
Comment #11
ron_s CreditAttribution: ron_s commentedI'm curious to know why you would say this has "nothing to do with elysia_cron, and is a generic Drupal problem caused by a bad database configuration"?
The database server requirements for Drupal (http://drupal.org/requirements/database) state the following:
"LOCK TABLES" is not required by Drupal core 6.x. You should update the module documentation to note that LOCK TABLES is a requirement for Elysia Cron.
Comment #12
kala4ekDrupal 6 is not supported anymore.