Azure Function Runtime ~4 is unreachable after running for weeks Australia East

Glenn Sampson 0 Reputation points
2023-02-07T09:46:47.88+00:00

Azure Function (Linux) consumption plan was running fine for a long time TODAY it has stopped working randomly - no changes or deployments

It says that the 'Azure Function Runtime is unreachable' and all my endpoints and triggers are dead.

Steps i've tried to resolve

  1. I have tried to redeploy the function app when its been stopped and running in the portal with this code in vscode func azure functionapp publish <app-name> --force --verbose It returns this error 
    Syncing triggers...
        Request:
        Method: POST, RequestUri: 'https://management.azure.com/subscriptions/<redacted>/resourceGroups/<redacted>/providers/Microsoft.Web/sites/<redacted>/host/default/sync?api-version=2015-08-01', Version: 1.1, Content: System.Net.Http.StringContent, Headers:
        {
          Authorization: Bearer <redacted>
          User-Agent: functions-core-tools/4.0.4915
          Accept: application/json
          x-ms-request-id: <redacted>
          Content-Type: application/json; charset=utf-8
        }
        null
        
        Response:
        StatusCode: 400, ReasonPhrase: 'Bad Request', Version: 1.1, Content: System.Net.Http.HttpConnectionResponseContent, Headers:
        {
          Cache-Control: no-cache
          Pragma: no-cache
          Strict-Transport-Security: max-age=31536000; includeSubDomains
          Server: Microsoft-IIS/10.0
          X-AspNet-Version: 4.0.30319
          X-Powered-By: ASP.NET
          x-ms-ratelimit-remaining-subscription-writes: 1198
          x-ms-request-id: <redacted>
          x-ms-correlation-request-id: <redacted>
          x-ms-routing-request-id: AUSTRALIAEAST:20230207T092005Z:<redacted>
          X-Content-Type-Options: nosniff
          Date: Tue, 07 Feb 2023 09:20:05 GMT
          Content-Length: 346
          Content-Type: application/json; charset=utf-8
          Expires: -1
        }
        {"Code":"BadRequest","Message":"Encountered an error (ServiceUnavailable) from host runtime.","Target":null,"Details":[{"Message":"Encountered an error (ServiceUnavailable) from host runtime."},{"Code":"BadRequest"},{"ErrorEntity":{"Code":"BadRequest","Message":"Encountered an error (ServiceUnavailable) from host runtime."}}],"Innererror":null}
    ```
    
    
1. I have tried to restart the function app in the portal
1. I have also checked the AzureWebJobsStorage setting (storage account is still there, key is still correct)
    
    

How to fix please?
Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,249 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. VenkateshDodda-MSFT 18,191 Reputation points Microsoft Employee
    2023-02-13T04:13:55.8333333+00:00

    @Glenn Sampson Thank you for reaching out to Microsoft Q&A, apologizes for the inconvenience caused on this.

    I have looked at the backend logs and we see that your function app (fro**-functions) is impacted with the recent outage in australia east region here is the more information about the outage. 

    Summary of Impact: Between 04:57 UTC and 13:30 UTC on 07 Feb 2023, you were identified as a customer using App Service in Australia East who may have received intermittent HTTP 500-level response codes, experienced timeouts or high latency when accessing Function apps on Linux consumption SKU.  

    Workaround: Customers may have considered deploying Function App to a different region, such as: Australia Southeast, Southeast Asia, Japan East, Korea Central, East Asia, West India and Central India. Following the documentation: Move your function app between regions in Azure Functions. 

    Mitigation: We performed a configuration change in the underlying partition, helping to manage the workload and process incoming requests as expected, mitigating the issue.

    0 comments