As is normal for me now, I do all upgrades on a test install before I do them on my production sites. After the upgrade on my test site to Drupal 6.17, I'm continually being told the access permissions need to be rebuild. This, in itself, isn't surprising as all of the modules involving those permissions (ACL, Forum & Content Access, and OG Access) must be disabled during the update and then reactivated. What is surprising is that it hangs at the point it is telling me it is rebuilding the permissions.

I also apologize - in advance - for reporting this as a bug in EACH of these module sections. However, disabling and removing ALL of these modules does get rid of the error and problem. But, any attempt to activate any of them causes the issue return. Also, unsurprising, the content that was previously marked as private (thru one of these modules) remains public as the permissions cannot be rebuilt.

I found an extensive thread on this topic here, but those involve an older version of Drupal:
http://drupal.org/node/399572
But it appears as though that entire section of node.module has been revised since the solutions proposed in that thread was posted. Not going to do the update for my main sites until I have a better clue as to what is going on as I don't want to mess them up...

Comments

salvis’s picture

Status: Active » Closed (duplicate)

I think the thread you're interested in is #281326: The content access permissions need to be rebuilt., especially #51.

The essence is that you probably have one or more nodes that fail to load. This can be caused by database corruption or by some bug in one of the modules that are involved in loading your nodes.

Unfortunately, Drupal core is not very robust in this situation and the rebuilding process fails.

Why this would be worse under 6.17 is unclear. Have you tried rebuilding permissions under 6.16 and did it work? The fact that any node module will cause the same misbehavior is a very strong indicator that the problem is not with any of them.

IreneKraus’s picture

I do not see how there could be any problems with the content in the database, as I had deleted ALL of it on the site, rebuilt that and tried the rebuild permissions option again. (The database was repaired/optimized thru PHPAdmin too.) So I don't think the suggestion mention in http://drupal.org/node/281326, section 51 applies either as there WERE no nodes existing on some of these attempts.

Sorry for taking so long to respond but I am still recovering from cancer treatments. Can only work for a limited period of time per day. If you want admin access to the test install I'm talking about let me know so you can confirm what I'm seeing...

salvis’s picture