Unable to log into AEM 6.5

[RobertHarperFS]

This issue is on a UAT standalone instance at work. I am unable to log in due to an Exception being thrown and I am being redirected to an error page. Looking at the error in the error.log file, I am seeing this.

09.04.2024 08:16:34.389 *ERROR* [172.19.53.81 [1712668594378] GET /libs/cq/core/content/welcome.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingException java.io.IOException: java.io.IOException: org.apache.jackrabbit.core.data.DataStoreException: Record 13b992d6e8bf63d38e1a06fee14e89231c617794650a6a2a73467f08a7e55381 does not exist at org.apache.jackrabbit.oak.plugins.blob.BlobStoreBlob$1.read(BlobStoreBlob.java:57) [org.apache.jackrabbit.oak-blob-plugins:1.22.13]...

I can find this record on disk in the repository at ./repository/datastore/13/b9/92/13b992d6e8bf63d38e1a06fee14e89231c617794650a6a2a73467f08a7e55381

Since I am unable to log into the UI, is there a good way to recover/rebuild the indexes? Is there a curl command that I could use to trigger a rebuild of the indexes?

[Harwinder-singh]

@RobertHarperFS looks like a case of repository corruption. 

You can try running a DataStore consistency check using OAK run tool.

https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-16550

[RobertHarperFS]

I looked into that but I do not have permissions to download the tool and install it on the host. It looks like the corruption could have been caused by the logs filling up the disk space. I had IT restore from a backup and moved the logging to a different container where there is more space for logging.