Hi all.

We have a strange issue here: some of our users trigger a "0" Status: Request failed error when searching through content. After some digging and testing, we noticed only users with certain roles are affected.

We use roles mostly for organizational purposes, not so much for access restriction. All of our users who are allowed to search through the content have an "internal users" role. This role grants them access to the search engine. Most other roles have no permissions set what so ever.

All users with certain roles (e.g. "teachers") cannot search through the content. They also have the "internal users" role. And if we remove the "teachers" role from a user, the search engine works for her. But if we assign the "teachers" role again, the same error appears.

This error does not appear if a user has the "Access administration pages" permission. We checked several settings, each time with a single checkbox, and that one did it. But, again, if a user has none of the "defective" roles and no "Access administration pages" permission, he can use the search engine without trouble.

Any thoughts ?

CommentFileSizeAuthor
screen.JPG47.74 KBwadmiraal

Comments

wadmiraal’s picture

wadmiraal commented
Status: Active » Fixed

Ok, so after a lot of reading and tracing and debugging and hair pulling, we know what went wrong.

I forgot to mention that we use TAC Lite as well.

The problem is that when there are too many roles (and not necessarily the roles I mentioned before), there's too much data sent to Solr. The GET request gets huge with all the data from TAC lite. There's not much we can do about it. We've reached Apache's limit for GET requests. Solution: recompile Apache...but we would like to avoid that if possible.

So we did a lot of cleaning up with TAC Lite, tried to remove as much information as possible from the TAC Lite schemes, and now it works. The GET request is again at a reasonable size.

We'll bump into this again someday, however. Maybe we'll need to search for another node access module, or deactivate Apache Solr Node Access altogether.

Hope this will help someone, if they ever run into this.

Cheers,

pwolanin’s picture

pwolanin commented
Version: 6.x-1.3 » 6.x-1.x-dev

The most current version of the module will switch to POST if the search is too long - did you try upgrading to the latest version?

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

wadmiraal’s picture

wadmiraal commented

No, not yet. I will though, thanks.