Getting module not found error in during site startup

Bitthal Ladiwal 0

I am trying to deploy an azure bot (python-echo-bot) to azure app service using arm templates

https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/python/02.echo-bot
It build successfully but at the site starting process I get this error (see image Screenshot 2025-01-15 140608

)

I am using zip file for the deployment, here is the zip file contents

Screenshot 2025-01-15 124324

And no I am not including the root folder in the zip file.
i am zipping the files inside

BotBuilder-Samples\samples\python\02.echo-bot\

Please help, I am stuck.

Edit:

I noticed that the gunicorn container is listening on port 8000 and the app.py bot runs on port 3978.... also the appCommandLine in the botApp template has command - "

gunicorn --bind 0.0.0.0: --worker-class aiohttp.worker.GunicornWebWorker --timeout 600 app:APP

Sina Salam 15,891 Reputation points

2025-01-15T16:40:30.0466667+00:00
Hello Bitthal Ladiwal,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are getting module not found error in during site startup.

The first thing you might need to look into are missing dependencies or incorrect startup commands, which are common causes of such errors.

However, these are lists of more specific possible steps, to be able to resolve the "module not found" error and successfully deploy your bot to Azure App Service.

Make sure that all necessary dependencies are listed in the requirements.txt file. This file should be at the root of your zip file.

Check that the file structure inside your zip file is correct. The requirements.txt and your main application file (e.g., app.py or bot.py) should be at the root level of the zip file.

Make sure that the startup command points to the correct entry point of your bot application. For example, if your main file is bot.py, the startup command should be:
az webapp config set --resource-group <your-resource-group> --name <your-app-name> --startup-file "python3 bot.py"

Ensure that your ARM template correctly specifies the deployment settings, including the app service plan, web app, and deployment source. This is an example of how to configure your ARM template:
{ "type": "Microsoft.Web/sites", "apiVersion": "2021-02-01", "name": "<your-app-name>", "location": "<your-location>", "properties": { "serverFarmId": "<your-app-service-plan>", "siteConfig": { "appSettings": [ { "name": "WEBSITES_PORT", "value": "8000" } ] } } }

Check the logs for more detailed error messages. You can access the logs through the Azure portal or using the Azure CLI:

az webapp log tail --resource-group <your-resource-group> --name <your-app-name>

I hope this is helpful! Do not hesitate to let me know if you have any other questions.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.
Bitthal Ladiwal 0 Reputation points

2025-01-18T11:53:07.49+00:00
Hi @Sina Salam ,

I was using this github repo - https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/python/

and I tried deploying the the welcom-bot under sample/python/. You can see that app.py is the main file and bots is not python file but a module, inside bots there is a file named echo_bot.py and there is a class EchoBot.

The things I changed it order for this to work:
---> I removed the bots module and took out the echo_bot.py file on the same level as app.py and refactored the import statements as well.
Also in the ARM template in the startup gunicorn command there is no port mentioned only the host which was

gunicorn --bind 0.0.0.0 --worker-class aiohttp.worker.GunicornWebWorker --timeout 600 app:APP

---> and in the config.py which is in the same level as app.py has the port mentioned as "3978" or similar. I also had to change this port to 8000 because I noticed changing the startup gunicorn command did not help me and the server was still listening at port 8000. So I changed the port in config.py.

These are the changes I had to make in order for it to work.
Sina Salam 15,891 Reputation points

2025-01-18T12:38:36.9466667+00:00
Dear Bitthal Ladiwal,

Thank you for your feedback.

You will need to ensure compatibility between gunicorn and the bot, and avoids potential pitfalls in deployment. By aligning the file structure, port configurations, and startup command, the bot will deploy successfully to Azure App Service.

These are the steps you will need to take:

Keep the file structure simple and align it with how gunicorn expects the main module. Place echo_bot.py in the same directory as app.py, and update import statements accordingly.

Set the WEBSITES_PORT to 8000 (the default for gunicorn) in the ARM template:
{ "name": "WEBSITES_PORT", "value": "8000" }
Update config.py (or equivalent configuration file) to use port 8000 instead of 3978: "port": 8000

Modify the gunicorn startup command in the ARM template to explicitly include the port:
gunicorn --bind 0.0.0.0:8000 --worker-class aiohttp.worker.GunicornWebWorker --timeout 600 app:APP

Ensure the requirements.txt file lists all dependencies accurately and check that the app service logs for errors using bash command: az webapp log tail --resource-group <your-resource-group> --name <your-app-name>

This is a "Best Practices" tips: Avoid hardcoding ports in both the gunicorn command and configuration file. Instead, use environment variables:
import os PORT = int(os.environ.get("PORT", 8000))
Make sure the WEBSITES_PORT environment variable is set in your deployment pipeline to match the port defined in the startup command.

Goodluck.
santoshkc 11,785 Reputation points Microsoft Vendor

2025-01-20T09:34:08.7166667+00:00

Hi Bitthal Ladiwal,

Just checking in to see if the below answer provided by @Sina Salam helped.
Bitthal Ladiwal 0 Reputation points

2025-01-22T10:10:54.1166667+00:00

Hi, @santoshkc ,

The answer provided by sina, did not help. I had to make my own changes. In their previous response they just repeated what I did to fix the problem.
Sina Salam 15,891 Reputation points

2025-01-22T14:20:34.4633333+00:00

Dear Bitthal Ladiwal,

Thank you for your feedback.

Sorry for the answer not been helpful but I did repeat what you have done to resolve the issue.

Also, it is good, to know that the issue has been fixed.

I would like you to accept the repetition or give us your detail workaround steps to post here for others going through the same issue in the community.

Thank you as you respond.

Cheers

Share via

Getting module not found error in during site startup

Your answer