kudu | Mirror of Apache Kudu

I have files under platforms/browser/www in cordova browser platform and I have uploaded that file on azure kudu wwwroot folder. The App running perfectly on local machine but getting error while running on azure app service.

Error:

When I'm debugging it then getting the error at line no 17

I have created an App in Cordova and I just want to run it in browser instead of Android or iOS. My application is running perfectly in local machine by running the command "cordova serve" in my VS Code editor. I'm trying to publish it on Azure with following steps:

1. Created an Azure App with following configuration:

2. Drag and drop all files and folders from platforms/browser/www to Kudu

3. getting following error while browsing:

my initController.js

I have made an Azure DevOps YAML Pipeline which successfully deploys into our testing env; I have copied that pipeline changed the App Name for our Staging Env and the Pipeline fails and gives out this error:

We have deployed a very simple .NET CORE 3 Web API application to Azure Cloud. The application is a web api and talks to a very simple SQL server database hosted in Azure as well. There are two main performance problems we are noticing

All API calls go to DB for either read or write operations. The tables only contain 4 and 5 rows and the queries are just basic select and insert queries with no joins.

1. The first call to the API is very slow (30 seconds to query 1 record in a table of size 10) and we added the timer and noticed it is the DB call that is taking 99.99% of the time. So I used the Azure Data Studio Profiler and realized that the query reached SQL Server after like 29.90 seconds. So the issue is not the query itself. Also, the second, third query etc. are super fast and return within < 30 milli-seconds. So the issue is not the internet connectivity between the Web App and the Azure SQL Database.

2. The bigger problem is that, if you stop calling the API for say 2-3 minutes and then do another call, then again the first query takes 30 seconds. But the subsequent queries are faster.

If this was only happening when w3wp.exe starts then I wouldn't be concerned but if the requests to the API stop coming for 2-3 minutes then again it is down. This is of concern.

We have Always ON set to Yes.

I tried collecting .NET Trace in Azure for the web app but this is giving me this weird error.

Here are the Nuget package versions installed in the VS solution related to EF.

Here is the SQL Server pricing tier.

Is there any other way to collect trace for Azure Web APP. I really need to see the call stack of the code for those 30 seconds to move forward. I have access to KUDU etc.

Thanks.

UPDATE 3 - 8th May 2021

I have posted the answer to my own question. This may not be root cause for other people who face similar problem but at least 1 area to look into.

UPDATE 2 - 7th May 2021

After adding EF Core logging as suggested by Ivan, he is right that the opening of connection is taking too long? Why is that? And how to stop that from happening?

UPDATE 1 - 7th May 2021

Jason Pan - We are using App Service Plan and this is the only application hosted there. The plan is P1V2 (https://azure.microsoft.com/en-us/pricing/details/app-service/windows/).

Ivan Stoev - Yes since the .NET Trace is not working for some reason as explained in my question, we captured the App Insights Profiler Trace to capture the call stack and as per call stack it appears that the connection to the SQL server was opened after 30 seconds. So I made two changes in my code:

a. Removed IDisposable from our Repository class that was having our context inject through DI. Before inside the Dispose method, I was calling Dispose on our context class.

b. I replaced services.AddDbContext with services.AddDbContextPool

I then wrote a test program to call the API method randomly once every 2 to 4 mins for 1 hour and only 1 call took 30 seconds and the remaining 21 took few milli-seconds.

But my next step is to run a 24 hours test (1 call every 2-7 mins for example) to see if this was just fluke or actually the solution.

I've got several webjobs that I deploy using an Azure DevOps pipeline. After the .NET 5 migration I have these errors in Kudu

This happened after .net 5 migration but I don't really think it is connected to it. The app service configuration is set to NET5.

I already try these actions:

1. Manually delete all jobs in kudu and redeploy them
2. Deploy the webjobs in another app service
3. Obviously (ironically) in the local environment it works

The fact that they won't work in another app service means the problem is in the devOps pipeline, but I didn't change it. I mean, it builds in net5 right now, that's all.

Could someone know about this type of error? I never encountered something like this in kudu and It's difficult to even search for a solution.

Thanks in advance.

Using "yo office" generated the custom functions add-in project. Implemented all the necessary custom functions and the addin works fine in local environment.

Now facing following deployment issue when deploying to Azure services.

Invalid start-up command "office-addin-debugging start manifest.xml" in package.json. Please use the format "node ". Missing server.js/app.js files, web.config is not generated Invalid start-up command "office-addin-debugging start manifest.xml" in package.json. Please use the format "node ".\r\nMissing server.js/app.js files, web.config is not generated\r\nC:\Program Files (x86)\SiteExtensions\Kudu\92.30310.5111\bin\Scripts\starter.cmd "C:\home\site\deployments\tools\deploy.cmd"

Following is the script block in package.json

I have a simple Azure Function written in c#, it calls newman, a tool installed through NPM. it works fine locally, but newman is not recognized after deploying to Azure. I installed newman from Kudu console, and I can run newman from Kudu console without any problem, not not when I call it from Azure function:

'newman' is not recognized as an internal or external command,

I'm trying to get a React app running in Azure App Services and having difficulties getting environmental variables to work.

When running locally I'm using a .env.local file to load environmental variables (which isn't checked into git).

We have a spark streaming (spark version 2.4.0 ) job which consumes one Kafka topic(4 partition) which includes business-changes as json with Id. These Kafka values also consist RecordTime field and other fields inside json object. This streaming job upserts a Kudu table according to the Id field.

After a while we noticed that, some updates are really not reflecting the latest state of the values for some id fields. We assume 4 different executor processing per partition and when one of them finishes earlier than other it updates target Kudu table. so if we have values like below: