The "Permission Denied" also happens when there is high database load, as usually happens during the backup (between 0800 UTC and 0900 UTC), and the calling code does not yet check why the permission check code failed - due to a DB timeout or due to rules violations.

On the other side, just because some spam still gets through does not mean that the measures are ineffective. I see much potential in the recent change as it made it much easier to plug in additional checks like rate limiting.

(between 0800 UTC and 0900 UTC),

Ah. Okay, I'll watch for that in future.

does not yet check why the permission check code failed - due to a DB timeout or due to rules violations.

A "timed out" error would have saved me wondering what I was doing wrong and this thread.

does not mean that the measures are ineffective.

I did say "yet". My intent was to aid debugging rather than a complaint.

---

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Our database backup shouldn't be causing high load anymore and runs earlier than that, so I suspect there's something else happening in that time frame if you are seeing high load.

I have also met this error (permission denied error message when I'm trying to post a node), and others have mentioned it in the chatterbox too. I conjecture that this is related to this other error looking at my writeups... error. I can't prove that though, because I don't have enough points of measurements. Waiting a few minutes and the retrying the post seems to work around the problem.