Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The listener for function '' was unable to start.Microsoft.Azure.WebJobs.Host.Listeners.FunctionListenerException : The listener for function #8079

Open
SailleshPawar opened this issue Jan 20, 2022 · 9 comments

Comments

@SailleshPawar
Copy link

Check for a solution in the Azure portal

For issues in production, please check for a solution to common issues in the Azure portal before opening a bug. In the Azure portal, navigate to your function app, select Diagnose and solve problems from the left, and view relevant dashboards before opening your issue.

Investigative information

Please provide the following:

  • Timestamp:
  • FUNCTIONS_EXTENSION_VERSION: 3
  • Function App version:
  • Function App name:
  • Function name(s) (as appropriate):
  • Invocation ID:
  • Region: West Europe

Related information

Provide any related information

  • Programming language used
  • Links to source
  • Bindings used
Azure.RequestFailedException : This request is not authorized to perform this operation.RequestId:3a945827-201e-0031-4515-0e9215000000Time:2022-01-20T15:53:37.3831861ZStatus: 403 (This request is not authorized to perform this operation.)ErrorCode: AuthorizationFailureContent:AuthorizationFailureThis request is not authorized to perform this operation.RequestId:3a945827-201e-0031-4515-0e9215000000Time:2022-01-20T15:53:37.3831861ZHeaders:Server: Microsoft-HTTPAPI/2.0x-ms-request-id: 3a945827-201e-0031-4515-0e9215000000x-ms-client-request-id: 558f6040-c65c-4a6c-b5b0-17968e881fdfx-ms-error-code: AuthorizationFailureDate: Thu, 20 Jan 2022 15:53:36 GMTContent-Length: 246Content-Type: application/xmlat async Azure.Storage.Blobs.BlobRestClient.AcquireLeaseAsync(Nullable`1 timeout,Nullable`1 duration,String proposedLeaseId,Nullable`1 ifModifiedSince,Nullable`1 ifUnmodifiedSince,String ifMatch,String ifNoneMatch,String ifTags,CancellationToken cancellationToken)at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at async Azure.Storage.Blobs.Specialized.BlobLeaseClient.AcquireInternal(TimeSpan duration,RequestConditions conditions,Boolean async,CancellationToken cancellationToken)at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at async Azure.Storage.Blobs.Specialized.BlobLeaseClient.AcquireAsync(TimeSpan duration,RequestConditions conditions,CancellationToken cancellationToken)at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at async Microsoft.Azure.WebJobs.Script.BlobLeaseDistributedLockManager.TryAcquireLeaseAsync(BlobLeaseDistributedLockManager lockManager,BlobClient blobClient,TimeSpan leasePeriod,String proposedLeaseId,CancellationToken cancellationToken,String accountOverride) at D:\a\1\s\src\WebJobs.Script\Host\DistributedLockManagers\BlobLeaseDistributedLockManager.cs : 134at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at async Microsoft.Azure.WebJobs.Script.BlobLeaseDistributedLockManager.TryLockAsync(String account,String lockId,String lockOwnerId,String proposedLeaseId,TimeSpan lockPeriod,CancellationToken cancellationToken) at D:\a\1\s\src\WebJobs.Script\Host\DistributedLockManagers\BlobLeaseDistributedLockManager.cs : 82at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at async Microsoft.Azure.WebJobs.Host.SingletonManager.TryLockAsync(String lockId,String functionInstanceId,SingletonAttribute attribute,CancellationToken cancellationToken,Boolean retry) at C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Singleton\SingletonManager.cs : 113at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at async Microsoft.Azure.WebJobs.Host.Listeners.SingletonListener.StartAsync(CancellationToken cancellationToken) at C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Singleton\SingletonListener.cs : 48at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at async Microsoft.Azure.WebJobs.Host.Listeners.FunctionListener.StartAsync(??) at C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Listeners\FunctionListener.cs : 68End of inner exception
</details>
-->
@ghost ghost assigned kashimiz Jan 20, 2022
@v-bbalaiagar v-bbalaiagar self-assigned this Jan 21, 2022
@v-bbalaiagar
Copy link

Hi @SailleshPawar , Thank you for your feedback! We will check for the possibilities internally and update you with the findings.

@v-bbalaiagar
Copy link

Hi @SailleshPawar , Similar scenarios were tracked earlier as mentioned here - https://docs.microsoft.com/en-us/answers/questions/698846/listener-for-azure-function-was-unable-to-start-er.html
Please check and let us know if this helps.

@SailleshPawar
Copy link
Author

Thanks will check the same. :)

@SailleshPawar
Copy link
Author

@v-bbalaiagar The above mentioned docs is specifying the issue on local env which doesn't seems to be the same, the issue that we are facing is on the function app which is deployed on Azure.

@v-bbalaiagar
Copy link

Hi @SailleshPawar , Thanks for the update, We will investigate this further and update you with the findings.

@dndao
Copy link

dndao commented Mar 30, 2022

I'm experiencing the same problem with a range of function apps running SDK functions 3.0.11 and on framework .Net Core 3.1.

@alecglen
Copy link

Did anyone find a solution to this?

@2010b9
Copy link

2010b9 commented Nov 11, 2024

Same problem here – any solution? 👀

@2010b9
Copy link

2010b9 commented Nov 11, 2024

Not sure if this helps, but in my case I had to go to the networking settings of the storage account associated with my function app. I set the Public network access to Enabled from all networks and after ~5min I got a message in the function app's logs stating [Information] Listener successfully started for function 'Functions.XXXX' after 15 retries.. The Public network access was previously set to Enabled from selected virtual networks and IP addresses. You may not be able to change this setting if it's the IT team controlling your infra, but this may serve as a starting point, I believe. Hope this helps!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants