Web app down

Question

Hi everyone,

I am having trouble figuring out why my web app is not working anymore as it was working fine for the last week. I think the error is occurring somewhere in my backend, but I need to help to pinpoint it more specifically. The only information I have really gathered is from the "log stream" of the web app and the docker log: https://yogabackend.scm.azurewebsites.net/api/vfs/LogFiles/2023_12_12_lw0sdlwk0000YH_docker.log

2023-12-11T15:51:34.114Z INFO - Logging is not enabled for this container.Please use [https://aka.ms/linux-diagnostics]() to enable logging to see container logs here.

2023-12-11T15:51:36.391Z INFO - Initiating warmup request to container yogabackend_6_2060730e for site yogabackend

2023-12-11T15:51:53.133Z INFO - Container yogabackend_6_2060730e for site yogabackend initialized successfully and is ready to serve requests./home/LogFiles/2023_12_12_lw0sdlwk0000YH_default_docker.log ([https://yogabackend.scm.azurewebsites.net/api/vfs/LogFiles/2023_12_12_lw0sdlwk0000YH_default_docker.log]())

2023-12-12T11:21:36.076523314Z at Module._resolveFilename (node:internal/modules/cjs/loader:1048:15)

2023-12-12T11:21:36.076525814Z at Module._load (node:internal/modules/cjs/loader:901:27)

2023-12-12T11:21:36.076528214Z at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)

2023-12-12T11:21:36.076530614Z at node:internal/main/run_main_module:23:47 {

2023-12-12T11:21:36.076533114Z code: 'MODULE_NOT_FOUND',

2023-12-12T11:21:36.076535414Z requireStack: []

2023-12-12T11:21:36.076537814Z }

2023-12-12T11:21:36.084171125Z

2023-12-12T11:21:36.084185425Z Node.js v20.9.0

/home/LogFiles/2023_12_12_lw0sdlwk0000YH_docker.log ([https://yogabackend.scm.azurewebsites.net/api/vfs/LogFiles/2023_12_12_lw0sdlwk0000YH_docker.log]())

2023-12-12T11:14:06.153Z ERROR - Container yogabackend_0_0052c858 didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging.

2023-12-12T11:14:06.234Z INFO - Stopping site yogabackend because it failed during startup.

2023-12-12T11:21:17.885Z INFO - Starting container for site

2023-12-12T11:21:17.886Z INFO - docker run -d --expose=8080 --name yogabackend_0_3008e239 -e WEBSITE_USE_DIAGNOSTIC_SERVER=true -e WEBSITE_SITE_NAME=YogaBackend -e WEBSITE_AUTH_ENABLED=False -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=yogabackend.azurewebsites.net -e WEBSITE_INSTANCE_ID=e74ad8f923478178b0ec287aa356d3a79913f84b72e09e658b9f29bde21f16aa appsvc/node:20-lts_20231109.3.tuxprod

2023-12-12T11:21:17.887Z INFO - Logging is not enabled for this container.Please use [https://aka.ms/linux-diagnostics]() to enable logging to see container logs here.

2023-12-12T11:21:24.221Z INFO - Initiating warmup request to container yogabackend_0_3008e239 for site yogabackend

2023-12-12T11:21:37.452Z ERROR - Container yogabackend_0_3008e239 for site yogabackend has exited, failing site start

2023-12-12T11:21:37.454Z ERROR - Container yogabackend_0_3008e239 didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging.

2023-12-12T11:21:37.459Z INFO - Stopping site yogabackend because it failed during startup.Ending Log Tail of existing logs ---Starting Live Log Stream ---

2023-12-12T11:34:05 No new trace in the past 1 min(s).  

The app is hosting our backend for an exam project so it is quite critical that we make it work again. I can provide any other information as well, but as I am not very experienced I was hoping someone here could guide me a bit of the way. Thank you in advance.

Answer 1

Hey @Daniel Javier Christjansen

First step is to enable diagnostic logging on your backend app service by following the steps for a Linux container outlined in https://aka.ms/linux-diagnostics. You can download the full logs at https://<your app name>.scm.azurewebsites.net/api/logs/docker/zip. However, based on hte provided information, your app is failing due to a missing module. The additional diagnostics should provide insight into the which module is not being loaded. Once you replace/deploy that module, your app should start working again. If the module is there, then there could be a dependency error that the module is looking for.