AEM looking for a valid user on content pages

Avatar

Avatar

sawan051

Avatar

sawan051

sawan051

26-11-2019

I just upgraded to AEM 6.5.2 and have content copied from production. The number of users available on different level servers will NOT be same, different levels have different set of users.

Now when I load a page by navigation from coral UI in column view and load any page, the error log is full of missing user errors:

GET /mnt/overlay/wcm/core/content/sites/jcr:content/views/column.0.40.html/content/abc/global/en_yy HTTP/1.1] WARN  AEM Unable to get display name for USER

javax.jcr.RepositoryException: Unable to retrieve properties for USER

        at com.adobe.granite.security.user.internal.UserPropertiesManagerImpl.checkValidAuthorizableInfo(UserPropertiesManagerImpl.java:676)

The USER value here is user-id for different user, who might have created of modified the page. I believe AEM is trying to read from page version history or something.

As the pages are copy of production, but users are not available on every level, I see 100s of such errors on each level.

If I add these missing users on test levels the error goes away, but this seems an un-necessary task for test levels or even on local. [ I will NOT want to copy all users if I just need the content.]

I tried to look for this issue and it seems that people have reported this as known AEM issue.

Migration Error while upgrading to AEM 6.2 from 6.4

If anyone has encountered OR resolved this issue, please suggest.

Thanks in Advance!!

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Vish_dhaliwal

Employee

Avatar

Vish_dhaliwal

Employee

Vish_dhaliwal
Employee

26-11-2019

Hello,

This is a known issue with internal JIRA ID GRANITE-26948 which has been resolved in current master branch.

The workaround is to redirect the warnings into another logs with level "Error".

Regards,

Vishu

Answers (8)

Answers (8)

Avatar

Avatar

Vish_dhaliwal

Employee

Avatar

Vish_dhaliwal

Employee

Vish_dhaliwal
Employee

06-12-2019

Hello Martin,

Take a look at the example in this blog: CQ-OPS - How to Suppress INFOrmational Log Messages From...

In this case, the log level should be ERROR since the messages are thrown as warnings.

Regards,

Vishu

Avatar

Avatar

Vish_dhaliwal

Employee

Avatar

Vish_dhaliwal

Employee

Vish_dhaliwal
Employee

26-11-2019

Hey Sawan,

This might not get backported to 6.5 since there is no functional impact as such. Please raise a daycare ticket with a strong business impact statement in case you require a fix 6.5.

Regards,

Vishu

Avatar

Avatar

martin-nekula-h

Avatar

martin-nekula-h

martin-nekula-h

09-12-2019

Thank You both, it helped, I was configuring it a bit wrongly Nice to hear that it will get addressed.

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

991

Correct Reply

1.0K

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

991

Correct Reply

1.0K
Jörg_Hoh
Employee

07-12-2019

HI Martin,

this warning is caused by references to users (in "jcr:lastModified" or "jcr:created" properties), who do no longer exist.

Avatar

Avatar

Vish_dhaliwal

Employee

Avatar

Vish_dhaliwal

Employee

Vish_dhaliwal
Employee

06-12-2019

Hello Martin,

btw, I see there has been a new backport request opened NPR-30977 for 6.5. So, the chances are this might get fixed in upcoming services packs.

Regards,

Vishu

Avatar

Avatar

Vish_dhaliwal

Employee

Avatar

Vish_dhaliwal

Employee

Vish_dhaliwal
Employee

06-12-2019

Please follow these steps to suppress the  messages:

- Go to /system/console/slinglog

- Log level - ERROR

- Logger: com.adobe.granite.security.user.util.AuthorizableUtil

- Log file: error.log

Regards,

Vishu

Avatar

Avatar

martin-nekula-h

Avatar

martin-nekula-h

martin-nekula-h

06-12-2019

Hello Vishu,

this has been a problem for us as well, after the update. Could you please elaborate about how to redirect the warnings? I haven´t been able to find a configuration for this.

Best Regards

Martin

Avatar

Avatar

sawan051

Avatar

sawan051

sawan051

26-11-2019

Thanks for quick response Vish.dhaliwal​ .

Will this fix be available in any upcoming hotfix or next SP?