Share via

webapp getting down

STSI Support 0 Reputation points
2025-09-29T15:48:15.33+00:00

We have configured a webapp server, application is not working as expected, it is getting down again and again with the error application error on screen after browsing. Can you ppl help me out on this issue.

How can we get logs to verify the errors in app server and sql db.

Deployment is also taking much time deploy the code some times get Deployment failed because the site failed to start within 10 mins.

InprogressInstances: 0, SuccessfulInstances: 0, FailedInstances: 1

Error: Deployment for site 'app-qa-smart-westus-01' with DeploymentId 'e44abbd3-e386-4af1-8f60-c1b2fd1dc8b4' failed because the worker proccess failed to start within the allotted time.ing failed and showing an error

Azure App Service
Azure App Service

Azure App Service is a service used to create and deploy scalable, mission-critical web apps.


1 answer

Sort by: Most helpful
  1. Anonymous
    2025-09-29T22:21:40.1933333+00:00

    Hi @STSI Support ,

    Thank you for posting your question on Microsoft Q&A.

    If you're experiencing repeated downtime with your Azure Web App, seeing "Application Error" messages, or facing deployment failures because the site doesn't start within 10 minutes, the following troubleshooting steps may help:

    Azure Web App Troubleshooting Steps

    1. Try Azure App Service Diagnostics

    Azure includes a diagnostics tool that can help you pinpoint problems:

    • Navigate to Azure Portal > App Service > Diagnose and solve problems.
    • Check categories such as Availability and Performance for:
      • App Down Workflow
      • Application Logs
      • CPU/Memory Usage
      • Web App Troubleshooter

    Reference: Troubleshoot with Diagnostics - Azure App Service | Microsoft Learn

    This tool also offers options for auto-healing and profiling to help address issues temporarily.

    1. Review Logs for the Web App and SQL Database

    Web App Logs

    • To enable logging in the Azure Portal:
      • Go to App Service > Monitoring > App Service Logs
      • Turn on Application Logging and Web Server Logging
      • Or via CLI:
    az webapp log config --name  --resource-group  --application-logging filesystem --web-server-logging filesystem
    

    Access logs via Kudu Console:

    • Navigate to https://<appname>.scm.azurewebsites.net/DebugConsole
    • Check LogFiles directory for detailed logs

    SQL Database Logs

    • Enable Auditing to monitor events:
      • Navigate to SQL Database > Auditing
      • Select either Log Analytics, Event Hubs, or Azure Storage as the storage destination
    • Access logs in Log Analytics:
      • Run the query: search "SQLSecurityAuditEvents"
      • You can adjust the time range and apply filters as needed

    Common Reasons for Deployment Failures

    Site Doesn’t Start Within 10 Minutes

    This can happen due to:

    • Missing dependencies, such as required Python libraries not included in the container
    • Incorrect startup commands or missing configuration files like web.config or package.json
    • Port is not set correctly (containers should listen on PORT=80)
    • Database connection problems causing the application to crash during startup

    Solutions

    • Increase the startup timeout by adding WEBSITES_CONTAINER_START_TIME_LIMIT in App Settings (maximum: 1800 seconds)
    • Use a startup script (startup.sh) to install any missing libraries
    • Verify the working directory and module paths in your script
    • Review Deployment Center > Logs for detailed error information

    References

    Troubleshoot with Diagnostics - Azure App Service

    Kindly let us know if the above comment helps or you need further assistance on this issue.

    Please "upvote" if the information helped you. This will help us and others in the community as well.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.