It's annoying critical bug maybe as I am now, sorry, but after a months of working drupal site, the chance to get Access Denied to whole site is certain. Put "Access Denied" in the search box here and you will see what i mean or click here.

Your site will go Access Denied after awhile. Using of whatever modules are making this error, your wonderful hosting company makes this error, your correct settings makes this error, the God himself makes this error. Actually it doesn't matter who makes this error because you will end with a bunch of nodes, content, call it whatever you want, in your database completely out of order sooner or later.

Cannot give you details "how", "when", "who", or "why", because i don't know any of it. Be nid number one, or anon dude #2... The bug is simply there, Access Denied and more that 2 months writing "books" and "nodes" and texts are now denied to all. I mark it "critical" but that's not the word for it. Maybe "disasterous".

Guys, please, can someone put a bit effort to fix this once and for all?

Comments

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Category: bug » support
Priority: Critical » Normal

Re-filing as a support request unless some means of reproducing the bug (or even verifying its existence) are found. It sounds like you're getting some kind of data corruption, or some buggy module has reset the status field in your node table.

heine’s picture

heine commented
Category: support » bug
Priority: Normal » Critical

Is this a Drupal Access denied message or does it originate from the database?

Please provide additional information. That includes the basic version information, but also a list of modules you use. In addition, we need info on the roles and accounts which receive an access denied.

Please check whether there are entries in the users table for uid 0 and uid 1.

heine’s picture

heine commented
Category: bug » support
Priority: Critical » Normal

race condition

Kodeart’s picture

Kodeart commented

Hi guys and thanks for your quick respond. I really appreciate this.

I didn't put any details on purpose, looks to me like digging into a sea of possible causes (and they are many). Here's what I can provide as details. If you can see or know anything suspicious in the following info, please post it. I cannot figure it out what's going on.

My build:
Drupal 4.7.4
MySQL 4.0.24-standard-log (no table locking permissions)
PHP 4.3.11
Apache 3.23
Shared hosting: IX Webhosting (higly not recommended)

Modules (3rd party):
- advanced_menu
- bookmarks
- emailpage
- globalredirect (redirections ok)
- moviereview
- node_style (working as expected)
- nodeaccess (working as expected)
- panels (created only 1 panel for "sitemap")
- print
- urllist

Modules (Drupal default):
- No taxonomy at all, taxonomy.module not enabled
- aggregator
- archive
- book
- help
- locale
- menu
- page
- path
- ping
- poll
- profile
- story
- syndication
- watchdog

Other settings/notes:
Fameous zero-user exist (users table: '0', '', '') ,status=0
Admin is uid=1 and enabled (status=1)
Node Access value exist (node_access table: 0, 0, 'all', 1, 0, 0);
Roles: 2 additional
Access Control: viewing enabled for all roles
Access Rules: none
Cron is running every 1h
Cache disabled
Clean urls enabled
File system to "Private"; the folder perm. 777
String handling: using mbstring extension
.htaccess as in default, no additional RewriteRules
Additional theme: friendselectric (using blumerine)

First time denials were for anonymous users only (admin can see everything). I fix the pages with recreating them from the scratch (what a fix!), around 20 nodes.
This (second) time they are lot more than 20 and no one can see a thing. Neither admin nor anonymous, registered etc. Time between 2 issues >2 months.

Assumptions...
my host had a big problems with their mysql servers. They were up/down/up/down every 5 minutes and couldn't put it together more than 4 months. Could be corrupted data or the absence of table locking permissions.

Could be also trying too many modules. But the nodes were okay while testing, accessible at any point. This happened after i don't know what... just like that, *snap*, simply they couldn't be accessed, not even in admin section for editing. Oh, the main site menu (not admin navigation) I can see the primary links but not secondary.

--
I must note here, this is not about my problem. It could happen to anyone after awhile "for no reason". Looks like Drupal have a major bad flaw, muff at the core, how he handles the modules or something, I don't know. So that's why I send a desperate call "Please guys find the bad critical bugs". And yeah, sorry, but I wont quit Drupal. I like this comminity and Drupal so much :)

Again, thanks for your responds.
-- mixa

heine’s picture

heine commented

Thanks!

If you have a duplicate test site, please (on the test site) do the following:
- disable nodeaccess
- execute the queries:

DELETE FROM node_access;
INSERT INTO node_access (nid, gid, realm, grant_view, grant_update, grant_delete) VALUES (0, 0, 'all', 1, 0, 0);

- browse around.

If you do not have a test site, create a backup, try the above. Then you can always restore the backup. You may want to block access to your site though since the above instructions would restore the default node_access table, making all content visible for users with the access content permission.

I must note here, this is not about my problem. It could happen to anyone after awhile "for no reason". Looks like Drupal have a major bad flaw, muff at the core, how he handles the modules or something, I don't know. So that's why I send a desperate call "Please guys find the bad critical bugs". And yeah, sorry, but I wont quit Drupal. I like this comminity and Drupal so much :)

does not follow from

my host had a big problems with their mysql servers. They were up/down/up/down every 5 minutes and couldn't put it together more than 4 months. Could be corrupted data or the absence of table locking permissions.

heine’s picture

heine commented
Status: Active » Closed (won't fix)

Your system does not meet the minimum system requirements as detailled on the page System requirements and the install documentation contained in the Drupal archive. Therefore, this issue is a "won't fix".

sami-an’s picture

sami-an commented
Issue summary: View changes

This problem is caused by: browser settings. Solution: Allow cookies