I am using Terraform to deploy Azure Functions infrastructure through Azure DevOps release pipeline. Everything works fine but starting from last Friday, I got an error said Function runtime is unable to start. After some investigation, I found out the host.json file is not generated in the Azure Function. Any ideas on what's the potential fix for this?
(Only change is updated Function version v2 to v3, but even I downgrade back to v2, same problem still exists).
Environment:
Azure Function V2/V3
Resources Created By Terraform using App Service Plan Tier
Seems this is an internal issue. Rising a support ticket from the Azure portal will be a good way to find its reason.
Related
I am trying to use Azure DevOps pipelines to build a .NET 5 (Core) web app and deploy it to my Azure app service. I can't find any complete examples in the documentation that achieve this so I'm following this:
https://github.com/shahedc/NetLearnerApp/blob/main/azure-pipelines.yml.txt
However, the Azure deploy task keeps returning this vague error:
In my Azure portal I only get this error:
I am assuming the issue is in my pipeline because deployment works when I deploy it directly from the Deployment Center in the Azure portal. Here are the details for the 3 relevant tasks my pipeline:
I found the solution. It turns out the issue was not in the pipeline, but was caused by a Git connection to the app service I had previously set up in the Azure Deployment Center. Even though I disconnected/removed this Git connection, there was somehow still a residual file left over in Azure that was causing the error. I deleted the 'deployments' folder in Kudu (pictured below) and the pipeline started working as expected.
Getting to the above pictured view:
Navigate to your Azure Function project
Search for Advanced Tools
Open PowerShell
Check if you have disk space available.
Yesterday we started getting this error, even if we tried to re-deploy packages that were successfully deployed just an hour before. Our system guys checked and found out that we reached the space limit and that it was time to upgrade.
P.S. I know that this was answered a long time ago. I am just sharing the solution that was not mentioned here and that worked for us.
think what Dan Beaulieu said in above answers is correct, but one thing to add, in my case, after deleting the deployments folder, remember to restart the app service/web app, which will make it take effect.
I have release azure function app from VSO Azure App Service Deploy release task,
it gives:
System.Nets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions I searched on google, people say the sockets get expired but i am using S3 pricing tier
I have then released the same function app from Visual Studio 2017 which runs perfectly fine without any exceptions.
I am attaching the artifacts, build assets, release pipeline details, please help. I will not be able to move to production unless this issue is resolved.
Structure of Artifacts which is not working
Structure of artifacts which is working fine-published from VS2017
Here is the github link for more details regarding the issue.
https://github.com/microsoft/azure-pipelines-tasks/issues/11345
I had to give a proper storage connection string for the following, instead of UseDevelopmentStorage=true,
So I am using Azure Functions at work and thought I would have a play and install them on my own server. I have successfully installed Azure Functions Runtime 2 (preview).
I have then followed the Java tutorial to create an Azure Function :
https://learn.microsoft.com/en-us/azure/azure-functions/functions-create-first-java-maven
How do I then deploy this function to my own Azure functions server?
In the guide it says about using :
az login
mvn azure-functions:deploy
Unfortunately, mvn azure-functions:deploy is to deploy functions to Azure site as az login is required before deployment, which doesn't support deployment to on-premises Runtime portal.
But the key point is, the on-premises Runtime is obsolete(one year behind the latest bits), new project probably can't work with it even if we find how to publish.
Since v2 becomes GA, it is recommended to leverage custom image for usages out of Azure box.
Update
Missed one point. As AF Team answered in the issue you post, no Java Image for now so the usage of Azure Java Function outside Azure is blocked unless we could figure out creating the image on our own.
I have an Azure Service Bus Trigger that has been working both locally and in our Azure environment. Unfortunately, I had been deploying this to a consumption service plan, and I need it on a regular service plan. All deployments have been via Visua Studio.
No problem, right? I deployed the exact same code to a different service plan (in the same resource group) and it does not work. Messages are not being taken off of the queue.
At first I thought it was a connectivity or configuration issue, but then I noticed that the function isn't listed under "Functions."
I realize that the difference service plan itself isn't likely to be the cause, but I can't figure out what else has changed. I have also redeployed this code using the Consumption Plan and the trigger works perfectly.
Thanks for the advice.
I've just checked the debug console for both versions and there's obviously a lot missing from the one that isn't working. Bummer that VS said the deployment was successful. Btw, the bad version is "running." I guess I'll have to deploy again with some verbose output to see if that helps.
I am deploying to local azure compute emulator. It goes into a loop displaying: Role state Unknown and Destroyed. I can deploy the same exact code to azure cloud with no issues, but it fails in the local deployment. I checked the fusion log to see if there is any assembly load issues with no avail. How can I chase down such an issue?
OK. It turns out I copied the web.config from the earlier version and it brought the old version of DiagnosticMonitorTraceListener and targetFramework. I guess, this is a pretty common pattern of mistake. Once I fixed them by copying them from a health project, it worked like charm.