CF Push of Windows Stack applications fails with error: "envoy-nginx application: load: cmd run: exit status 3221225785"
search cancel

CF Push of Windows Stack applications fails with error: "envoy-nginx application: load: cmd run: exit status 3221225785"

book

Article ID: 298211

calendar_today

Updated On: 01-14-2025

Products

VMware Tanzu Application Service for VMs

Issue/Introduction

TAS-Windows stemcell was recently upgraded. Smoke test errand now fails, and can no longer push windows deployments.

The logs in a TAS-W application failing to be pushed are as follows:
2021-03-11T10:48:24.592-07:00 [APP/PROC/WEB/0] [OUT] Server Started for 759611b6-ef1e-4d44-8915-9403f1bea785 
2021-03-11T10:48:25.083-07:00 [PROXY/0] [OUT] envoy-nginx application: tailing error log 
2021-03-11T10:48:25.084-07:00 [PROXY/0] [OUT] envoy-nginx application: start nginx: C:\etc\cf-assets\envoy\nginx.exe -p C:\Users\ContainerAdministrator\AppData\Local\Temp\nginx808966563 
2021-03-11T10:48:25.258-07:00 [PROXY/0] [ERR] 
2021/03/11 17:48:25 envoy-nginx application: load: cmd run: exit status 3221225785 2021-03-11T10:48:25.808-07:00 [PROXY/0] [OUT] Exit status 1 
2021-03-11T10:48:42.048-07:00 [CELL/0] [OUT] Cell 5dc1e683-6525-498a-a1f2-2850c56372ee destroying container for instance 10edcc81-7a54-45d0-537c-0424 
2021-03-11T10:48:42.048-07:00 [CELL/0] [OUT] Cell 5dc1e683-6525-498a-a1f2-2850c56372ee stopping instance 10edcc81-7a54-45d0-537c-0424 
2021-03-11T10:48:42.112-07:00 [API/0] [OUT] Process has crashed with type: "web" 
2021-03-11T10:48:42.121-07:00 [API/0] [OUT] App instance exited with guid dd0e9512-bf31-48ea-b101-90e37e243733 payload: {"instance"=>"10edcc81-7a54-45d0-537c-0424", "index"=>0, "cell_id"=>"5dc1e683-6525-498a-a1f2-2850c56372ee", "reason"=>"CRASHED", "exit_description"=>"PROXY: Exited with status 1; process did not exit; process did not exit", "crash_count"=>16, "crash_timestamp"=>1615484922097270688, "version"=>"c4c6f8fb-504e-44b0-bb17-f6d7edc9ebca"}


Environment

Product Version: 2.10

Resolution

This may be an indication that a Windows update did not run on stemcell. Run the command systeminfo to check the most recent hotfixes installed on Windows cell:

bosh_3910f727271c4dc@WIN-JC3614QB8MU 
C:\Users\bosh_3910f727271c4dc>systeminfo 
Host Name: WIN-JC3614QB8MU 
OS Name: Microsoft Windows Server 2019 Standard 
OS Version: 10.0.17763 N/A Build 17763 OS Manufacturer: Microsoft Corporation
...
Hotfix(s): 3 Hotfix(s) Installed.
[01]: KB4514366
[02]: KB4512577
[03]: KB4512578
Then check the most recent hotfix (example KB4512578) in the list to see when it was published (a simple google search of KB4512578 should tell this).

This issue is one that causes problems with apps starting in the Windows container environment, refer to the following link for more information: https://support.microsoft.com/en-us/topic/you-might-encounter-issues-when-using-windows-server-containers-with-the-february-11-2020-security-update-release-b9a8fcae-950d-7a0b-ac7c-cb6b294cb809. If the most recent hotfix is prior to February 2020, then you are affected by this issue.

Windows updates should be applied to the base stemcell as is called out in stembuild documentation. Additionally you can run the command Get-WindowsUpdate command via powershell but it's better to apply update to stemcell for persistence.