search

dotnet / runtime

.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
https://docs.microsoft.com/dotnet/core/
MIT License
14.99k stars 4.67k forks source link

[8.0] [wasm] [AOT] HTTP Error 500.30 - ASP.NET Core app failed to start #95160

Open carlossanlop opened 10 months ago

carlossanlop commented 10 months ago

Error Blob

{
  "ErrorMessage": "HTTP Error 500.30 - ASP.NET Core app failed to start",
  "BuildRetry": false,
  "ErrorPattern": "",
  "ExcludeConsoleLog": false
}

Reproduction Steps

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0
ghost commented 10 months ago

Tagging subscribers to 'arch-wasm': @lewing See info in area-owners.md if you want to be subscribed.

Issue Details
### Error Blob ```json { "ErrorMessage": "HTTP Error 500.30 - ASP.NET Core app failed to start", "BuildRetry": false, "ErrorPattern": "", "ExcludeConsoleLog": false } ``` ### Reproduction Steps - PR: https://github.com/dotnet/runtime/pull/95148 - Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=478676 - Queue: `browser-wasm windows Release LibraryTests_HighResource_AOT` from runtime-extra-platforms - Step: `Build product` (Why is it showing up green, but still being reported as a failure?) - Job: https://dev.azure.com/dnceng-public/public/_build/results?buildId=478676&view=logs&j=13711b3e-fe09-5ef6-c164-4a62d0e4a813&t=42061139-9f72-519c-4326-1ecb451c2758&l=15 - Output: ``` ========================== Starting Command Output =========================== "C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "D:\a\_work\_temp\38893e30-51a0-46bf-9ec9-0825eb0fc60d.cmd"" GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1 ##[error](NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start Common solutions to this issue: The app failed to start The app started but then stopped The app started but threw an exception during startup Troubleshooting steps: Check the system event log for error messages Enable logging the application process' stdout messages Attach a debugger to the application process and inspect For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS. Retrying. Waiting for 3 seconds before next attempt (2 of 5). GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1 ##[error](NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start Common solutions to this issue: The app failed to start The app started but then stopped The app started but threw an exception during startup Troubleshooting steps: Check the system event log for error messages Enable logging the application process' stdout messages Attach a debugger to the application process and inspect For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS. Retrying. Waiting for 7 seconds before next attempt (3 of 5). GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1 ##[error](NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start ```
Author: carlossanlop
Assignees: -
Labels: `arch-wasm`, `os-windows`, `blocking-clean-ci`, `wasm-aot-test`, `Known Build Error`
Milestone: -
ghost commented 10 months ago

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries See info in area-owners.md if you want to be subscribed.

Issue Details
### Error Blob ```json { "ErrorMessage": "HTTP Error 500.30 - ASP.NET Core app failed to start", "BuildRetry": false, "ErrorPattern": "", "ExcludeConsoleLog": false } ``` ### Reproduction Steps - PR: https://github.com/dotnet/runtime/pull/95148 - Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=478676 - Queue: `browser-wasm windows Release LibraryTests_HighResource_AOT` from runtime-extra-platforms - Step: `Build product` (Why is it showing up green, but still being reported as a failure?) - Job: https://dev.azure.com/dnceng-public/public/_build/results?buildId=478676&view=logs&j=13711b3e-fe09-5ef6-c164-4a62d0e4a813&t=42061139-9f72-519c-4326-1ecb451c2758&l=15 - Output: ``` ========================== Starting Command Output =========================== "C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "D:\a\_work\_temp\38893e30-51a0-46bf-9ec9-0825eb0fc60d.cmd"" GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1 ##[error](NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start Common solutions to this issue: The app failed to start The app started but then stopped The app started but threw an exception during startup Troubleshooting steps: Check the system event log for error messages Enable logging the application process' stdout messages Attach a debugger to the application process and inspect For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS. Retrying. Waiting for 3 seconds before next attempt (2 of 5). GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1 ##[error](NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start Common solutions to this issue: The app failed to start The app started but then stopped The app started but threw an exception during startup Troubleshooting steps: Check the system event log for error messages Enable logging the application process' stdout messages Attach a debugger to the application process and inspect For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS. Retrying. Waiting for 7 seconds before next attempt (3 of 5). GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1 ##[error](NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start ``` ### Known issue validation **Build: :mag_right:** https://dev.azure.com/dnceng-public/public/_build/results?buildId=478676 **Error message validated:** `HTTP Error 500.30 - ASP.NET Core app failed to start` **Result validation: :white_check_mark:** Known issue matched with the provided build. **Validation performed at:** 11/23/2023 2:40:17 AM UTC ### Report |Build|Definition|Step Name|Console log|Pull Request| |---|---|---|---|---| |[478676](https://dev.azure.com/dnceng-public/public/_build/results?buildId=478676)|dotnet/runtime|windows-x64 Release NativeAOT_Checked_Libs_SpeedOpt |[Log](https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_apis/build/builds/478676/logs/1220)|| #### Summary |24-Hour Hit Count|7-Day Hit Count|1-Month Count| |---|---|---| |0|1|1|
Author: carlossanlop
Assignees: -
Labels: `arch-wasm`, `area-Infrastructure-libraries`, `os-windows`, `blocking-clean-ci`, `untriaged`, `wasm-aot-test`, `Known Build Error`, `needs-area-label`
Milestone: -
ghost commented 10 months ago

Tagging subscribers to this area: @dotnet/runtime-infrastructure See info in area-owners.md if you want to be subscribed.

Issue Details
### Error Blob ```json { "ErrorMessage": "HTTP Error 500.30 - ASP.NET Core app failed to start", "BuildRetry": false, "ErrorPattern": "", "ExcludeConsoleLog": false } ``` ### Reproduction Steps - PR: https://github.com/dotnet/runtime/pull/95148 - Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=478676 - Queue: `browser-wasm windows Release LibraryTests_HighResource_AOT` from runtime-extra-platforms - Step: `Build product` (Why is it showing up green, but still being reported as a failure?) - Job: https://dev.azure.com/dnceng-public/public/_build/results?buildId=478676&view=logs&j=13711b3e-fe09-5ef6-c164-4a62d0e4a813&t=42061139-9f72-519c-4326-1ecb451c2758&l=15 - Output: ``` ========================== Starting Command Output =========================== "C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "D:\a\_work\_temp\38893e30-51a0-46bf-9ec9-0825eb0fc60d.cmd"" GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1 ##[error](NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start Common solutions to this issue: The app failed to start The app started but then stopped The app started but threw an exception during startup Troubleshooting steps: Check the system event log for error messages Enable logging the application process' stdout messages Attach a debugger to the application process and inspect For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS. Retrying. Waiting for 3 seconds before next attempt (2 of 5). GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1 ##[error](NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start Common solutions to this issue: The app failed to start The app started but then stopped The app started but threw an exception during startup Troubleshooting steps: Check the system event log for error messages Enable logging the application process' stdout messages Attach a debugger to the application process and inspect For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS. Retrying. Waiting for 7 seconds before next attempt (3 of 5). GET https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1 ##[error](NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start ``` ### Known issue validation **Build: :mag_right:** https://dev.azure.com/dnceng-public/public/_build/results?buildId=478676 **Error message validated:** `HTTP Error 500.30 - ASP.NET Core app failed to start` **Result validation: :white_check_mark:** Known issue matched with the provided build. **Validation performed at:** 11/23/2023 2:40:17 AM UTC ### Report |Build|Definition|Step Name|Console log|Pull Request| |---|---|---|---|---| |[478676](https://dev.azure.com/dnceng-public/public/_build/results?buildId=478676)|dotnet/runtime|windows-x64 Release NativeAOT_Checked_Libs_SpeedOpt |[Log](https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_apis/build/builds/478676/logs/1220)|| #### Summary |24-Hour Hit Count|7-Day Hit Count|1-Month Count| |---|---|---| |0|1|1|
Author: carlossanlop
Assignees: -
Labels: `arch-wasm`, `os-windows`, `blocking-clean-ci`, `area-Infrastructure`, `untriaged`, `wasm-aot-test`, `Known Build Error`, `needs-area-label`
Milestone: -
jeffschwMSFT commented 7 months ago

was not seen recently... dropping blocking-clean-ci

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0