Hello,

I installed the domain module, and got an error at the end of the recreate permission process.
There's no report of any kind in drupal logs.
I'm not sure this is domain related but I noticed that I had this error when opening the domain_access table in phpmyadmin :
column 'nid' should not be part of both a primary key and an index key.
(ps : this is not the actual message but a traduction from french)

Do you think I should worry about this error ?
Could it be related to my permission issue

Thanks

CommentFileSizeAuthor
#2 drupal_error.jpg5.86 KBjferrervalls
#2 mysql_error.jpg115.6 KBjferrervalls
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

agentrickard’s picture

It could be. Does the MySQL log show anything? Did you get any on-screen error message?

That's an odd MySQL warning. What version are you running?

jferrervalls’s picture

FileSize
115.6 KB
5.86 KB

I'm running MySQL: 5.0.51a.
See the attach files for the error displaying at the end of the rebuild process.
As I said there's no significative report in the drupal log.
Also drupal doesn't display any error for Node Access Permissions in the status report, but most of my content can not be access for anonymous users.

The second attach file is my phpadmin page for domain_access (sorry for french) with the error mentionned above.

Is it normal to have nid as an INDEX ??

Thanks

jferrervalls’s picture

Also
when I try to rebuild permission with a drush command, I've got the following error :

xxx:~# drush eval 'node_access_rebuild();'
tput: unknown terminal "xterm-256color"
Drush command terminated abnormally due to an unrecoverable error. [error]
Error: Call to undefined function node_access_rebuild() in /usr/share/drush/commands/core/core.drush.inc(637) : eval()'d

Disabling the domain module solved the error, so this issue is indeed related to the domain_access table

agentrickard’s picture

Don't use drush eval. Use drush cache clear. When using drush with domain you must also pass an -l or -URL value in most cases.

I don't get the same MySQL warning which I suspect is a strict warning. Why don't you just remove the index and try again.

We can remove that index if the nid column is indexed independently by MySQL.