none
Unable to Start deployed functions RRS feed

  • Question

  • I'm running an ARM deployment script  for Azure Functions  v1.0.     Our team managed to deploy our latest changes this morning  with no issues but   now the Dev Team and QA team cannot deploy our instances of the same  build. 

    We keep getting the following error message when  opening the azure function blade to manage a function 

    Error:

    The function runtime is unable to start.

    Session Id: 0959d92b39a540cda6ad2de41b533056

    Timestamp: 2018-09-21T16:28:11.278Z

    x

    Error:

    Internal Server Error - https://csg-mesh-devawpopen-eastus2.azurewebsites.net/admin/host/systemkeys/_master

    Session Id: 0959d92b39a540cda6ad2de41b533056

    Timestamp: 2018-09-21T16:30:09.760Z

    The functions host cannot start for some reason.   Looking in kudu for the log files   I can only see logs at the following locations 

    D:/home/LogFiles/eventlog.xml

    d:/home/LogFiles/kudu/trace

    I do not see any logs    inside the folders at  d:\home\LogFiles\Application

    inside the eventlog.xml  I see 

    <Event>
            <System>
                <Provider Name="ZipFS"/>
                <EventID>0</EventID>
                <Level>1</Level>
                <Task>0</Task>
                <Keywords>Keywords</Keywords>
                <TimeCreated SystemTime="2018-09-21T16:07:16Z"/>
                <EventRecordID>576376640</EventRecordID>
                <Channel>Application</Channel>
                <Computer>RD2818784AF7AB</Computer>
                <Security/>
            </System>
            <EventData>
                <Data>Failed to create security dummy file: 5</Data>
            </EventData>
        </Event>
        <Event>
            <System>
                <Provider Name="IIS AspNetCore Module V2"/>
                <EventID>1032</EventID>
                <Level>4</Level>
                <Task>0</Task>
                <Keywords>Keywords</Keywords>
                <TimeCreated SystemTime="2018-09-21T16:07:16Z"/>
                <EventRecordID>576376687</EventRecordID>
                <Channel>Application</Channel>
                <Computer>RD2818784AF7AB</Computer>
                <Security/>
            </System>
            <EventData>
                <Data>Application 'D:\Program Files (x86)\SiteExtensions\Functions\2.0.12115\64bit\' started the coreclr in-process successfully.</Data>
            </EventData>
        </Event>

     The last event makes me think that the azure function is attempting to start the V 2.0  CLI and not the V1.0 CLI.      Since we were able to deploy to our staging environment  this morning, this makes me believe that something has change during the day,  as we are unable to deploy the same code this afternoon. 

     
    Friday, September 21, 2018 4:39 PM

Answers

  • Hi Frankous,

    This probably means that your ARM template is incorrectly setting FUNCTIONS_EXTENSION_VERSION. Please make sure to set it to ~1. See this page for more info.

    thanks,
    David

    • Marked as answer by Frankous Friday, September 21, 2018 5:25 PM
    Friday, September 21, 2018 5:13 PM

All replies

  • Hi Frankous,

    This probably means that your ARM template is incorrectly setting FUNCTIONS_EXTENSION_VERSION. Please make sure to set it to ~1. See this page for more info.

    thanks,
    David

    • Marked as answer by Frankous Friday, September 21, 2018 5:25 PM
    Friday, September 21, 2018 5:13 PM
  • And please verify that ALL your functions V1 deployments have ~1 set and that ALL of your relevant ARM templates do too.
    Friday, September 21, 2018 5:21 PM
  • Hey David. 

     Your right there is a typo in the  FUNCTIONS_EXTENSION_VERSION .   in our app setting it was 
    FUNCTIONS_EXTENSION_VESION

    strange our deployments used to work  this morning.         Anyways thanks for the extra eyes, the arm template has been updated.

    Friday, September 21, 2018 5:21 PM
  • Yep I just went through and verified the appSettings  for our azure functions projects.

    I can also tell there was an update too since our staging environment  has the bad deploy app Setting of 

    FUNCTIONS_EXTENSION_VESION   and it still runs.    

    Thanks for the quick replies too guys, we were dead in the water testing changes until just now. 
    Friday, September 21, 2018 5:39 PM