this error occurs while deploying node app on azure - Starting container for site 2024-01-09T12:31:06.330Z INFO - docker run -d --expose=8080 --name packmen-app-web-services_1_944b3113 -e WEBSITE_USE_DIAGNOSTIC_SERVER=true -e WEBSITE_SITE_NAME=packmen-a

Question

this error occurs while deploying node app on azure - Starting container for site 2024-01-09T12:31:06.330Z INFO - docker run -d --expose=8080 --name packmen-app-web-services_1_944b3113 -e WEBSITE_USE_DIAGNOSTIC_SERVER=true -e WEBSITE_SITE_NAME=packmen-a

Suresh G Nair 0

VenkateshDodda-MSFT 25,251 Reputation points Microsoft Employee Moderator

2024-01-10T06:48:14.9366667+00:00
@Suresh G Nair Thanks for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.

Could you please help us in sharing more insights.

What exactly you are doing?

Is that deployment successful? how are you deploying your application (using vs or by configuring source controls)

Can you share the complete error message by reviewing the log stream logs?

Is there any documentation are you following if yes could you please the same.

Also are you deploying your node application on web app for containers or are you using code option?

Suresh G Nair 0

I was deploying a node js app (react with mongodb) to azure web app service through GitHub actions. Deployment was successful. While accessing app through url isn't available. I look through log stream and find some errors.

2024-01-10T06:39:58.008505880Z    _____                               
2024-01-10T06:39:58.008543481Z   /  _  \ __________ _________   ____  
2024-01-10T06:39:58.008574082Z  /  /_\  \\___   /  |  \_  __ \_/ __ \ 
2024-01-10T06:39:58.008578282Z /    |    \/    /|  |  /|  | \/\  ___/ 
2024-01-10T06:39:58.008581482Z \____|__  /_____ \____/ |__|    \___  >
2024-01-10T06:39:58.008584982Z         \/      \/                  \/ 
2024-01-10T06:39:58.008588082Z A P P   S E R V I C E   O N   L I N U X
2024-01-10T06:39:58.008591282Z 
2024-01-10T06:39:58.008594282Z Documentation: http://aka.ms/webapp-linux
2024-01-10T06:39:58.008597382Z NodeJS quickstart: https://aka.ms/node-qs
2024-01-10T06:39:58.008600482Z NodeJS Version : v20.9.0
2024-01-10T06:39:58.008603582Z Note: Any data outside '/home' is not persisted
2024-01-10T06:39:58.008606782Z 
2024-01-10T06:40:01.772083701Z Starting OpenBSD Secure Shell server: sshd.
2024-01-10T06:40:02.516442901Z Starting periodic command scheduler: cron.
2024-01-10T06:40:03.033727045Z Found build manifest file at '/home/site/wwwroot/oryx-manifest.toml'. Deserializing it...
2024-01-10T06:40:03.046541935Z Build Operation ID: a44e9b93b2573b2e
2024-01-10T06:40:04.712008444Z Environment Variables for Application Insight's Pre-IPA Codeless Configuration exists..
2024-01-10T06:40:04.910501577Z Writing output script to '/opt/startup/startup.sh'
2024-01-10T06:40:05.193960569Z Running #!/bin/sh
2024-01-10T06:40:05.194037770Z 
2024-01-10T06:40:05.194045671Z # Enter the source directory to make sure the script runs where the user expects
2024-01-10T06:40:05.194049771Z cd "/home/site/wwwroot"
2024-01-10T06:40:05.194053271Z 
2024-01-10T06:40:05.194056871Z export NODE_PATH=/usr/local/lib/node_modules:$NODE_PATH
2024-01-10T06:40:05.194060371Z if [ -z "$PORT" ]; then
2024-01-10T06:40:05.194135772Z 		export PORT=8080
2024-01-10T06:40:05.194142072Z fi
2024-01-10T06:40:05.194145372Z 
2024-01-10T06:40:05.194148572Z echo Found tar.gz based node_modules.
2024-01-10T06:40:05.194151772Z extractionCommand="tar -xzf node_modules.tar.gz -C /node_modules"
2024-01-10T06:40:05.194155372Z echo "Removing existing modules directory from root..."
2024-01-10T06:40:05.194158872Z rm -fr /node_modules
2024-01-10T06:40:05.194162072Z mkdir -p /node_modules
2024-01-10T06:40:05.194165172Z echo Extracting modules...
2024-01-10T06:40:05.194168272Z $extractionCommand
2024-01-10T06:40:05.194171372Z export NODE_PATH="/node_modules":$NODE_PATH
2024-01-10T06:40:05.194174572Z export PATH=/node_modules/.bin:$PATH
2024-01-10T06:40:05.194177773Z if [ -d node_modules ]; then
2024-01-10T06:40:05.194200973Z     mv -f node_modules _del_node_modules || true
2024-01-10T06:40:05.194205473Z fi
2024-01-10T06:40:05.194208573Z 
2024-01-10T06:40:05.194211673Z if [ -d /node_modules ]; then
2024-01-10T06:40:05.194214773Z     ln -sfn /node_modules ./node_modules 
2024-01-10T06:40:05.194217973Z fi
2024-01-10T06:40:05.194221073Z 
2024-01-10T06:40:05.194224073Z echo "Done."
2024-01-10T06:40:05.194606379Z export NODE_OPTIONS='--require /usr/local/lib/node_modules/applicationinsights/out/Bootstrap/Oryx.js ' $NODE_OPTIONS
2024-01-10T06:40:05.205058034Z npm start
2024-01-10T06:40:05.253014945Z Found tar.gz based node_modules.
2024-01-10T06:40:05.260008149Z Removing existing modules directory from root...
2024-01-10T06:40:05.293077539Z Extracting modules...

2024-01-10T06:43:50.707Z ERROR - Container packmen-app-web-services_1_153e79ac for site packmen-app-web-services did not start within expected time limit. Elapsed time = 230.9251109 sec
2024-01-10T06:43:50.717Z ERROR - Container packmen-app-web-services_1_153e79ac didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging.
2024-01-10T06:43:51.838Z INFO  - Stopping site packmen-app-web-services because it failed during startup.
2024-01-10T06:45:16  No new trace in the past 1 min(s).
2024-01-10T06:46:16  No new trace in the past 2 min(s).
2024-01-10T06:47:16  No new trace in the past 3 min(s).
2024-01-10T06:48:00.699Z INFO  - Starting container for site
2024-01-10T06:48:00.701Z INFO  - docker run -d --expose=8080 --name packmen-app-web-services_1_9d11bac0 -e WEBSITE_USE_DIAGNOSTIC_SERVER=true -e WEBSITE_SITE_NAME=packmen-app-web-services -e WEBSITE_AUTH_ENABLED=False -e PORT=8080 -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=packmen-app-web-services.azurewebsites.net -e WEBSITE_INSTANCE_ID=436d0a3e8aee4d04857cbdc0264e6696b4edee5752c86ca15a79fe0e49dfdf3c -e HTTP_LOGGING_ENABLED=1 appsvc/node:20-lts_20231109.3.tuxprod 
2024-01-10T06:48:04.081Z INFO  - Initiating warmup request to container packmen-app-web-services_1_9d11bac0 for site packmen-app-web-services
2024-01-10T06:48:35.070Z INFO  - Waiting for response to warmup request for container packmen-app-web-services_1_9d11bac0. Elapsed time = 30.989133 sec
2024-01-10T06:48:50.465Z INFO  - Waiting for response to warmup request for container packmen-app-web-services_1_9d11bac0. Elapsed time = 46.3839651 sec
2024-01-10T06:49:05.918Z INFO  - Waiting for response to warmup request for container packmen-app-web-services_1_9d11bac0. Elapsed time = 61.8374966 sec
Error connecting to log-streaming service:
aborted

VenkateshDodda-MSFT 25,251 Reputation points Microsoft Employee Moderator

2024-01-10T07:04:05.7333333+00:00

@Suresh G Nair Thanks for your swift response. from the above logs , we see that container didnt start within the expected time limit. Could you please add this app setting WEBSITES_CONTAINER_START_TIME_LIMIT value 1800 and check.
Suresh G Nair 0 Reputation points

2024-01-10T07:07:08.1+00:00

Thank you for your response, I'll extend the container startup time limit.
VenkateshDodda-MSFT 25,251 Reputation points Microsoft Employee Moderator

2024-01-10T07:59:14.23+00:00

@Suresh G Nair Thanks for the update post adding the above app settings, I hope the app is up and running and do let me know if you are facing any issues.

1 answer

Your answer

VenkateshDodda-MSFT 25,251 Reputation points Microsoft Employee Moderator

2024-01-10T06:48:14.9366667+00:00

@Suresh G Nair Thanks for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.

Could you please help us in sharing more insights.

What exactly you are doing?

Is that deployment successful? how are you deploying your application (using vs or by configuring source controls)

Can you share the complete error message by reviewing the log stream logs?

Is there any documentation are you following if yes could you please the same.

Also are you deploying your node application on web app for containers or are you using code option?
VenkateshDodda-MSFT 25,251 Reputation points Microsoft Employee Moderator

2024-01-10T07:04:05.7333333+00:00

@Suresh G Nair Thanks for your swift response. from the above logs , we see that container didnt start within the expected time limit. Could you please add this app setting WEBSITES_CONTAINER_START_TIME_LIMIT value 1800 and check.
Suresh G Nair 0 Reputation points

2024-01-10T07:07:08.1+00:00

Thank you for your response, I'll extend the container startup time limit.
VenkateshDodda-MSFT 25,251 Reputation points Microsoft Employee Moderator

2024-01-10T07:59:14.23+00:00

@Suresh G Nair Thanks for the update post adding the above app settings, I hope the app is up and running and do let me know if you are facing any issues.

Answer 1

@Suresh G Nair Thanks for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.

I am summarizing the above and posting the same as Answer for the benefit of community.

Post adding the app setting WEBSITES_CONTAINER_START_TIME_LIMIT with value 1800 from backend logs we see that container is up and able to accept the requests.

If are still facing any issue like application error while requesting the root(/) of your app service I would suggest you enable diagnostic logging and review the application logs or use the webapp Down detector under Diagnose and solve problems to troubleshoot or understand more about these issues. I hope the answer helps. Please let me know if you have any further queries.

Please accept as Yes if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.

Share via

this error occurs while deploying node app on azure - Starting container for site 2024-01-09T12:31:06.330Z INFO - docker run -d --expose=8080 --name packmen-app-web-services_1_944b3113 -e WEBSITE_USE_DIAGNOSTIC_SERVER=true -e WEBSITE_SITE_NAME=packmen-a

1 answer

Your answer