Azure Function with Event Hub Trigger works randomly when it runs on docker container locally

Question

Azure Function with Event Hub Trigger works randomly when it runs on docker container locally

Scenario

Azure Function with Event Hub trigger running on docker container
Azure Storage Account on my Azure subscription

Behaviour

Running an Azure Function with Event Hub Trigger as docker container using Azure Storage Account I receive the error attached

45649-azure-storage-account-error.txt
I said randomly in the title because it worked fine for couple of days and then started to throw the issue attached

I want to point out that :

The connection string to Azure Storage is the same used in the days where it worked.
On VS2019 same connection works fine without issues.

MayankBargali-MSFT 53,026 Reputation points

2020-12-09T11:20:53.517+00:00

Hi @Luca Pierpaoli

Can you provide more information on how you are communicating with the storage account? Also, verify if there is any clock sync issue with the docker container.
Luca Pierpaoli 21 Reputation points

2020-12-09T11:33:40.337+00:00
Hi @MayankBargali-MSFT

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

46558-docker-composeyaml.txt

Talking about clock sync with the docker container.

Could you help me to understand your request better ?

Where I have to check for docker container clock sync ?

Thanks
Luca
Luca Pierpaoli 21 Reputation points

2020-12-09T11:34:04.423+00:00

Let me know if you need other info

thank you
Luca
MayankBargali-MSFT 53,026 Reputation points

2020-12-10T08:22:01.787+00:00

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.

MayankBargali-MSFT 53,026 Reputation points

2020-12-09T11:20:53.517+00:00

Hi @Luca Pierpaoli

Can you provide more information on how you are communicating with the storage account? Also, verify if there is any clock sync issue with the docker container.
Luca Pierpaoli 21 Reputation points

2020-12-09T11:33:40.337+00:00

Hi @MayankBargali-MSFT

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

46558-docker-composeyaml.txt

Talking about clock sync with the docker container.

Could you help me to understand your request better ?

Where I have to check for docker container clock sync ?

Thanks
Luca
Luca Pierpaoli 21 Reputation points

2020-12-09T11:34:04.423+00:00

Let me know if you need other info

thank you
Luca
MayankBargali-MSFT 53,026 Reputation points

2020-12-10T08:22:01.787+00:00

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.

Answer 1

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 :

https://github.com/microsoft/WSL/issues/4114
https://github.com/microsoft/WSL/issues/4245
https://github.com/microsoft/WSL/issues/4677

Hope this helps!

Azure Function with Event Hub Trigger works randomly when it runs on docker container locally

0 additional answers

Activity