AEM 6.3 nodename not getting set

Forum|Forum|8 years ago
February 2, 2018
3 replies
1926 views

Hello.

I am using AEM 6.3. Recently, new content seems to not have the nodename property set correctly. I only know this circumstantially; I discovered this because the /siteadmin search stopped working on the names. The search uses /bin/querybuilder.json, with the node name going into the fulltext parameter. In some cases, with slightly older content, it works. But for newer content, it does not.

Then I tested with querybuilder directly. When I have (older) content that works, all three of these queries give the same result:

/bin/querybuilder.json?type=cq:Page&fulltext=mynode

/bin/querybuilder.json?type=cq:Page&nodename=mynode

/bin/querybuilder.json?type=cq:Page&property=jcr%3apath&property.value=/path/to/content/mynode

But with (newer) non-working content, only the last one works.

Other bits of information: We have multiple environments, and on my local machine, it's not a problem... just our testing environment (that I know of). So I don't think the issue is in the content.

Also - if I take a piece of working content and change the name in crx/de, nodename/fulltext no longer works. But if I change it back, it will work again.

The main question is: How do I fix this?

Sub questions: What could cause this? And how can I best troubleshoot this?

Thank you.

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

Best answer by akashdeepAEM

Hi Matt,

We may like to check if in crx/de at path /oak:index/cqPageLucene has node property "corrupt" with some Date value then this index MUST be reindexed for indexing to work properly.

To reindex, we need to set the "reindex" node to "true" value from its default false. Which upon completion will be set back to false value.

We may find similar entry in error.logs
*WARN* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.TrackingCorruptIndexHandler Ignoring corrupt index [/oak:index/cqPageLucene] which has been marked as corrupt since date.This index MUST be reindexed for indexing to work properly.

A

akashdeepAEMAccepted solution

New Participant

Hi Matt,

We may like to check if in crx/de at path /oak:index/cqPageLucene has node property "corrupt" with some Date value then this index MUST be reindexed for indexing to work properly.

To reindex, we need to set the "reindex" node to "true" value from its default false. Which upon completion will be set back to false value.

We may find similar entry in error.logs
*WARN* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.TrackingCorruptIndexHandler Ignoring corrupt index [/oak:index/cqPageLucene] which has been marked as corrupt since date.This index MUST be reindexed for indexing to work properly.

M

Matt-H-Author

New Participant

Yes.