Hello Smith, May I know which command you are using to restart the Odoo server? It will help to identify if the issue is related to the way the server is being restarted

Hi Rushnik, thank you for reaching out. There is a script that is created upon deployment of the ec2 instance. This script is executed whenever the ec2 server is rebooted. I am also able to invoke the script manually after stopping the docker containers for nginx and odoo to perform a manual reboot of the odoo instance. This script executes a docker compose file for both the odoo and nginx containers.

After diving deeper into this, I may have found the issue the command argument in the docker compose file is as follows:

command: >
bash -c "pip install qifparse --break-system-packages && odoo
--addons-path=/usr/lib/python3/dist-packages/odoo/addons,/mnt/odoo/addons,/mnt/odoo/addons/project
--workers=4
--proxy-mode
--database=$DB_NAME
--db_host=$DB_HOST
--db_port=$DB_PORT
--db_user=$DB_USER
--db_password=$DB_PASSWORD
-i base,web,base_account_budget,base_accounting_kit,project_department,project_key,project_milestone_status,project_parent,project_parent_task_filter,project_pivot,project_purchase_link,project_role,project_scrum,project_sequence,project_type,project_template,project_type,project_version,project_task_note,project_role,project_pivot,mail,calendar,contacts,hr,project,sales_team,crm,stock,account
--without-demo=All"

Is " -i base..." potentially causing this issue? Should this only be run once upon initialization of the database, and omitted from the docker compose entirely? I was under the impression that these flags activate the module, but it appears that it might also be remapping the database to default values and overriding things like the company logo.