none
ContainerHost crashes: Add-WindowsFeature Web-Mgmt-Service inside container RRS feed

  • Question

  • When working inside the containers I experienced several crahes ("ran into problem and will restart") on the Container Host and the VM restarted

    took me some time to pinpoint it, but it seems running (in the container)

    "Add-WindowsFeature Web-Mgmt-Service" crashes the Host (at round about 89% progress bar).

    Is the IIS Web Management Service not supported (yet)? Or is this a bug?


    Monday, February 1, 2016 5:47 PM

All replies

  • From eventvwr on ContainerHost:

    Log Name:      Application
    Source:        Application Error
    Date:          01.02.2016 18:43:36
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      WIN-D0UGH51VICO
    Description:
    Faulting application name: lsass.exe, version: 10.0.10586.0, time stamp: 0x5632d7c6
    Faulting module name: lsass.exe, version: 10.0.10586.0, time stamp: 0x5632d7c6
    Exception code: 0xc0000005
    Fault offset: 0x0000000000004394
    Faulting process id: 0x274
    Faulting application start time: 0x01d15d174b501a00
    Faulting application path: C:\Windows\system32\lsass.exe
    Faulting module path: C:\Windows\system32\lsass.exe
    Report Id: af562799-8569-486e-b35f-8201bc02bd0c
    Faulting package full name: 
    Faulting package-relative application ID: 
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2016-02-01T17:43:36.417041600Z" />
        <EventRecordID>1785</EventRecordID>
        <Channel>Application</Channel>
        <Computer>WIN-D0UGH51VICO</Computer>
        <Security />
      </System>
      <EventData>
        <Data>lsass.exe</Data>
        <Data>10.0.10586.0</Data>
        <Data>5632d7c6</Data>
        <Data>lsass.exe</Data>
        <Data>10.0.10586.0</Data>
        <Data>5632d7c6</Data>
        <Data>c0000005</Data>
        <Data>0000000000004394</Data>
        <Data>274</Data>
        <Data>01d15d174b501a00</Data>
        <Data>C:\Windows\system32\lsass.exe</Data>
        <Data>C:\Windows\system32\lsass.exe</Data>
        <Data>af562799-8569-486e-b35f-8201bc02bd0c</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    followed by:

    Log Name:      Application
    Source:        Microsoft-Windows-Wininit
    Date:          01.02.2016 18:43:38
    Event ID:      1015
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      WIN-D0UGH51VICO
    Description:
    A critical system process, C:\Windows\system32\lsass.exe, failed with status code c0000005.  The machine must now be restarted.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
        <EventID Qualifiers="49152">1015</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2016-02-01T17:43:38.553168900Z" />
        <EventRecordID>1787</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer>WIN-D0UGH51VICO</Computer>
        <Security />
      </System>
      <EventData>
        <Data>C:\Windows\system32\lsass.exe</Data>
        <Data>c0000005</Data>
      </EventData>
    </Event>
    

    Tuesday, February 2, 2016 8:36 AM
  • I confirm the same behavior even on my environment. I also noticed that if I type a Get-windowsfeature once the container is back running most of the features are missing as if the  connection layer has issues with container host.

    Alex

    Tuesday, February 2, 2016 11:52 AM
  • same behavior here: reduced set of features after re-starting the stopped container (after host restart).

    do you also have problems to start and attach to the container? it does not work with the first docker start and docker attach, i have to "docker start" the container twice and then attach works...



    Tuesday, February 2, 2016 12:01 PM
  • used windows container for the test and had no issues will try to use a docker instance.

    Tuesday, February 2, 2016 12:23 PM
  • Luckily the application I'm trying to containerize still installs without Web-Mgmt-Service, so this issue is not urgent anymore (at least for me)
    Monday, February 8, 2016 4:00 PM