Publish server has errored with Azure Storage timeout.

[dante8888]

Description:

We are encountering a repository access issue in our AEM Publish instance.

The error occurs intermittently when attempting to retrieve a specific model JSON file.

The error logs indicate a failure to access the repository due to an Azure Storage timeout.

09.10.2024 21:55:39.308 [cm-p73952-e729753-aem-publish-b7559b44f-qwqxh] *WARN* [18.221.162.93 [1728510698739] GET /content/us/en/home.model.json HTTP/1.1] org.apache.jackrabbit.oak.segment.file.FileStore Unable to access repository

org.apache.jackrabbit.oak.segment.spi.RepositoryNotReachableException: com.microsoft.azure.storage.StorageException: The client could not finish the operation within specified maximum execution timeout.

    at org.apache.jackrabbit.oak.segment.azure.AzureUtilities.readBufferFully(AzureUtilities.java:94) [org.apache.jackrabbit.oak-segment-azure:1.68.0]

    at org.apache.jackrabbit.oak.segment.azure.AzureSegmentArchiveReader.doReadSegmentToBuffer(AzureSegmentArchiveReader.java:76) [org.apache.jackrabbit.oak-segment-azure:1.68.0]

Please advise me if you have any idea !

Many Thanks

[martin_ecx_io]

As this is looks like a cloud service instance logging the issue, I'd recommend logging a support ticket for this so the relevant team can investigate internally.

There isn't anything showing on the status.adobe.com so it doesn't look to be a general issue and as it seems intermittent and linked to a specific page it may indicate some specific issue with that object in the azure storage.

[kautuk_sahni]

@dante8888 Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

[Jörg_Hoh · Accepted solution]

I checked briefly, and on that day a single instance was affected a few times by this issue. Nothing in the days before and after, and it's also not a common issue which I am aware of. 

I would consider this a one-time glitch.