AEM 6.3: created groups and users are not found in search after server restart | Community
Skip to main content
U
UweJä
Level 2
July 4, 2019

AEM 6.3: created groups and users are not found in search after server restart

  • July 4, 2019
  • 1 reply
  • 9805 views

Hello,

when I create a new group or user in /system/useradmin everything is fine as long as the server keeps running.

When I only log out and back in again, still everything works fine.

But as soon as I stop the instance and start it up again, the users and groups are still there but are not found in the search anymore.

I always have to click through the pages until I find them, which is really annoying.

I tried reindexing the authorisables, because I found that hint in the forum but it didn't solve the issue.

Does anybody have encountered this issue before and knows a solution?

Thanks in advance for your help!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

anujg3325839
Adobe Employee
anujg3325839Adobe Employee
Adobe Employee
July 4, 2019

Did you try to click on Hide users or Hide group and do the search?

Does the touch UI also show the same behavior? Do you see any kind of traversal warning message in error logs?

U
UweJäAuthor
Level 2
July 4, 2019

I clicked hide users and Hide groups several times.

Same behaviour on touch UI.

There are traversal errors but not regarding users or groups but rather certain pages.

For example

04.07.2019 08:23:47.055 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.IndexUpdate Reindexing Traversed #10000 /de/department-landing-info/Communication/germany/public/events/2017/54-jahre-ebm-in-mulfingen

Edit:

Now I probably found the problem in the error.log

04.07.2019 09:07:35.445 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate Marking [/oak:index/authorizables] as corrupt. The index is failing since Do Jul 04 08:37:30 MESZ 2019 ,4 indexing cycles, failed 361 times, skipped 0 time

04.07.2019 09:07:35.451 *WARN* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.TrackingCorruptIndexHandler Ignoring corrupt index [/oak:index/authorizables] which has been marked as corrupt [since Do Jul 04 08:37:30 MESZ 2019 ,4 indexing cycles, failed 361 times, skipped 1 time]. This index MUST be reindexed for indexing to work properly

04.07.2019 09:07:40.443 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate Marking [/oak:index/authorizables] as corrupt. The index is failing since Do Jul 04 08:37:30 MESZ 2019 ,4 indexing cycles, failed 361 times, skipped 1 time

04.07.2019 09:07:45.444 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate Marking [/oak:index/authorizables] as corrupt. The index is failing since Do Jul 04 08:37:30 MESZ 2019 ,4 indexing cycles, failed 361 times, skipped 2 time

04.07.2019 09:07:50.444 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate Marking [/oak:index/authorizables] as corrupt. The index is failing since Do Jul 04 08:37:30 MESZ 2019 ,4 indexing cycles, failed 361 times, skipped 3 time

04.07.2019 09:07:55.444 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate Marking [/oak:index/authorizables] as corrupt. The index is failing since Do Jul 04 08:37:30 MESZ 2019 ,4 indexing cycles, failed 361 times, skipped 4 time

04.07.2019 09:08:00.444 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate Marking [/oak:index/authorizables] as corrupt. The index is failing since Do Jul 04 08:37:30 MESZ 2019 ,4 indexing cycles, failed 361 times, skipped 5 time

But I have absolutely no clue how to fix that.

U
UweJäAuthor
Level 2
July 16, 2019

Hi,

the documentation mentions that the commands are from 1.7.0  Jackrabbit Oak – Oak Run Indexing

To confirm whether its just reindex please try

You can try reindexing by changing the property value 'reindex' from false to true at the path /oak:index/authorizables

Once saved, you can see reindexing for the selected index is triggered in the logs.

Tip : you can check at the below URL to check the status of oak indexes


Hi everybody,

I appreciate your answers and I learned quite a bit from it! Thank you!

I finally was able to resolve issue but in a totally other way than I thought:

Per coincident I found out that the corrupted authorizables-index that was unrepairable with all the measures mentioned above was caused by a corrupted content package. I have absolutely no idea what was wrong with it, but when I uninstalled that package, everything worked fine.

So I installed a freshly built content package from a working server instance and that solved the issue.

Thanks again for your support. Issue solved!

Terms & ConditionsAccessibility statement

Loading footer...