Hi @Luca Pierpaoli , Microsoft support team had taken up this issue. Upon investigation, we found that there are no issue on Storage Account and confirmed that the issue you had was not related to Azure.
For similar issues, there are couple of GitHub threads which might help to fix it :
Hope this helps!
thank you for your response .
I'm going to share how the system is configured
I'm running an azure function using docker-compose.
I attached file with the docker-compose configuration I'm using for the azure function only.
I removed application env variable to be more readable
Talking about clock sync with the docker container.
Let me know if you need other info
Hi @Luca Pierpaoli
The clock sync issue means when the clock is not correct on the machine i.e. the client where you are initiating the request.
In a scenario where you are storage SDK and providing the connecting string, internal the SDK will generate the SAS token to authenticate the request.
If the clock time is not correct (out of sync) then tokens there would be a difference in token expiry thus causing the behavior.
I will also need more details on the source code how you are communicating with the storage account as per the exception trace:
Queues\Listeners\QueueListener.cs:line 193 therefore I wish to engage with you offline for a closer look and provide quick and specialized assistance.
Sign in to comment