502 Bad Gateway after ubuntu 20 upgrade Inventree 0.15.1 #7246

mabroens · 2024-05-16T18:05:04Z

Deployment Method

Describe the problem*

after runnig sudo apt update && sudo apt upgrade and rebooting my Ubuntu 20 machin i am no longer able to connect to inventree. not remote nor local.
i get :

Please instruct me how to fix this.

Steps to Reproduce

sudo apt update && sudo apt upgrade reboot

Relevant log output

No response

The text was updated successfully, but these errors were encountered:

shapirus · 2024-05-16T20:43:56Z

You need to check the startup logs of inventree (wherever they may be in your particular case). Error 502 means that nginx wasn't able to connect to the inventree backend, which may in turn mean that it's not even starting.

mabroens · 2024-05-17T08:27:24Z

@shapirus thank you for the hint. But i am just a user of the system. Could you give me a few more hints on what or where i should look.

I found in /opt/inventree/log a setup_xxx.log file from yesterday but i could not find startup logs.

I have checked the status for ngunx but that seems to be running.

Any hints pls i really need inventree to be up and running again.

Br Martijn

shapirus · 2024-05-17T09:20:30Z

This is all specific to your particular setup. Since nobody knows the details of how it is configured in your case, it is not likely that someone will be able to give a useful answer. There are many possible ways to start the inventree processes and save (or not save) their logs.
It's best to ask the person who configured it, or consult the manual/guide which was used to set it up.

mabroens · 2024-05-17T18:31:01Z

I can partly understand but as mentioned im a user and yes i installed inventree myself on a bare ubuntu system.
Its been working well for me so far.
I did nit make any changes would not even know how to. I just followed the baremetal installer instructions.

That said I assume there are default locations where inventree stores this log.

You also refer to a manual where should i be able to find this?

Alternatively there will also be a config somewhere that instructs Inventree how to act where to store its data where to save its logs etc.

Can you guide me there? Or pint me to someone that provides helps a s a service? Im based in the Netherlands if that helps.

Br martijn

mabroens · 2024-05-20T09:00:02Z

Question,
i'm still not able to get Inventree up. and was googliong on nginx error debugging etc. and found:https://www.linuxbabe.com/linux-server/how-to-fix-common-nginx-errors

they mention: sudo systemctl status php7.4-fpm which is not running on my machine:

sudo systemctl status php7.4-fpm
Unit php7.4-fpm.service could not be found.

But than i'm not sure if its required or not for inventree.

meanwhile i have also tried reinstalling Inventree ( sudo wget -qO install.sh https://get.inventree.org && bash install.sh )
but also that did not resolve my issue.

any hints help is very much apreciated.

br martijn

SchrodingersGat · 2024-05-20T09:44:45Z

I found in /opt/inventree/log a setup_xxx.log file from yesterday but i could not find startup logs.

Can you share the logs here? Where there any error messages present in those logs?

mabroens · 2024-05-20T09:55:01Z

Hi Oliver,
thanks :-)

these are the latest files:

-rw-r--r--  1 inventree inventree     0 mei  1 00:00 setup_2024-04-29_17_59_17.log
-rw-r--r--  1 inventree inventree 74886 mei  1 00:00 setup_2024-04-29_17_59_17.log.1
-rw-r--r--  1 root      root          0 mei 18 00:00 setup_2024-05-16_19_05_43.log
-rw-r--r--  1 root      root      51660 mei 18 00:00 setup_2024-05-16_19_05_43.log.1
 cat /opt/inventree/log/setup_2024-05-16_19_05_43.log
 cat /opt/inventree/log/setup_2024-05-16_19_05_43.log.1

and the content of setup_2024-05-16_19_05_43.log.1

# Setting base environment variables
# Using existing config file: /etc/inventree/config.yaml
ERROR: Could not open requirements file: [Errno 2] No such file or directory: '/opt/inventree/.github/requirements.txt'
# Collected environment variables:
#    INVENTREE_MEDIA_ROOT=/opt/inventree/data/media
#    INVENTREE_STATIC_ROOT=/opt/inventree/data/static
#    INVENTREE_BACKUP_DIR=/opt/inventree/data/backup
#    INVENTREE_PLUGINS_ENABLED=true
#    INVENTREE_PLUGIN_FILE=/etc/inventree/plugins.txt
#    INVENTREE_SECRET_KEY_FILE=/etc/inventree/secret_key.txt
#    INVENTREE_DB_ENGINE=sqlite3
#    INVENTREE_DB_NAME=/opt/inventree/data/database.sqlite3
#    INVENTREE_DB_USER=sampleuser
#    INVENTREE_DB_HOST=samplehost
#    INVENTREE_DB_PORT=123456
# Getting the IP address of the server via web service
IP address is xx.xx.xxx.xxx
# Setting up python environment
Requirement already satisfied: invoke in ./env/lib/python3.10/site-packages (2.1.3)
Requirement already satisfied: wheel in ./env/lib/python3.10/site-packages (0.40.0)
# Stopping nginx
# Setting up nginx to /etc/nginx/sites-enabled/inventree.conf
# Starting nginx
# (Re)creating init scripts
Nothing to do.
Nothing to do.
# Enabling InvenTree on boot
# Admin data already exists - skipping
# Stopping InvenTree
# Updating InvenTree
Requirement already satisfied: wheel in ./env/lib/python3.10/site-packages (0.40.0)
# inv update| Installing required python packages from 'src/backend/requirements.txt'
# inv update| Requirement already satisfied: pip in ./env/lib/python3.10/site-packages (24.0)
# inv update| Requirement already satisfied: setuptools in ./env/lib/python3.10/site-packages (69.2.0)
# inv update| Collecting setuptools
# inv update|   Downloading setuptools-69.5.1-py3-none-any.whl.metadata (6.2 kB)
# inv update| Downloading setuptools-69.5.1-py3-none-any.whl (894 kB)
# inv update|    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 894.6/894.6 kB 9.0 MB/s eta 0:00:00
# inv update| Installing collected packages: setuptools
# inv update|   Attempting uninstall: setuptools
# inv update|     Found existing installation: setuptools 69.2.0
# inv update|     Uninstalling setuptools-69.2.0:
# inv update|       Successfully uninstalled setuptools-69.2.0
# inv update| Successfully installed setuptools-69.5.1
# inv update| Collecting asgiref==3.8.1 (from -r src/backend/requirements.txt (line 3))
# inv update|   Downloading asgiref-3.8.1-py3-none-any.whl (23 kB)
# inv update| Requirement already satisfied: async-timeout==4.0.3 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 9)) (4.0.3)
# inv update| Requirement already satisfied: attrs==23.2.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 13)) (23.2.0)
# inv update| Collecting babel==2.15.0 (from -r src/backend/requirements.txt (line 19))
# inv update|   Downloading Babel-2.15.0-py3-none-any.whl (9.6 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 9.6/9.6 MB 15.7 MB/s eta 0:00:00
# inv update| Requirement already satisfied: bleach==6.1.0 in ./env/lib/python3.10/site-packages (from bleach[css]==6.1.0->-r src/backend/requirements.txt (line 23)) (6.1.0)
# inv update| Requirement already satisfied: brotli==1.1.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 27)) (1.1.0)
# inv update| Requirement already satisfied: certifi==2024.2.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 112)) (2024.2.2)
# inv update| Requirement already satisfied: cffi==1.16.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 118)) (1.16.0)
# inv update| Requirement already satisfied: charset-normalizer==3.3.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 174)) (3.3.2)
# inv update| Requirement already satisfied: coreapi==2.3.3 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 266)) (2.3.3)
# inv update| Requirement already satisfied: coreschema==0.0.4 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 269)) (0.0.4)
# inv update| Collecting cryptography==42.0.7 (from -r src/backend/requirements.txt (line 273))
# inv update|   Downloading cryptography-42.0.7-cp39-abi3-manylinux_2_28_x86_64.whl (3.8 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.8/3.8 MB 19.9 MB/s eta 0:00:00
# inv update| Requirement already satisfied: cssselect2==0.7.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 309)) (0.7.0)
# inv update| Requirement already satisfied: defusedxml==0.7.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 313)) (0.7.1)
# inv update| Requirement already satisfied: deprecated==1.2.14 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 319)) (1.2.14)
# inv update| Requirement already satisfied: diff-match-patch==20230430 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 326)) (20230430)
# inv update| Collecting dj-rest-auth==6.0.0 (from -r src/backend/requirements.txt (line 330))
# inv update|   Downloading dj-rest-auth-6.0.0.tar.gz (220 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 220.0/220.0 kB 17.9 MB/s eta 0:00:00
# inv update|   Preparing metadata (setup.py): started
# inv update|   Preparing metadata (setup.py): finished with status 'done'
# inv update| Collecting django==4.2.12 (from -r src/backend/requirements.txt (line 332))
# inv update|   Downloading Django-4.2.12-py3-none-any.whl (8.0 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 8.0/8.0 MB 19.0 MB/s eta 0:00:00
# inv update| Collecting django-allauth==0.61.1 (from -r src/backend/requirements.txt (line 366))
# inv update|   Downloading django-allauth-0.61.1.tar.gz (951 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 951.5/951.5 kB 20.8 MB/s eta 0:00:00
# inv update|   Installing build dependencies: started
# inv update|   Installing build dependencies: finished with status 'done'
# inv update|   Getting requirements to build wheel: started
# inv update|   Getting requirements to build wheel: finished with status 'done'
# inv update|   Installing backend dependencies: started
# inv update|   Installing backend dependencies: finished with status 'done'
# inv update|   Preparing metadata (pyproject.toml): started
# inv update|   Preparing metadata (pyproject.toml): finished with status 'done'
# inv update| Requirement already satisfied: django-allauth-2fa==0.11.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 369)) (0.11.1)
# inv update| Requirement already satisfied: django-cleanup==8.1.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 372)) (8.1.0)
# inv update| Requirement already satisfied: django-cors-headers==4.3.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 375)) (4.3.1)
# inv update| Requirement already satisfied: django-crispy-forms==1.14.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 378)) (1.14.0)
# inv update| Requirement already satisfied: django-dbbackup==4.1.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 381)) (4.1.0)
# inv update| Requirement already satisfied: django-error-report-2==0.4.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 384)) (0.4.2)
# inv update| Collecting django-filter==24.2 (from -r src/backend/requirements.txt (line 387))
# inv update|   Downloading django_filter-24.2-py3-none-any.whl (94 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 94.5/94.5 kB 14.6 MB/s eta 0:00:00
# inv update| Requirement already satisfied: django-flags==5.0.13 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 390)) (5.0.13)
# inv update| Requirement already satisfied: django-formtools==2.5.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 393)) (2.5.1)
# inv update| Requirement already satisfied: django-ical==1.9.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 396)) (1.9.2)
# inv update| Requirement already satisfied: django-import-export==3.3.7 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 399)) (3.3.7)
# inv update| Requirement already satisfied: django-js-asset==2.2.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 402)) (2.2.0)
# inv update| Requirement already satisfied: django-maintenance-mode==0.21.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 406)) (0.21.1)
# inv update| Requirement already satisfied: django-markdownify==0.9.3 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 409)) (0.9.3)
# inv update| Requirement already satisfied: django-money==3.2.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 412)) (3.2.0)
# inv update| Requirement already satisfied: django-mptt==0.16.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 415)) (0.16.0)
# inv update| Collecting django-otp==1.5.0 (from -r src/backend/requirements.txt (line 418))
# inv update|   Downloading django_otp-1.5.0-py3-none-any.whl (80 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 81.0/81.0 kB 4.5 MB/s eta 0:00:00
# inv update| Collecting django-picklefield==3.2 (from -r src/backend/requirements.txt (line 422))
# inv update|   Downloading django_picklefield-3.2-py3-none-any.whl (9.5 kB)
# inv update| Requirement already satisfied: django-q-sentry==0.1.6 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 426)) (0.1.6)
# inv update| Collecting django-q2==1.6.2 (from -r src/backend/requirements.txt (line 428))
# inv update|   Downloading django_q2-1.6.2-py3-none-any.whl (101 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 101.2/101.2 kB 16.3 MB/s eta 0:00:00
# inv update| Requirement already satisfied: django-recurrence==1.11.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 431)) (1.11.1)
# inv update| Requirement already satisfied: django-redis==5.4.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 435)) (5.4.0)
# inv update| Requirement already satisfied: django-sesame==3.2.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 438)) (3.2.2)
# inv update| Requirement already satisfied: django-sql-utils==0.7.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 441)) (0.7.0)
# inv update| Requirement already satisfied: django-sslserver==0.22 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 444)) (0.22)
# inv update| Requirement already satisfied: django-stdimage==6.0.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 446)) (6.0.2)
# inv update| Requirement already satisfied: django-taggit==5.0.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 449)) (5.0.1)
# inv update| Requirement already satisfied: django-user-sessions==2.0.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 452)) (2.0.0)
# inv update| Collecting django-weasyprint==2.3.0 (from -r src/backend/requirements.txt (line 455))
# inv update|   Downloading django_weasyprint-2.3.0-py3-none-any.whl (10 kB)
# inv update| Requirement already satisfied: django-xforwardedfor-middleware==2.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 458)) (2.0)
# inv update| Requirement already satisfied: djangorestframework==3.14.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 460)) (3.14.0)
# inv update| Requirement already satisfied: djangorestframework-simplejwt==5.3.1 in ./env/lib/python3.10/site-packages (from djangorestframework-simplejwt[crypto]==5.3.1->-r src/backend/requirements.txt (line 467)) (5.3.1)
# inv update| Collecting drf-spectacular==0.27.2 (from -r src/backend/requirements.txt (line 470))
# inv update|   Downloading drf_spectacular-0.27.2-py3-none-any.whl (102 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 102.9/102.9 kB 12.4 MB/s eta 0:00:00
# inv update| Collecting dulwich==0.22.1 (from -r src/backend/requirements.txt (line 473))
# inv update|   Downloading dulwich-0.22.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (979 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 979.1/979.1 kB 16.4 MB/s eta 0:00:00
# inv update| Requirement already satisfied: et-xmlfile==1.1.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 521)) (1.1.0)
# inv update| Requirement already satisfied: feedparser==6.0.11 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 525)) (6.0.11)
# inv update| Collecting fonttools==4.51.0 (from fonttools[woff]==4.51.0->-r src/backend/requirements.txt (line 528))
# inv update|   Downloading fonttools-4.51.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (4.6 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.6/4.6 MB 16.5 MB/s eta 0:00:00
# inv update| Collecting googleapis-common-protos==1.63.0 (from -r src/backend/requirements.txt (line 572))
# inv update|   Downloading googleapis_common_protos-1.63.0-py2.py3-none-any.whl (229 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 229.1/229.1 kB 11.8 MB/s eta 0:00:00
# inv update| Collecting grpcio==1.63.0 (from -r src/backend/requirements.txt (line 578))
# inv update|   Downloading grpcio-1.63.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (5.6 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 5.6/5.6 MB 16.7 MB/s eta 0:00:00
# inv update| Collecting gunicorn==22.0.0 (from -r src/backend/requirements.txt (line 626))
# inv update|   Downloading gunicorn-22.0.0-py3-none-any.whl (84 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 84.4/84.4 kB 17.9 MB/s eta 0:00:00
# inv update| Requirement already satisfied: html5lib==1.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 629)) (1.1)
# inv update| Collecting icalendar==5.0.12 (from -r src/backend/requirements.txt (line 633))
# inv update|   Downloading icalendar-5.0.12-py3-none-any.whl (116 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 116.3/116.3 kB 11.7 MB/s eta 0:00:00
# inv update| Collecting idna==3.7 (from -r src/backend/requirements.txt (line 637))
# inv update|   Downloading idna-3.7-py3-none-any.whl (66 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 66.8/66.8 kB 17.1 MB/s eta 0:00:00
# inv update| Collecting importlib-metadata==7.0.0 (from -r src/backend/requirements.txt (line 641))
# inv update|   Downloading importlib_metadata-7.0.0-py3-none-any.whl (23 kB)
# inv update| Requirement already satisfied: inflection==0.5.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 648)) (0.5.1)
# inv update| Requirement already satisfied: itypes==1.2.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 652)) (1.2.0)
# inv update| Collecting jinja2==3.1.4 (from -r src/backend/requirements.txt (line 656))
# inv update|   Downloading jinja2-3.1.4-py3-none-any.whl (133 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 133.3/133.3 kB 8.5 MB/s eta 0:00:00
# inv update| Collecting jsonschema==4.22.0 (from -r src/backend/requirements.txt (line 660))
# inv update|   Downloading jsonschema-4.22.0-py3-none-any.whl (88 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 88.3/88.3 kB 15.5 MB/s eta 0:00:00
# inv update| Requirement already satisfied: jsonschema-specifications==2023.12.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 664)) (2023.12.1)
# inv update| Collecting markdown==3.6 (from -r src/backend/requirements.txt (line 668))
# inv update|   Downloading Markdown-3.6-py3-none-any.whl (105 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 105.4/105.4 kB 14.2 MB/s eta 0:00:00
# inv update| Requirement already satisfied: markuppy==1.14 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 672)) (1.14)
# inv update| Requirement already satisfied: markupsafe==2.1.5 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 675)) (2.1.5)
# inv update| Requirement already satisfied: oauthlib==3.2.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 737)) (3.2.2)
# inv update| Requirement already satisfied: odfpy==1.4.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 741)) (1.4.1)
# inv update| Requirement already satisfied: openpyxl==3.1.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 744)) (3.1.2)
# inv update| Collecting opentelemetry-api==1.24.0 (from -r src/backend/requirements.txt (line 748))
# inv update|   Downloading opentelemetry_api-1.24.0-py3-none-any.whl (60 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 60.1/60.1 kB 12.1 MB/s eta 0:00:00
# inv update| Collecting opentelemetry-exporter-otlp==1.24.0 (from -r src/backend/requirements.txt (line 760))
# inv update|   Downloading opentelemetry_exporter_otlp-1.24.0-py3-none-any.whl (7.0 kB)
# inv update| Collecting opentelemetry-exporter-otlp-proto-common==1.24.0 (from -r src/backend/requirements.txt (line 763))
# inv update|   Downloading opentelemetry_exporter_otlp_proto_common-1.24.0-py3-none-any.whl (17 kB)
# inv update| Collecting opentelemetry-exporter-otlp-proto-grpc==1.24.0 (from -r src/backend/requirements.txt (line 769))
# inv update|   Downloading opentelemetry_exporter_otlp_proto_grpc-1.24.0-py3-none-any.whl (18 kB)
# inv update| Collecting opentelemetry-exporter-otlp-proto-http==1.24.0 (from -r src/backend/requirements.txt (line 773))
# inv update|   Downloading opentelemetry_exporter_otlp_proto_http-1.24.0-py3-none-any.whl (16 kB)
# inv update| Collecting opentelemetry-instrumentation==0.45b0 (from -r src/backend/requirements.txt (line 777))
# inv update|   Downloading opentelemetry_instrumentation-0.45b0-py3-none-any.whl (28 kB)
# inv update| Collecting opentelemetry-instrumentation-django==0.45b0 (from -r src/backend/requirements.txt (line 785))
# inv update|   Downloading opentelemetry_instrumentation_django-0.45b0-py3-none-any.whl (18 kB)
# inv update| Collecting opentelemetry-instrumentation-redis==0.45b0 (from -r src/backend/requirements.txt (line 788))
# inv update|   Downloading opentelemetry_instrumentation_redis-0.45b0-py3-none-any.whl (11 kB)
# inv update| Collecting opentelemetry-instrumentation-requests==0.45b0 (from -r src/backend/requirements.txt (line 791))
# inv update|   Downloading opentelemetry_instrumentation_requests-0.45b0-py3-none-any.whl (12 kB)
# inv update| Collecting opentelemetry-instrumentation-wsgi==0.45b0 (from -r src/backend/requirements.txt (line 794))
# inv update|   Downloading opentelemetry_instrumentation_wsgi-0.45b0-py3-none-any.whl (13 kB)
# inv update| Collecting opentelemetry-proto==1.24.0 (from -r src/backend/requirements.txt (line 798))
# inv update|   Downloading opentelemetry_proto-1.24.0-py3-none-any.whl (50 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 50.8/50.8 kB 9.3 MB/s eta 0:00:00
# inv update| Collecting opentelemetry-sdk==1.24.0 (from -r src/backend/requirements.txt (line 805))
# inv update|   Downloading opentelemetry_sdk-1.24.0-py3-none-any.whl (106 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 106.1/106.1 kB 18.8 MB/s eta 0:00:00
# inv update| Collecting opentelemetry-semantic-conventions==0.45b0 (from -r src/backend/requirements.txt (line 811))
# inv update|   Downloading opentelemetry_semantic_conventions-0.45b0-py3-none-any.whl (36 kB)
# inv update| Collecting opentelemetry-util-http==0.45b0 (from -r src/backend/requirements.txt (line 820))
# inv update|   Downloading opentelemetry_util_http-0.45b0-py3-none-any.whl (6.9 kB)
# inv update| Collecting packaging==24.0 (from -r src/backend/requirements.txt (line 827))
# inv update|   Downloading packaging-24.0-py3-none-any.whl (53 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 53.5/53.5 kB 29.8 MB/s eta 0:00:00
# inv update| Requirement already satisfied: pdf2image==1.17.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 831)) (1.17.0)
# inv update| Collecting pillow==10.3.0 (from -r src/backend/requirements.txt (line 834))
# inv update|   Downloading pillow-10.3.0-cp310-cp310-manylinux_2_28_x86_64.whl (4.5 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.5/4.5 MB 8.6 MB/s eta 0:00:00
# inv update| Requirement already satisfied: pint==0.21 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 910)) (0.21)
# inv update| Collecting pip-licenses==4.4.0 (from -r src/backend/requirements.txt (line 913))
# inv update|   Downloading pip_licenses-4.4.0-py3-none-any.whl (20 kB)
# inv update| Collecting prettytable==3.10.0 (from -r src/backend/requirements.txt (line 916))
# inv update|   Downloading prettytable-3.10.0-py3-none-any.whl (28 kB)
# inv update| Collecting protobuf==4.25.3 (from -r src/backend/requirements.txt (line 920))
# inv update|   Downloading protobuf-4.25.3-cp37-abi3-manylinux2014_x86_64.whl (294 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 294.6/294.6 kB 7.2 MB/s eta 0:00:00
# inv update| Requirement already satisfied: py-moneyed==3.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 935)) (3.0)
# inv update| Collecting pycparser==2.22 (from -r src/backend/requirements.txt (line 939))
# inv update|   Downloading pycparser-2.22-py3-none-any.whl (117 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 117.6/117.6 kB 9.7 MB/s eta 0:00:00
# inv update| Collecting pydyf==0.10.0 (from -r src/backend/requirements.txt (line 943))
# inv update|   Downloading pydyf-0.10.0-py3-none-any.whl (8.1 kB)
# inv update| Requirement already satisfied: pyjwt==2.8.0 in ./env/lib/python3.10/site-packages (from pyjwt[crypto]==2.8.0->-r src/backend/requirements.txt (line 947)) (2.8.0)
# inv update| Collecting pyphen==0.15.0 (from -r src/backend/requirements.txt (line 953))
# inv update|   Downloading pyphen-0.15.0-py3-none-any.whl (2.1 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.1/2.1 MB 11.5 MB/s eta 0:00:00
# inv update| Requirement already satisfied: pypng==0.20220715.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 957)) (0.20220715.0)
# inv update| Requirement already satisfied: python-barcode==0.15.1 in ./env/lib/python3.10/site-packages (from python-barcode[images]==0.15.1->-r src/backend/requirements.txt (line 961)) (0.15.1)
# inv update| Collecting python-dateutil==2.9.0.post0 (from -r src/backend/requirements.txt (line 964))
# inv update|   Downloading python_dateutil-2.9.0.post0-py2.py3-none-any.whl (229 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 229.9/229.9 kB 12.8 MB/s eta 0:00:00
# inv update| Requirement already satisfied: python-dotenv==1.0.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 970)) (1.0.1)
# inv update| Collecting python-fsutil==0.14.1 (from -r src/backend/requirements.txt (line 973))
# inv update|   Downloading python_fsutil-0.14.1-py3-none-any.whl (16 kB)
# inv update| Requirement already satisfied: python3-openid==3.2.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 977)) (3.2.0)
# inv update| Requirement already satisfied: pytz==2024.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 981)) (2024.1)
# inv update| Requirement already satisfied: pyyaml==6.0.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 988)) (6.0.1)
# inv update| Requirement already satisfied: qrcode==7.4.2 in ./env/lib/python3.10/site-packages (from qrcode[pil]==7.4.2->-r src/backend/requirements.txt (line 1043)) (7.4.2)
# inv update| Collecting rapidfuzz==3.9.0 (from -r src/backend/requirements.txt (line 1047))
# inv update|   Downloading rapidfuzz-3.9.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (3.4 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.4/3.4 MB 11.5 MB/s eta 0:00:00
# inv update| Collecting redis==5.0.4 (from -r src/backend/requirements.txt (line 1138))
# inv update|   Downloading redis-5.0.4-py3-none-any.whl (251 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 252.0/252.0 kB 9.9 MB/s eta 0:00:00
# inv update| Collecting referencing==0.35.1 (from -r src/backend/requirements.txt (line 1142))
# inv update|   Downloading referencing-0.35.1-py3-none-any.whl (26 kB)
# inv update| Collecting regex==2024.4.28 (from -r src/backend/requirements.txt (line 1148))
# inv update|   Downloading regex-2024.4.28-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (774 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 774.1/774.1 kB 11.3 MB/s eta 0:00:00
# inv update| Requirement already satisfied: requests==2.31.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1228)) (2.31.0)
# inv update| Collecting requests-oauthlib==2.0.0 (from -r src/backend/requirements.txt (line 1236))
# inv update|   Downloading requests_oauthlib-2.0.0-py2.py3-none-any.whl (24 kB)
# inv update| Collecting rpds-py==0.18.1 (from -r src/backend/requirements.txt (line 1240))
# inv update|   Downloading rpds_py-0.18.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.1 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.1/1.1 MB 12.0 MB/s eta 0:00:00
# inv update| Collecting sentry-sdk==2.1.1 (from -r src/backend/requirements.txt (line 1343))
# inv update|   Downloading sentry_sdk-2.1.1-py2.py3-none-any.whl (277 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 277.3/277.3 kB 7.4 MB/s eta 0:00:00
# inv update| Requirement already satisfied: setuptools==69.5.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1347)) (69.5.1)
# inv update| Requirement already satisfied: sgmllib3k==1.0.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1353)) (1.0.0)
# inv update| Requirement already satisfied: six==1.16.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1356)) (1.16.0)
# inv update| Collecting sqlparse==0.5.0 (from -r src/backend/requirements.txt (line 1363))
# inv update|   Downloading sqlparse-0.5.0-py3-none-any.whl (43 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 44.0/44.0 kB 20.0 MB/s eta 0:00:00
# inv update| Requirement already satisfied: tablib==3.5.0 in ./env/lib/python3.10/site-packages (from tablib[html,ods,xls,xlsx,yaml]==3.5.0->-r src/backend/requirements.txt (line 1369)) (3.5.0)
# inv update| Requirement already satisfied: tinycss2==1.2.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirementsWARNING: The candidate selected for download or install is a yanked version: 'django' candidate (version 4.2.12 at https://files.pythonhosted.org/packages/13/b3/4462fc6d771763a273590ecd6e535f284e057f5b8cc1dd41fca774b1072c/Django-4.2.12-py3-none-any.whl (from https://pypi.org/simple/django/) (requires-python:>=3.8))
Reason for being yanked: Release files have Windows end-of-line characters and are missing executable bits.
.txt (line 1373)) (1.2.1)
# inv update| Collecting typing-extensions==4.11.0 (from -r src/backend/requirements.txt (line 1380))
# inv update|   Downloading typing_extensions-4.11.0-py3-none-any.whl (34 kB)
# inv update| Requirement already satisfied: uritemplate==4.1.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1389)) (4.1.1)
# inv update| Collecting urllib3==2.2.1 (from -r src/backend/requirements.txt (line 1395))
# inv update|   Downloading urllib3-2.2.1-py3-none-any.whl (121 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 121.1/121.1 kB 8.3 MB/s eta 0:00:00
# inv update| Collecting wcwidth==0.2.13 (from -r src/backend/requirements.txt (line 1402))
# inv update|   Downloading wcwidth-0.2.13-py2.py3-none-any.whl (34 kB)
# inv update| Collecting weasyprint==61.2 (from -r src/backend/requirements.txt (line 1406))
# inv update|   Downloading weasyprint-61.2-py3-none-any.whl (271 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 271.5/271.5 kB 14.5 MB/s eta 0:00:00
# inv update| Requirement already satisfied: webencodings==0.5.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1410)) (0.5.1)
# inv update| Collecting whitenoise==6.6.0 (from -r src/backend/requirements.txt (line 1418))
# inv update|   Downloading whitenoise-6.6.0-py3-none-any.whl (19 kB)
# inv update| Requirement already satisfied: wrapt==1.16.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1421)) (1.16.0)
# inv update| Requirement already satisfied: xlrd==2.0.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1496)) (2.0.1)
# inv update| Requirement already satisfied: xlwt==1.3.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1500)) (1.3.0)
# inv update| Collecting zipp==3.18.1 (from -r src/backend/requirements.txt (line 1504))
# inv update|   Downloading zipp-3.18.1-py3-none-any.whl (8.2 kB)
# inv update| Requirement already satisfied: zopfli==0.2.3 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1508)) (0.2.3)
# inv update| Building wheels for collected packages: dj-rest-auth, django-allauth
# inv update|   Building wheel for dj-rest-auth (setup.py): started
# inv update|   Building wheel for dj-rest-auth (setup.py): finished with status 'done'
# inv update|   Created wheel for dj-rest-auth: filename=dj_rest_auth-6.0.0-py2.py3-none-any.whl size=250774 sha256=68e1e23e44a84a23a92406d211066c8ffaad0260e68732da81dc8041c4720132
# inv update|   Stored in directory: /tmp/pip-ephem-wheel-cache-2uv1gs4f/wheels/52/57/bc/bf75e7a58965bd0cc7a862d657204e049bbd63567d8ca2bc75
# inv update|   Building wheel for django-allauth (pyproject.toml): started
# inv update|   Building wheel for django-allauth (pyproject.toml): finished with status 'done'
# inv update|   Created wheel for django-allauth: filename=django_allauth-0.61.1-py3-none-any.whl size=1259785 sha256=524dc8e0033146fa8468e8fcb30b8c3975f89e6a1ac66fab74e0e71d5d709a8c
# inv update|   Stored in directory: /tmp/pip-ephem-wheel-cache-2uv1gs4f/wheels/b8/8e/55/e239a6c337430c7d00d97240cd7ad7bda03959ad6b02916ca4
# inv update| Successfully built dj-rest-auth django-allauth
# inv update| Installing collected packages: wcwidth, python-fsutil, zipp, whitenoise, urllib3, typing-extensions, sqlparse, rpds-py, regex, redis, rapidfuzz, python-dateutil, pyphen, pydyf, pycparser, protobuf, prettytable, pillow, packaging, opentelemetry-util-http, opentelemetry-semantic-conventions, markdown, jinja2, idna, grpcio, fonttools, babel, sentry-sdk, referencing, pip-licenses, opentelemetry-proto, importlib-metadata, icalendar, gunicorn, googleapis-common-protos, dulwich, asgiref, weasyprint, requests-oauthlib, opentelemetry-exporter-otlp-proto-common, opentelemetry-api, django, cryptography, opentelemetry-sdk, opentelemetry-instrumentation, jsonschema, django-weasyprint, django-picklefield, django-otp, django-filter, opentelemetry-instrumentation-wsgi, opentelemetry-instrumentation-requests, opentelemetry-instrumentation-redis, opentelemetry-exporter-otlp-proto-http, opentelemetry-exporter-otlp-proto-grpc, drf-spectacular, django-q2, django-allauth, dj-rest-auth, opentelemetry-instrumentation-django, opentelemetry-exporter-otlp
# inv update|   Attempting uninstall: wcwidth
# inv update|     Found existing installation: wcwidth 0.2.6
# inv update|     Uninstalling wcwidth-0.2.6:
# inv update|       Successfully uninstalled wcwidth-0.2.6
# inv update|   Attempting uninstall: python-fsutil
# inv update|     Found existing installation: python-fsutil 0.13.1
# inv update|     Uninstalling python-fsutil-0.13.1:
# inv update|       Successfully uninstalled python-fsutil-0.13.1
# inv update|   Attempting uninstall: zipp
# inv update|     Found existing installation: zipp 3.17.0
# inv update|     Uninstalling zipp-3.17.0:
# inv update|       Successfully uninstalled zipp-3.17.0
# inv update|   Attempting uninstall: urllib3
# inv update|     Found existing installation: urllib3 2.2.0
# inv update|     Uninstalling urllib3-2.2.0:
# inv update|       Successfully uninstalled urllib3-2.2.0
# inv update|   Attempting uninstall: typing-extensions
# inv update|     Found existing installation: typing_extensions 4.9.0
# inv update|     Uninstalling typing_extensions-4.9.0:
# inv update|       Successfully uninstalled typing_extensions-4.9.0
# inv update|   Attempting uninstall: sqlparse
# inv update|     Found existing installation: sqlparse 0.4.4
# inv update|     Uninstalling sqlparse-0.4.4:
# inv update|       Successfully uninstalled sqlparse-0.4.4
# inv update|   Attempting uninstall: rpds-py
# inv update|     Found existing installation: rpds-py 0.17.1
# inv update|     Uninstalling rpds-py-0.17.1:
# inv update|       Successfully uninstalled rpds-py-0.17.1
# inv update|   Attempting uninstall: regex
# inv update|     Found existing installation: regex 2023.12.25
# inv update|     Uninstalling regex-2023.12.25:
# inv update|       Successfully uninstalled regex-2023.12.25
# inv update|   Attempting uninstall: redis
# inv update|     Found existing installation: redis 5.0.1
# inv update|     Uninstalling redis-5.0.1:
# inv update|       Successfully uninstalled redis-5.0.1
# inv update|   Attempting uninstall: rapidfuzz
# inv update|     Found existing installation: rapidfuzz 3.6.1
# inv update|     Uninstalling rapidfuzz-3.6.1:
# inv update|       Successfully uninstalled rapidfuzz-3.6.1
# inv update|   Attempting uninstall: python-dateutil
# inv update|     Found existing installation: python-dateutil 2.8.2
# inv update|     Uninstalling python-dateutil-2.8.2:
# inv update|       Successfully uninstalled python-dateutil-2.8.2
# inv update|   Attempting uninstall: pyphen
# inv update|     Found existing installation: pyphen 0.14.0
# inv update|     Uninstalling pyphen-0.14.0:
# inv update|       Successfully uninstalled pyphen-0.14.0
# inv update|   Attempting uninstall: pydyf
# inv update|     Found existing installation: pydyf 0.8.0
# inv update|     Uninstalling pydyf-0.8.0:
# inv update|       Successfully uninstalled pydyf-0.8.0
# inv update|   Attempting uninstall: pycparser
# inv update|     Found existing installation: pycparser 2.21
# inv update|     Uninstalling pycparser-2.21:
# inv update|       Successfully uninstalled pycparser-2.21
# inv update|   Attempting uninstall: protobuf
# inv update|     Found existing installation: protobuf 4.25.2
# inv update|     Uninstalling protobuf-4.25.2:
# inv update|       Successfully uninstalled protobuf-4.25.2
# inv update|   Attempting uninstall: pillow
# inv update|     Found existing installation: pillow 10.2.0
# inv update|     Uninstalling pillow-10.2.0:
# inv update|       Successfully uninstalled pillow-10.2.0
# inv update|   Attempting uninstall: packaging
# inv update|     Found existing installation: packaging 23.2
# inv update|     Uninstalling packaging-23.2:
# inv update|       Successfully uninstalled packaging-23.2
# inv update|   Attempting uninstall: opentelemetry-util-http
# inv update|     Found existing installation: opentelemetry-util-http 0.43b0
# inv update|     Uninstalling opentelemetry-util-http-0.43b0:
# inv update|       Successfully uninstalled opentelemetry-util-http-0.43b0
# inv update|   Attempting uninstall: opentelemetry-semantic-conventions
# inv update|     Found existing installation: opentelemetry-semantic-conventions 0.43b0
# inv update|     Uninstalling opentelemetry-semantic-conventions-0.43b0:
# inv update|       Successfully uninstalled opentelemetry-semantic-conventions-0.43b0
# inv update|   Attempting uninstall: markdown
# inv update|     Found existing installation: Markdown 3.5.2
# inv update|     Uninstalling Markdown-3.5.2:
# inv update|       Successfully uninstalled Markdown-3.5.2
# inv update|   Attempting uninstall: jinja2
# inv update|     Found existing installation: Jinja2 3.1.3
# inv update|     Uninstalling Jinja2-3.1.3:
# inv update|       Successfully uninstalled Jinja2-3.1.3
# inv update|   Attempting uninstall: idna
# inv update|     Found existing installation: idna 3.6
# inv update|     Uninstalling idna-3.6:
# inv update|       Successfully uninstalled idna-3.6
# inv update|   Attempting uninstall: grpcio
# inv update|     Found existing installation: grpcio 1.54.2
# inv update|     Uninstalling grpcio-1.54.2:
# inv update|       Successfully uninstalled grpcio-1.54.2
# inv update|   Attempting uninstall: fonttools
# inv update|     Found existing installation: fonttools 4.47.2
# inv update|     Uninstalling fonttools-4.47.2:
# inv update|       Successfully uninstalled fonttools-4.47.2
# inv update|   Attempting uninstall: babel
# inv update|     Found existing installation: Babel 2.14.0
# inv update|     Uninstalling Babel-2.14.0:
# inv update|       Successfully uninstalled Babel-2.14.0
# inv update|   Attempting uninstall: sentry-sdk
# inv update|     Found existing installation: sentry-sdk 1.40.0
# inv update|     Uninstalling sentry-sdk-1.40.0:
# inv update|       Successfully uninstalled sentry-sdk-1.40.0
# inv update|   Attempting uninstall: referencing
# inv update|     Found existing installation: referencing 0.33.0
# inv update|     Uninstalling referencing-0.33.0:
# inv update|       Successfully uninstalled referencing-0.33.0
# inv update|   Attempting uninstall: opentelemetry-proto
# inv update|     Found existing installation: opentelemetry-proto 1.22.0
# inv update|     Uninstalling opentelemetry-proto-1.22.0:
# inv update|       Successfully uninstalled opentelemetry-proto-1.22.0
# inv update|   Attempting uninstall: importlib-metadata
# inv update|     Found existing installation: importlib-metadata 6.11.0
# inv update|     Uninstalling importlib-metadata-6.11.0:
# inv update|       Successfully uninstalled importlib-metadata-6.11.0
# inv update|   Attempting uninstall: icalendar
# inv update|     Found existing installation: icalendar 5.0.11
# inv update|     Uninstalling icalendar-5.0.11:
# inv update|       Successfully uninstalled icalendar-5.0.11
# inv update|   Attempting uninstall: gunicorn
# inv update|     Found existing installation: gunicorn 21.2.0
# inv update|     Uninstalling gunicorn-21.2.0:
# inv update|       Successfully uninstalled gunicorn-21.2.0
# inv update|   Attempting uninstall: googleapis-common-protos
# inv update|     Found existing installation: googleapis-common-protos 1.62.0
# inv update|     Uninstalling googleapis-common-protos-1.62.0:
# inv update|       Successfully uninstalled googleapis-common-protos-1.62.0
# inv update|   Attempting uninstall: dulwich
# inv update|     Found existing installation: dulwich 0.21.7
# inv update|     Uninstalling dulwich-0.21.7:
# inv update|       Successfully uninstalled dulwich-0.21.7
# inv update|   Attempting uninstall: asgiref
# inv update|     Found existing installation: asgiref 3.7.2
# inv update|     Uninstalling asgiref-3.7.2:
# inv update|       Successfully uninstalled asgiref-3.7.2
# inv update|   Attempting uninstall: weasyprint
# inv update|     Found existing installation: weasyprint 60.2
# inv update|     Uninstalling weasyprint-60.2:
# inv update|       Successfully uninstalled weasyprint-60.2
# inv update|   Attempting uninstall: requests-oauthlib
# inv update|     Found existing installation: requests-oauthlib 1.3.1
# inv update|     Uninstalling requests-oauthlib-1.3.1:
# inv update|       Successfully uninstalled requests-oauthlib-1.3.1
# inv update|   Attempting uninstall: opentelemetry-exporter-otlp-proto-common
# inv update|     Found existing installation: opentelemetry-exporter-otlp-proto-common 1.22.0
# inv update|     Uninstalling opentelemetry-exporter-otlp-proto-common-1.22.0:
# inv update|       Successfully uninstalled opentelemetry-exporter-otlp-proto-common-1.22.0
# inv update|   Attempting uninstall: opentelemetry-api
# inv update|     Found existing installation: opentelemetry-api 1.22.0
# inv update|     Uninstalling opentelemetry-api-1.22.0:
# inv update|       Successfully uninstalled opentelemetry-api-1.22.0
# inv update|   Attempting uninstall: django
# inv update|     Found existing installation: Django 4.2.11
# inv update|     Uninstalling Django-4.2.11:
# inv update|       Successfully uninstalled Django-4.2.11
# inv update|   Attempting uninstall: cryptography
# inv update|     Found existing installation: cryptography 42.0.4
# inv update|     Uninstalling cryptography-42.0.4:
# inv update|       Successfully uninstalled cryptography-42.0.4
# inv update|   Attempting uninstall: opentelemetry-sdk
# inv update|     Found existing installation: opentelemetry-sdk 1.22.0
# inv update|     Uninstalling opentelemetry-sdk-1.22.0:
# inv update|       Successfully uninstalled opentelemetry-sdk-1.22.0
# inv update|   Attempting uninstall: opentelemetry-instrumentation
# inv update|     Found existing installation: opentelemetry-instrumentation 0.43b0
# inv update|     Uninstalling opentelemetry-instrumentation-0.43b0:
# inv update|       Successfully uninstalled opentelemetry-instrumentation-0.43b0
# inv update|   Attempting uninstall: jsonschema
# inv update|     Found existing installation: jsonschema 4.21.1
# inv update|     Uninstalling jsonschema-4.21.1:
# inv update|       Successfully uninstalled jsonschema-4.21.1
# inv update|   Attempting uninstall: django-weasyprint
# inv update|     Found existing installation: django-weasyprint 2.2.2
# inv update|     Uninstalling django-weasyprint-2.2.2:
# inv update|       Successfully uninstalled django-weasyprint-2.2.2
# inv update|   Attempting uninstall: django-picklefield
# inv update|     Found existing installation: django-picklefield 3.1
# inv update|     Uninstalling django-picklefield-3.1:
# inv update|       Successfully uninstalled django-picklefield-3.1
# inv update|   Attempting uninstall: django-otp
# inv update|     Found existing installation: django-otp 1.3.0
# inv update|     Uninstalling django-otp-1.3.0:
# inv update|       Successfully uninstalled django-otp-1.3.0
# inv update|   Attempting uninstall: django-filter
# inv update|     Found existing installation: django-filter 23.5
# inv update|     Uninstalling django-filter-23.5:
# inv update|       Successfully uninstalled django-filter-23.5
# inv update|   Attempting uninstall: opentelemetry-instrumentation-wsgi
# inv update|     Found existing installation: opentelemetry-instrumentation-wsgi 0.43b0
# inv update|     Uninstalling opentelemetry-instrumentation-wsgi-0.43b0:
# inv update|       Successfully uninstalled opentelemetry-instrumentation-wsgi-0.43b0
# inv update|   Attempting uninstall: opentelemetry-instrumentation-requests
# inv update|     Found existing installation: opentelemetry-instrumentation-requests 0.43b0
# inv update|     Uninstalling opentelemetry-instrumentation-requests-0.43b0:
# inv update|       Successfully uninstalled opentelemetry-instrumentation-requests-0.43b0
# inv update|   Attempting uninstall: opentelemetry-instrumentation-redis
# inv update|     Found existing installation: opentelemetry-instrumentation-redis 0.43b0
# inv update|     Uninstalling opentelemetry-instrumentation-redis-0.43b0:
# inv update|       Successfully uniERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
django-q 1.3.9 requires redis<4.0.0,>=3.5.3, but you have redis 5.0.4 which is incompatible.
2024-05-16 19:06:34,389 ERROR No CSRF_TRUSTED_ORIGINS specified. Please provide a list of trusted origins, or specify INVENTREE_SITE_URL
nstalled opentelemetry-instrumentation-redis-0.43b0
# inv update|   Attempting uninstall: opentelemetry-exporter-otlp-proto-http
# inv update|     Found existing installation: opentelemetry-exporter-otlp-proto-http 1.22.0
# inv update|     Uninstalling opentelemetry-exporter-otlp-proto-http-1.22.0:
# inv update|       Successfully uninstalled opentelemetry-exporter-otlp-proto-http-1.22.0
# inv update|   Attempting uninstall: opentelemetry-exporter-otlp-proto-grpc
# inv update|     Found existing installation: opentelemetry-exporter-otlp-proto-grpc 1.22.0
# inv update|     Uninstalling opentelemetry-exporter-otlp-proto-grpc-1.22.0:
# inv update|       Successfully uninstalled opentelemetry-exporter-otlp-proto-grpc-1.22.0
# inv update|   Attempting uninstall: drf-spectacular
# inv update|     Found existing installation: drf-spectacular 0.27.1
# inv update|     Uninstalling drf-spectacular-0.27.1:
# inv update|       Successfully uninstalled drf-spectacular-0.27.1
# inv update|   Attempting uninstall: django-q2
# inv update|     Found existing installation: django-q2 1.6.1
# inv update|     Uninstalling django-q2-1.6.1:
# inv update|       Successfully uninstalled django-q2-1.6.1
# inv update|   Attempting uninstall: django-allauth
# inv update|     Found existing installation: django-allauth 0.60.1
# inv update|     Uninstalling django-allauth-0.60.1:
# inv update|       Successfully uninstalled django-allauth-0.60.1
# inv update|   Attempting uninstall: dj-rest-auth
# inv update|     Found existing installation: dj-rest-auth 5.0.2
# inv update|     Uninstalling dj-rest-auth-5.0.2:
# inv update|       Successfully uninstalled dj-rest-auth-5.0.2
# inv update|   Attempting uninstall: opentelemetry-instrumentation-django
# inv update|     Found existing installation: opentelemetry-instrumentation-django 0.43b0
# inv update|     Uninstalling opentelemetry-instrumentation-django-0.43b0:
# inv update|       Successfully uninstalled opentelemetry-instrumentation-django-0.43b0
# inv update|   Attempting uninstall: opentelemetry-exporter-otlp
# inv update|     Found existing installation: opentelemetry-exporter-otlp 1.22.0
# inv update|     Uninstalling opentelemetry-exporter-otlp-1.22.0:
# inv update|       Successfully uninstalled opentelemetry-exporter-otlp-1.22.0
# inv update| Successfully installed asgiref-3.8.1 babel-2.15.0 cryptography-42.0.7 dj-rest-auth-6.0.0 django-4.2.12 django-allauth-0.61.1 django-filter-24.2 django-otp-1.5.0 django-picklefield-3.2 django-q2-1.6.2 django-weasyprint-2.3.0 drf-spectacular-0.27.2 dulwich-0.22.1 fonttools-4.51.0 googleapis-common-protos-1.63.0 grpcio-1.63.0 gunicorn-22.0.0 icalendar-5.0.12 idna-3.7 importlib-metadata-7.0.0 jinja2-3.1.4 jsonschema-4.22.0 markdown-3.6 opentelemetry-api-1.24.0 opentelemetry-exporter-otlp-1.24.0 opentelemetry-exporter-otlp-proto-common-1.24.0 opentelemetry-exporter-otlp-proto-grpc-1.24.0 opentelemetry-exporter-otlp-proto-http-1.24.0 opentelemetry-instrumentation-0.45b0 opentelemetry-instrumentation-django-0.45b0 opentelemetry-instrumentation-redis-0.45b0 opentelemetry-instrumentation-requests-0.45b0 opentelemetry-instrumentation-wsgi-0.45b0 opentelemetry-proto-1.24.0 opentelemetry-sdk-1.24.0 opentelemetry-semantic-conventions-0.45b0 opentelemetry-util-http-0.45b0 packaging-24.0 pillow-10.3.0 pip-licenses-4.4.0 prettytable-3.10.0 protobuf-4.25.3 pycparser-2.22 pydyf-0.10.0 pyphen-0.15.0 python-dateutil-2.9.0.post0 python-fsutil-0.14.1 rapidfuzz-3.9.0 redis-5.0.4 referencing-0.35.1 regex-2024.4.28 requests-oauthlib-2.0.0 rpds-py-0.18.1 sentry-sdk-2.1.1 sqlparse-0.5.0 typing-extensions-4.11.0 urllib3-2.2.1 wcwidth-0.2.13 weasyprint-61.2 whitenoise-6.6.0 zipp-3.18.1
# inv update| Installing plugin packages from '/etc/inventree/plugins.txt'
# inv update| Backing up InvenTree database...
# inv update| Python version 3.10.12 - /opt/inventree/env/bin/python3
# Set permissions for data dir and media: /opt/inventree/data
# Starting InvenTree
####################################################################################
This InvenTree install uses nginx, the settings for the webserver can be found in
/etc/nginx/sites-enabled/inventree.conf
Try opening InvenTree with either
http://localhost/ or http://xx.xx.xx.xx/

Admin user data:
   Email:
   Username:
   Password:
####################################################################################

Pls let me know if you require more.

Br Martijn

SchrodingersGat · 2024-05-20T13:52:22Z

@matmair the error message at the start of the log looks suspicious to me:

ERROR: Could not open requirements file: [Errno 2] No such file or directory: '/opt/inventree/.github/requirements.txt'

Is this potentially a mangled path in the installer since we split the source code into the new directories?

asscherhofstede · 2024-05-21T07:35:56Z

have the same issue with a fresh install on a vm, within the logs i only found user warnings. not that he couldnt find the requirements.txt.

asscherhofstede · 2024-05-21T07:48:39Z

have the same issue with a fresh install on a vm, within the logs i only found user warnings. not that he couldnt find the requirements.txt.

config file /etc/inventree/config.yaml

Just fixed my error. in the config there is a line for INVENTREE_SITE_URL:

uncomment that, that was my problem it couldnt find a base url.

SchrodingersGat · 2024-05-21T09:58:56Z

@mabroens can you see if setting the INVENTREE_SITE_URL param in your config file addresses the issue?

mabroens · 2024-05-21T10:02:47Z

Hi Oliver,

I had seen the post and will try but can you be more specific to what config file.
/opt/inventree/conf.yaml?? Or another one

SchrodingersGat · 2024-05-21T11:11:02Z

@asscherhofstede can you please specify exactly which config file you adjusted?

asscherhofstede · 2024-05-21T13:10:20Z

@asscherhofstede can you please specify exactly which config file you adjusted?

@SchrodingersGat @mabroens this one
/etc/inventree/config.yaml

mabroens · 2024-05-21T14:26:04Z

I just tried but my config.yml does not have that line.
config.yaml.txt

asscherhofstede · 2024-05-21T15:28:19Z

I just tried but my config.yml does not have that line. config.yaml.txt

okay im reproducing the error, i just got a clean ubuntu 20.04 install and had the same issue. I've downloaded with sudo apt-get install inventree.
everything seems to work fine every systemctl inventree seems to be working even the log doesnt have any error except userwarnings. but still getting 502 bad gateway.

if found two config.yaml files.

/opt/inventree/src/backend/InvenTree/config.yaml
/etc/inventree/config.yaml

and both files are same, on line 88 you'll see # site_url: 'http://localhost:8000'

uncomment line 88 on config file /etc/inventree/config.yaml

let me know if it works @mabroens

mabroens · 2024-05-21T17:18:12Z

@asscherhofstede
I just checked again my /etc/inventree/config.yaml does not have a localhost reference like you specify.
my /opt/inventree/src/backend/InvenTree/ does not have a config.yaml only config_template.yaml which does have the localhost:8000 entry.

should i just copy config_template.yaml to config.yml and make a backup of the original?

mabroens · 2024-05-21T17:25:41Z

just tried that but without success. still bad gateway

asscherhofstede · 2024-05-22T08:00:25Z

@mabroens can you show us your config file.

mabroens · 2024-05-22T09:22:34Z

sure. i had already copied it 5 above but this is the cat:

cat /etc/inventree/config.yaml

# Secret key for backend
# Use the environment variable INVENTREE_SECRET_KEY_FILE
secret_key_file: '/etc/inventree/secret_key.txt'

# Database backend selection - Configure backend database settings
# Documentation: https://inventree.readthedocs.io/en/latest/start/config/

# Note: Database configuration options can also be specified from environmental variables,
#       with the prefix INVENTREE_DB_
#       e.g INVENTREE_DB_NAME / INVENTREE_DB_USER / INVENTREE_DB_PASSWORD
database:
  # Uncomment (and edit) one of the database configurations below,
  # or specify database options using environment variables

  # Refer to the django documentation for full list of options

  # --- Available options: ---
  # ENGINE: Database engine. Selection from:
  #         - mysql
  #         - postgresql
  #         - sqlite3
  # NAME: Database name
  # USER: Database username (if required)
  # PASSWORD: Database password (if required)
  # HOST: Database host address (if required)
  # PORT: Database host port (if required)

  # --- Database settings ---
  ENGINE: sqlite3
  NAME: '/opt/inventree/data/database.sqlite3'
  USER: sampleuser
  PASSWORD: samplepassword
  HOST: samplehost
  PORT: 123456

  # --- Example Configuration - MySQL ---
  #ENGINE: mysql
  #NAME: inventree
  #USER: inventree
  #PASSWORD: inventree_password
  #HOST: 'localhost'
  #PORT: '3306'

  # --- Example Configuration - Postgresql ---
  #ENGINE: postgresql
  #NAME: inventree
  #USER: inventree
  #PASSWORD: inventree_password
  #HOST: 'localhost'
  #PORT: '5432'

  # --- Example Configuration - sqlite3 ---
  # ENGINE: sqlite3
  # NAME: '/home/inventree/database.sqlite3'

# Set debug to False to run in production mode
# Use the environment variable INVENTREE_DEBUG
debug: False

# Configure the system logging level
# Use environment variable INVENTREE_LOG_LEVEL
# Options: DEBUG / INFO / WARNING / ERROR / CRITICAL
log_level: WARNING

# Select default system language (default is 'en-us')
# Use the environment variable INVENTREE_LANGUAGE
language: en-us

# System time-zone (default is UTC)
# Reference: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
timezone: UTC

# Base currency code (or use env var INVENTREE_BASE_CURRENCY)
base_currency: USD

# Add new user on first startup
#admin_user: admin
#admin_email: info@example.com
#admin_password: inventree

# List of currencies supported by default. Add other currencies here to allow use in InvenTree
currencies:
  - AUD
  - CAD
  - CNY
  - EUR
  - GBP
  - JPY
  - NZD
  - USD

# Email backend configuration
# Ref: https://docs.djangoproject.com/en/dev/topics/email/
# Alternatively, these options can all be set using environment variables,
# with the INVENTREE_EMAIL_ prefix:
# e.g. INVENTREE_EMAIL_HOST / INVENTREE_EMAIL_PORT / INVENTREE_EMAIL_USERNAME
# Refer to the InvenTree documentation for more information

email:
  # backend: 'django.core.mail.backends.smtp.EmailBackend'
  host: ''
  port: 25
  username: ''
  password: ''
  sender: ''
  tls: False
  ssl: False

# Set sentry_enabled to True to report errors back to the maintainers
# Set sentry,dsn to your custom DSN if you want to use your own instance for error reporting
sentry_enabled: False
#sentry_sample_rate: 0.1
#sentry_dsn: https://custom@custom.ingest.sentry.io/custom

# Set this variable to True to enable InvenTree Plugins
# Alternatively, use the environment variable INVENTREE_PLUGINS_ENABLED
plugins_enabled: true
plugin_file: '/etc/inventree/plugins.txt'
#plugin_dir: '/path/to/plugins/'

# Allowed hosts (see ALLOWED_HOSTS in Django settings documentation)
# A list of strings representing the host/domain names that this Django site can serve.
# Default behaviour is to allow all hosts (THIS IS NOT SECURE!)
allowed_hosts:
  - '*'

# Cross Origin Resource Sharing (CORS) settings (see https://github.com/ottoyiu/django-cors-headers)
# Following parameters are
cors:
  # CORS_ORIGIN_ALLOW_ALL - If True, the whitelist will not be used and all origins will be accepted.
  allow_all: True

  # CORS_ORIGIN_WHITELIST - A list of origins that are authorized to make cross-site HTTP requests. Defaults to []
  # whitelist:
  # - https://example.com
  # - https://sub.example.com

# MEDIA_ROOT is the local filesystem location for storing uploaded files
media_root: '/opt/inventree/data/media'

# STATIC_ROOT is the local filesystem location for storing static files
static_root: '/opt/inventree/data/static'

### Backup configuration options ###
# INVENTREE_BACKUP_DIR is the local filesystem location for storing backups
backup_storage: django.core.files.storage.FileSystemStorage
backup_dir: '/opt/inventree/data/backup'
#backup_options:

# Background worker options
background:
  workers: 4
  timeout: 90
  max_attempts: 5

# Optional URL schemes to allow in URL fields
# By default, only the following schemes are allowed: ['http', 'https', 'ftp', 'ftps']
# Uncomment the lines below to allow extra schemes
#extra_url_schemes:
#  - mailto
#  - git
#  - ssh

# Login configuration
login_confirm_days: 3
login_attempts: 5
login_default_protocol: http

# Remote / proxy login
# These settings can introduce security problems if configured incorrectly. Please read
# https://docs.djangoproject.com/en/4.0/howto/auth-remote-user/ for more details
# The header name should be prefixed by `HTTP`. Please read the docs for more details
# https://docs.djangoproject.com/en/stable/ref/request-response/#django.http.HttpRequest.META
remote_login_enabled: False
remote_login_header: HTTP_REMOTE_USER

# Logout redirect configuration
# This setting may be required if using remote / proxy login to redirect requests
# during the logout process (default is 'index'). Please read the docs for more details
# https://docs.djangoproject.com/en/stable/ref/settings/#logout-redirect-url
#logout_redirect_url: 'index'

# Permit custom authentication backends
#authentication_backends:
#  - 'django.contrib.auth.backends.ModelBackend'

#  Custom middleware, sometimes needed alongside an authentication backend change.
#middleware:
#  - 'django.middleware.security.SecurityMiddleware'
#  - 'django.contrib.sessions.middleware.SessionMiddleware'
#  - 'django.middleware.locale.LocaleMiddleware'
#  - 'django.middleware.common.CommonMiddleware'
#  - 'django.middleware.csrf.CsrfViewMiddleware'
#  - 'corsheaders.middleware.CorsMiddleware'
#  - 'django.contrib.auth.middleware.AuthenticationMiddleware'
#  - 'django.contrib.messages.middleware.MessageMiddleware'
#  - 'django.middleware.clickjacking.XFrameOptionsMiddleware'
#  - 'InvenTree.middleware.AuthRequiredMiddleware'

# Add SSO login-backends (see examples below)
# social_backends:
#  - 'allauth.socialaccount.providers.google'
#  - 'allauth.socialaccount.providers.github'
#  - 'allauth.socialaccount.providers.keycloak'

# Add specific settings for social account providers (if required)
# social_providers:
#   keycloak:
#     KEYCLOAK_URL: 'https://keycloak.custom/auth'
#     KEYCLOAK_REALM: 'master'

# Customization options
# Add custom messages to the login page or main interface navbar or exchange the logo
# Use environment variable INVENTREE_CUSTOMIZE or INVENTREE_CUSTOM_LOGO
# customize:
#   login_message: InvenTree demo instance - <a href='https://inventree.readthedocs.io/en/latest/demo/'> Click here for login details</a>
#   navbar_message: <h6>InvenTree demo mode <a href='https://inventree.readthedocs.io/en/latest/demo/'><span class='fas fa-info-circle'></span></a></h6>
#   logo: logo.png
#   splash: splash_screen.jpg
#   hide_admin_link: true
#   hide_password_reset: true

asscherhofstede · 2024-05-22T12:59:06Z

@mabroens thanks for the config file! sorry i didnt notice the previous ones.

first i would set debug to True if you are trying to figure out the error.
And the second is, i just looked trough the config file of the previous version and there is the same line.

try the blank config file from this link:
https://github.com/inventree/InvenTree/blob/master/src/backend/InvenTree/config_template.yaml

and uncomment line 88.

mabroens · 2024-05-22T13:02:22Z

yes i had already done that. see a few up. .

copied it uncommented the line 88 and than open web browser to Inventree . but still bad gateway.
or should i first do another step sorry.

Br Martijn

asscherhofstede · 2024-05-22T13:10:32Z

yes i had already done that. see a few up. .

copied it uncommented the line 88 and than open web browser to Inventree . but still bad gateway. or should i first do another step sorry.

Br Martijn

Yes but thats the template from within your program i mean from the github.

And if debug is true try every sysmtctl even ngix.
If there us any log otherwise i would suggest clean install. Because im not sure if the auto update was any good.

mabroens · 2024-05-22T13:22:12Z

ah that i missed :-) copied it to the system and systemctl restart inventree but still the same error.

you mention "otherwise i would suggest clean install." is that sudo apt-get install inventree and woud that overwrite my exsisting installation?
would that clear/kill/??? my database or do you have any instructions on how to secure my current dB?

my preference would be to do a clean install ie remove all except for my dB

asscherhofstede · 2024-05-22T13:55:16Z

ah that i missed :-) copied it to the system and systemctl restart inventree but still the same error.

you mention "otherwise i would suggest clean install." is that sudo apt-get install inventree and woud that overwrite my exsisting installation? would that clear/kill/??? my database or do you have any instructions on how to secure my current dB?

my preference would be to do a clean install ie remove all except for my dB

I wanna try before that on last thing.

Im using inventree restart instead of systemctl. Not sure if thats any difference.

And try if you would like:
Inventree config:get VAR=INVENTREE_SITE_URL
Im curious if its gets the config settings.

Im not sure how to handle that, maybe its as easy as using the old db. @SchrodingersGat

I think it realy depends on wich version u had before this.

mabroens · 2024-05-22T14:38:34Z

root@ASM100:/home/spectrum# inventree config:get VAR=INVENTREE_SITE_URL
root@ASM100:/home/spectrum#

mabroens · 2024-05-22T14:39:25Z

Oh and tried this: Im using inventree restart instead of systemctl. Not sure if thats any difference. as well but that makes no diff

mabroens · 2024-05-22T14:42:01Z

an otherthing i tried, for what its worth.:

root@ASM100:~# inventree logs --tail
==> /var/log/inventree/setup_2023-04-07_09_01_45.log <==

==> /var/log/inventree/setup_2023-04-25_15_30_41.log <==

==> /var/log/inventree/setup_2023-05-25_21_00_40.log <==

==> /var/log/inventree/setup_2023-07-02_20_27_31.log <==

==> /var/log/inventree/setup_2023-07-03_09_09_36.log <==

==> /var/log/inventree/setup_2023-07-09_11_13_05.log <==

==> /var/log/inventree/setup_2023-07-18_12_13_47.log <==

==> /var/log/inventree/setup_2023-08-27_10_32_12.log <==

==> /var/log/inventree/setup_2024-04-29_17_59_17.log <==

==> /var/log/inventree/setup_2024-05-16_19_05_43.log <==
mei 22 16:16:17 ASM100 systemd[1]: inventree-worker-1.service: Scheduled restart job, restart counter is at 5.
mei 22 16:16:17 ASM100 systemd[1]: inventree-web-1.service: Scheduled restart job, restart counter is at 5.
mei 22 16:16:17 ASM100 systemd[1]: Stopped inventree-web-1.service.
mei 22 16:16:17 ASM100 systemd[1]: inventree-web-1.service: Start request repeated too quickly.
mei 22 16:16:17 ASM100 systemd[1]: inventree-web-1.service: Failed with result 'exit-code'.
mei 22 16:16:17 ASM100 systemd[1]: Failed to start inventree-web-1.service.
mei 22 16:16:17 ASM100 systemd[1]: Stopped inventree-worker-1.service.
mei 22 16:16:17 ASM100 systemd[1]: inventree-worker-1.service: Start request repeated too quickly.
mei 22 16:16:17 ASM100 systemd[1]: inventree-worker-1.service: Failed with result 'exit-code'.
mei 22 16:16:17 ASM100 systemd[1]: Failed to start inventree-worker-1.service.
^C

mabroens · 2024-05-23T06:49:09Z

@SchrodingersGat ,

happy to debug but would also love to get it operational again. if i run sudo apt-get install inventree would that impact my exsisting dB in any way??

or do you have any recommendations steps to take?

SchrodingersGat · 2024-05-23T11:30:47Z

@mabroens to confirm did you set the site_url in your config file? Or via the INVENTREE_SITE_URL environment variable?

Strange that you are not getting any logs from systemctl.. Can you show the output of:

journalctl -u inventree-web-1.service

mabroens · 2024-05-23T13:32:30Z

root@ASM100:~# journalctl -u inventree-web-1.service
apr 07 09:01:54 ASM100 systemd[1]: Started inventree-web-1.service.
apr 07 09:01:54 ASM100 inventree-web-1.service[32931]: /opt/inventree/vendor/pkgr/processes/web: 2: exec: env/bin/gunicorn: not f>
apr 07 09:01:54 ASM100 systemd[1]: inventree-web-1.service: Main process exited, code=exited, status=127/n/a
apr 07 09:01:54 ASM100 systemd[1]: inventree-web-1.service: Failed with result 'exit-code'.
apr 07 09:01:55 ASM100 systemd[1]: inventree-web-1.service: Scheduled restart job, restart counter is at 1.
apr 07 09:01:55 ASM100 systemd[1]: inventree-web-1.service: Scheduled restart job, restart counter is at 2.
apr 07 09:01:55 ASM100 systemd[1]: Stopped inventree-web-1.service.
apr 07 09:01:55 ASM100 systemd[1]: Started inventree-web-1.service.
apr 07 09:01:55 ASM100 inventree-web-1.service[33075]: /opt/inventree/vendor/pkgr/processes/web: 2: exec: env/bin/gunicorn: not f>
apr 07 09:01:55 ASM100 systemd[1]: inventree-web-1.service: Main process exited, code=exited, status=127/n/a
apr 07 09:01:55 ASM100 systemd[1]: inventree-web-1.service: Failed with result 'exit-code'.
apr 07 09:01:55 ASM100 systemd[1]: Stopped inventree-web-1.service.
apr 07 09:03:36 ASM100 systemd[1]: Started inventree-web-1.service.
apr 07 09:03:36 ASM100 inventree-web-1.service[33679]: [2023-04-07 09:03:36 +0200] [33679] [INFO] Starting gunicorn 20.1.0
apr 07 09:03:36 ASM100 inventree-web-1.service[33679]: [2023-04-07 09:03:36 +0200] [33679] [INFO] Listening at: http://0.0.0.0:60>
apr 07 09:03:36 ASM100 inventree-web-1.service[33679]: [2023-04-07 09:03:36 +0200] [33679] [INFO] Using worker: sync
apr 07 09:03:36 ASM100 inventree-web-1.service[33820]: [2023-04-07 09:03:36 +0200] [33820] [INFO] Booting worker with pid: 33820
apr 07 09:03:36 ASM100 inventree-web-1.service[33822]: [2023-04-07 09:03:36 +0200] [33822] [INFO] Booting worker with pid: 33822
apr 07 09:03:36 ASM100 inventree-web-1.service[33825]: [2023-04-07 09:03:36 +0200] [33825] [INFO] Booting worker with pid: 33825
apr 07 09:03:36 ASM100 inventree-web-1.service[33824]: [2023-04-07 09:03:36 +0200] [33824] [INFO] Booting worker with pid: 33824
apr 07 09:03:36 ASM100 inventree-web-1.service[33828]: [2023-04-07 09:03:36 +0200] [33828] [INFO] Booting worker with pid: 33828
apr 07 09:03:36 ASM100 inventree-web-1.service[33832]: [2023-04-07 09:03:36 +0200] [33832] [INFO] Booting worker with pid: 33832
apr 07 09:03:36 ASM100 inventree-web-1.service[33829]: [2023-04-07 09:03:36 +0200] [33829] [INFO] Booting worker with pid: 33829
apr 07 09:03:36 ASM100 inventree-web-1.service[33853]: [2023-04-07 09:03:36 +0200] [33853] [INFO] Booting worker with pid: 33853
apr 07 09:03:37 ASM100 inventree-web-1.service[33854]: [2023-04-07 09:03:37 +0200] [33854] [INFO] Booting worker with pid: 33854
apr 07 09:03:42 ASM100 inventree-web-1.service[33829]: 07:03:42 [Q] INFO Enqueued 3
apr 07 09:03:42 ASM100 inventree-web-1.service[33825]: 07:03:42 [Q] INFO Enqueued 4
apr 07 09:03:43 ASM100 inventree-web-1.service[33832]: 07:03:43 [Q] INFO Enqueued 5
apr 07 09:03:43 ASM100 inventree-web-1.service[33824]: 07:03:43 [Q] INFO Enqueued 6
apr 07 09:03:43 ASM100 inventree-web-1.service[33853]: 07:03:43 [Q] INFO Enqueued 7
apr 07 09:03:43 ASM100 inventree-web-1.service[33822]: 07:03:43 [Q] INFO Enqueued 8
apr 07 09:03:43 ASM100 inventree-web-1.service[33828]: 07:03:43 [Q] INFO Enqueued 9
apr 07 09:03:43 ASM100 inventree-web-1.service[33820]: 07:03:43 [Q] INFO Enqueued 10
apr 07 09:03:43 ASM100 inventree-web-1.service[33854]: 07:03:43 [Q] INFO Enqueued 11
apr 07 09:39:04 ASM100 inventree-web-1.service[33822]: 127.0.0.1 - - [07/Apr/2023:07:39:04 +0000] "GET / HTTP/1.0" 302 0 "-" "Moz>
apr 07 09:39:04 ASM100 inventree-web-1.service[33822]: 07:39:04 [Q] INFO Enqueued 42
apr 07 09:39:04 ASM100 inventree-web-1.service[33822]: 07:39:04 [Q] INFO Enqueued 43
apr 07 09:39:04 ASM100 inventree-web-1.service[33822]: 07:39:04 [Q] INFO Enqueued 44
apr 07 09:39:04 ASM100 inventree-web-1.service[33822]: 07:39:04 [Q] INFO Enqueued 45
apr 07 09:39:04 ASM100 inventree-web-1.service[33822]: 127.0.0.1 - - [07/Apr/2023:07:39:04 +0000] "GET /accounts/login/?next=/ HT>
apr 07 09:39:22 ASM100 inventree-web-1.service[33824]: 127.0.0.1 - - [07/Apr/2023:07:39:22 +0000] "POST /accounts/login/ HTTP/1.0>
apr 07 09:39:35 ASM100 inventree-web-1.service[33820]: 127.0.0.1 - - [07/Apr/2023:07:39:35 +0000] "POST /accounts/login/ HTTP/1.0>
apr 07 09:49:38 ASM100 inventree-web-1.service[33820]: 127.0.0.1 - - [07/Apr/2023:07:49:38 +0000] "POST /accounts/login/ HTTP/1.0>
apr 07 09:49:48 ASM100 inventree-web-1.service[33832]: 127.0.0.1 - - [07/Apr/2023:07:49:48 +0000] "POST /accounts/login/ HTTP/1.0>
apr 07 09:49:56 ASM100 inventree-web-1.service[33832]: 127.0.0.1 - - [07/Apr/2023:07:49:56 +0000] "POST /accounts/login/ HTTP/1.0>
apr 07 09:50:47 ASM100 inventree-web-1.service[33822]: 127.0.0.1 - - [07/Apr/2023:07:50:47 +0000] "POST /accounts/login/ HTTP/1.0>
apr 07 09:50:47 ASM100 inventree-web-1.service[33824]: 127.0.0.1 - - [07/Apr/2023:07:50:47 +0000] "GET / HTTP/1.0" 302 0 "http://>
apr 07 09:50:47 ASM100 inventree-web-1.service[33853]: 07:50:47 [Q] INFO Enqueued 48
apr 07 09:50:47 ASM100 inventree-web-1.service[33853]: 07:50:47 [Q] INFO Enqueued 49
apr 07 09:50:47 ASM100 inventree-web-1.service[33853]: 07:50:47 [Q] INFO Enqueued 50
apr 07 09:50:47 ASM100 inventree-web-1.service[33853]: 07:50:47 [Q] INFO Enqueued 51
apr 07 09:50:47 ASM100 inventree-web-1.service[33853]: 07:50:47 [Q] INFO Enqueued 52
apr 07 09:50:47 ASM100 inventree-web-1.service[33853]: 07:50:47 [Q] INFO Enqueued 53
apr 07 09:50:47 ASM100 inventree-web-1.service[33853]: 07:50:47 [Q] INFO Enqueued 54

mabroens · 2024-05-23T13:42:09Z

here's my config.yaml content

cat /etc/inventree/config.yaml

# Secret key for backend
# Use the environment variable INVENTREE_SECRET_KEY_FILE
#secret_key_file: '/etc/inventree/secret_key.txt'

# Database backend selection - Configure backend database settings
# Documentation: https://docs.inventree.org/en/latest/start/config/

# Note: Database configuration options can also be specified from environmental variables,
#       with the prefix INVENTREE_DB_
#       e.g INVENTREE_DB_NAME / INVENTREE_DB_USER / INVENTREE_DB_PASSWORD
database:
  # Uncomment (and edit) one of the database configurations below,
  # or specify database options using environment variables

  # Refer to the django documentation for full list of options

  # --- Available options: ---
  # ENGINE: Database engine. Selection from:
  #         - mysql
  #         - postgresql
  #         - sqlite3
  # NAME: Database name
  # USER: Database username (if required)
  # PASSWORD: Database password (if required)
  # HOST: Database host address (if required)
  # PORT: Database host port (if required)

  # --- Database settings ---
  #ENGINE: sampleengine
  #NAME: '/path/to/database'
  #USER: sampleuser
  #PASSWORD: samplepassword
  #HOST: samplehost
  #PORT: 123456

  # --- Example Configuration - MySQL ---
  #ENGINE: mysql
  #NAME: inventree
  #USER: inventree
  #PASSWORD: inventree_password
  #HOST: 'localhost'
  #PORT: '3306'

  # --- Example Configuration - Postgresql ---
  #ENGINE: postgresql
  #NAME: inventree
  #USER: inventree
  #PASSWORD: inventree_password
  #HOST: 'localhost'
  #PORT: '5432'

  # --- Example Configuration - sqlite3 ---
  # ENGINE: sqlite3
  # NAME: '/home/inventree/database.sqlite3'

# Set debug to False to run in production mode
# Use the environment variable INVENTREE_DEBUG
debug: True

# Set to False to disable the admin interface (default = True)
# Or, use the environment variable INVENTREE_ADMIN_ENABLED
#admin_enabled: True

# Set the admin URL (default is 'admin')
# Or, use the environment variable INVENTREE_ADMIN_URL
#admin_url: 'admin'

# Configure the system logging level
# Use environment variable INVENTREE_LOG_LEVEL
# Options: DEBUG / INFO / WARNING / ERROR / CRITICAL
log_level: WARNING

# Enable database-level logging
# Use the environment variable INVENTREE_DB_LOGGING
db_logging: False

# Select default system language (default is 'en-us')
# Use the environment variable INVENTREE_LANGUAGE
language: en-us

# System time-zone (default is UTC)
# Reference: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
timezone: UTC

# Base URL for the InvenTree server
# Use the environment variable INVENTREE_SITE_URL
site_url: 'http://localhost:8000'

# Base currency code (or use env var INVENTREE_BASE_CURRENCY)
base_currency: USD

# Add new user on first startup by either adding values here or from a file
#admin_user: admin
#admin_email: info@example.com
#admin_password: inventree
#admin_password_file: '/etc/inventree/admin_password.txt'

# List of currencies supported by default. Add other currencies here to allow use in InvenTree
currencies:
  - AUD
  - CAD
  - CNY
  - EUR
  - GBP
  - JPY
  - NZD
  - USD

# Email backend configuration
# Ref: https://docs.djangoproject.com/en/dev/topics/email/
# Alternatively, these options can all be set using environment variables,
# with the INVENTREE_EMAIL_ prefix:
# e.g. INVENTREE_EMAIL_HOST / INVENTREE_EMAIL_PORT / INVENTREE_EMAIL_USERNAME
# Refer to the InvenTree documentation for more information

email:
  # backend: 'django.core.mail.backends.smtp.EmailBackend'
  host: ''
  port: 25
  username: ''
  password: ''
  sender: ''
  tls: False
  ssl: False

# Set sentry_enabled to True to report errors back to the maintainers
# Set sentry,dsn to your custom DSN if you want to use your own instance for error reporting
sentry_enabled: False
#sentry_sample_rate: 0.1
#sentry_dsn: https://custom@custom.ingest.sentry.io/custom

# OpenTelemetry tracing/metrics - disabled by default
# This can be used to send tracing data, logs and metrics to OpenTelemtry compatible backends
# See https://opentelemetry.io/ecosystem/vendors/ for a list of supported backends
# Alternatively, use environment variables eg. INVENTREE_TRACING_ENABLED, INVENTREE_TRACING_HEADERS, INVENTREE_TRACING_AUTH
#tracing:
#  enabled: true
#  endpoint: https://otlp-gateway-prod-eu-west-0.grafana.net/otlp
#  headers:
#    api-key: 'sample'
#  auth:
#    basic:
#      username: '******'
#      password: 'glc_****'
#  is_http: true
#  append_http: true
#  console: false
#  resources:
#    CUSTOM_KEY: 'CUSTOM_VALUE'

# Set this variable to True to enable InvenTree Plugins
# Alternatively, use the environment variable INVENTREE_PLUGINS_ENABLED
plugins_enabled: False
#plugin_noinstall: True
#plugin_file: '/path/to/plugins.txt'
#plugin_dir: '/path/to/plugins/'

# Set this variable to True to enable auto-migrations
# Alternatively, use the environment variable INVENTREE_AUTO_UPDATE
auto_update: False

# Allowed hosts (see ALLOWED_HOSTS in Django settings documentation)
# A list of strings representing the host/domain names that this Django site can serve.
# Default behaviour is to allow all hosts (THIS IS NOT SECURE!)
allowed_hosts:
  - '*'

# Trusted origins (see CSRF_TRUSTED_ORIGINS in Django settings documentation)
# If you are running behind a proxy, you may need to add the proxy address here
# trusted_origins:
#   - 'http://localhost'
#   - 'http://*.localhost'

# Proxy forwarding settings
# If InvenTree is running behind a proxy, you may need to configure these settings

# Override with the environment variable INVENTREE_USE_X_FORWARDED_HOST
use_x_forwarded_host: false

# Override with the environment variable INVENTREE_USE_X_FORWARDED_PORT
use_x_forwarded_port: false

# Cookie settings
cookie:
  secure: false
  samesite: none

# Cross Origin Resource Sharing (CORS) settings (see https://github.com/adamchainz/django-cors-headers)
cors:
  allow_all: true
  allow_credentials: true

  # whitelist:
  # - https://example.com
  # - https://sub.example.com

  # regex:

# MEDIA_ROOT is the local filesystem location for storing uploaded files
#media_root: '/home/inventree/data/media'

# STATIC_ROOT is the local filesystem location for storing static files
#static_root: '/home/inventree/data/static'

# INVENTREE_BACKUP_DIR is the local filesystem location for storing backups
#backup_dir: '/home/inventree/data/backup'

# Background worker options
background:
  workers: 4
  timeout: 90
  max_attempts: 5

# Login configuration
login_confirm_days: 3
login_attempts: 5
login_default_protocol: http

# Remote / proxy login
# These settings can introduce security problems if configured incorrectly. Please read
# https://docs.djangoproject.com/en/4.2/howto/auth-remote-user/ for more details
# The header name should be prefixed by `HTTP`. Please read the docs for more details
# https://docs.djangoproject.com/en/stable/ref/request-response/#django.http.HttpRequest.META
remote_login_enabled: False
remote_login_header: HTTP_REMOTE_USER

# JWT tokens
# JWT can be used optionally to authenticate users. Turned off by default.
# Alternatively, use the environment variable INVENTREE_USE_JWT
# use_jwt: True

# Logout redirect configuration
# This setting may be required if using remote / proxy login to redirect requests
# during the logout process (default is 'index'). Please read the docs for more details
# https://docs.djangoproject.com/en/stable/ref/settings/#logout-redirect-url
#logout_redirect_url: 'index'

# Add SSO login-backends (see examples below)
# social_backends:
#  - 'allauth.socialaccount.providers.google'
#  - 'allauth.socialaccount.providers.github'

# Add specific settings for social account providers (if required)
# Refer to the djngo-allauth documentation for more details:
# https://docs.allauth.org/en/latest/socialaccount/provider_configuration.html
# social_providers:
#   github:
#     VERIFIED_EMAIL: true

# Add LDAP support
# ldap:
#   enabled: false
#   debug: false  # enable debug mode to troubleshoot ldap configuration
#   server_uri: ldaps://example.org
#   bind_dn: cn=admin,dc=example,dc=org
#   bind_password: admin_password
#   search_base_dn: cn=Users,dc=example,dc=org

#   # enable TLS encryption over the standard LDAP port,
#   # see: https://django-auth-ldap.readthedocs.io/en/latest/reference.html#auth-ldap-start-tls
#   # start_tls: false

#   # uncomment if you want to use direct bind, bind_dn and bin_password is not necessary then
#   # user_dn_template: "uid=%(user)s,dc=example,dc=org"

#   # uncomment to set advanced global options, see https://www.python-ldap.org/en/latest/reference/ldap.html#ldap-options
#   # for all available options (keys and values starting with OPT_ get automatically converted to python-ldap keys)
#   # global_options:
#   #   OPT_X_TLS_REQUIRE_CERT: OPT_X_TLS_NEVER
#   #   OPT_X_TLS_CACERTFILE: /opt/inventree/ldapca.pem

#   # uncomment for advanced filter search, default: uid=%(user)s
#   # search_filter_str:

#   # uncomment for advanced user attribute mapping (in the format <InvenTree attribute>: <LDAP attribute>)
#   # user_attr_map:
#   #   first_name: givenName
#   #   last_name: sn
#   #   email: mail

#   # always update the user on each login, default: true
#   # always_update_user: true

#   # cache timeout to reduce traffic with LDAP server, default: 3600 (1h)
#   # cache_timeout: 3600

#   # LDAP group support
#   # group_search: ou=groups,dc=example,dc=com
#   # require_group: cn=inventree_allow,ou=groups,dc=example,dc=com
#   # deny_group: cn=inventree_deny,ou=groups,dc=example,dc=com
#   # Set staff/superuser flag based on LDAP group membership
#   # user_flags_by_group:
#   #   is_staff: cn=inventree_staff,ou=groups,dc=example,dc=com
#   #   is_superuser: cn=inventree_superuser,ou=groups,dc=example,dc=com

# Customization options
# Add custom messages to the login page or main interface navbar or exchange the logo
# Use environment variable INVENTREE_CUSTOMIZE or INVENTREE_CUSTOM_LOGO
# Logo and splash paths and filenames must be relative to the static_root directory
# customize:
#   login_message: InvenTree demo instance - <a href='https://inventree.org/demo.html'> Click here for login details</a>
#   navbar_message: <h6>InvenTree demo mode <a href='https://inventree.org/demo.html'><span class='fas fa-info-circle'></span></a></h6>
#   hide_admin_link: true
#   hide_password_reset: true
#   logo: img/custom_logo.png
#   splash: img/custom_splash.jpg
#   hide_pui_banner: true

# Set enabled frontends
# Use the environment variable INVENTREE_CLASSIC_FRONTEND
# classic_frontend: True
# Use the environment variable INVENTREE_PLATFORM_FRONTEND
# platform_frontend: True

SchrodingersGat · 2024-05-23T13:42:30Z

@mabroens ok, so looks like the web server is actually functioning at least.

Next we should look at the nginx logs. Grab the name of the nginx process with:

systemctl list-units --type=service --state=running

(let's say it's nginx.service)

Then run:

systemctl status nginx.service

journalctl -u nginx.service

mabroens · 2024-05-23T13:45:15Z

root@ASM100:~# systemctl list-units --type=service --state=running
UNIT LOAD ACTIVE SUB DESCRIPTION
accounts-daemon.service loaded active running Accounts Service
acpid.service loaded active running ACPI event daemon
avahi-daemon.service loaded active running Avahi mDNS/DNS-SD Stack
bluetooth.service loaded active running Bluetooth service
colord.service loaded active running Manage, Install and Generate Color Profiles
cron.service loaded active running Regular background program processing daemon
cups-browsed.service loaded active running Make remote CUPS printers available locally
cups.service loaded active running CUPS Scheduler
dbus.service loaded active running D-Bus System Message Bus
gdm.service loaded active running GNOME Display Manager
inventree-web.service loaded active running inventree-web.service
inventree-worker.service loaded active running inventree-worker.service
inventree.service loaded active running inventree.service
irqbalance.service loaded active running irqbalance daemon
kerneloops.service loaded active running Tool to automatically collect and submit kernel crash signatures
ModemManager.service loaded active running Modem Manager
NetworkManager.service loaded active running Network Manager
nginx.service loaded active running A high performance web server and a reverse proxy server
packagekit.service loaded active running PackageKit Daemon
polkit.service loaded active running Authorization Manager
power-profiles-daemon.service loaded active running Power Profiles daemon
rsyslog.service loaded active running System Logging Service
rtkit-daemon.service loaded active running RealtimeKit Scheduling Policy Service
snapd.service loaded active running Snap Daemon
ssh.service loaded active running OpenBSD Secure Shell server
switcheroo-control.service loaded active running Switcheroo Control Proxy service
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running User Login Management
systemd-oomd.service loaded active running Userspace Out-Of-Memory (OOM) Killer
systemd-resolved.service loaded active running Network Name Resolution
systemd-timesyncd.service loaded active running Network Time Synchronization
systemd-udevd.service loaded active running Rule-based Manager for Device Events and Files
teamviewerd.service loaded active running TeamViewer remote control daemon
thermald.service loaded active running Thermal Daemon Service
udisks2.service loaded active running Disk Manager
unattended-upgrades.service loaded active running Unattended Upgrades Shutdown
upower.service loaded active running Daemon for power management
user@1000.service loaded active running User Manager for UID 1000
user@129.service loaded active running User Manager for UID 129
wpa_supplicant.service loaded active running WPA supplicant

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
40 loaded units listed.
root@ASM100:~# systemctl status nginx.service
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2024-05-20 11:40:17 CEST; 3 days ago
Docs: man:nginx(8)
Main PID: 5948 (nginx)
Tasks: 5 (limit: 9374)
Memory: 5.0M
CPU: 45ms
CGroup: /system.slice/nginx.service
├─5948 "nginx: master process /usr/sbin/nginx -g daemon on; master_process on;"
├─5949 "nginx: worker process" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ""
├─5950 "nginx: worker process" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ""
├─5951 "nginx: worker process" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ""
└─5952 "nginx: worker process" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ""

mei 20 11:40:17 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
mei 20 11:40:17 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.
root@ASM100:~# journalctl -u nginx.service
apr 07 09:01:45 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
apr 07 09:01:45 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.
apr 07 09:01:52 ASM100 systemd[1]: Stopping A high performance web server and a reverse proxy server...
apr 07 09:01:52 ASM100 systemd[1]: nginx.service: Succeeded.
apr 07 09:01:52 ASM100 systemd[1]: Stopped A high performance web server and a reverse proxy server.
apr 07 09:01:52 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
apr 07 09:01:52 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.
apr 07 11:19:53 ASM100 systemd[1]: Stopping A high performance web server and a reverse proxy server...
apr 07 11:19:53 ASM100 systemd[1]: nginx.service: Succeeded.
apr 07 11:19:53 ASM100 systemd[1]: Stopped A high performance web server and a reverse proxy server.
-- Boot 4cdb840733a44a46b3bf77d9a5660e6a --
apr 07 11:21:43 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
apr 07 11:21:43 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.
-- Boot a4182342d06741639bd0399a8fccd718 --
apr 08 17:23:07 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
apr 08 17:23:07 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.
apr 11 11:20:57 ASM100 systemd[1]: Stopping A high performance web server and a reverse proxy server...
apr 11 11:20:57 ASM100 systemd[1]: nginx.service: Succeeded.
apr 11 11:20:57 ASM100 systemd[1]: Stopped A high performance web server and a reverse proxy server.
-- Boot fb9d67b5870b41f7b800ef5ea7d4de02 --
apr 11 11:22:47 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
apr 11 11:22:47 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.
apr 14 15:13:56 ASM100 systemd[1]: Stopping A high performance web server and a reverse proxy server...
apr 14 15:13:56 ASM100 systemd[1]: nginx.service: Succeeded.
apr 14 15:13:56 ASM100 systemd[1]: Stopped A high performance web server and a reverse proxy server.
-- Boot a0f841430eed4f11925545a38f85e711 --
apr 14 15:15:45 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
apr 14 15:15:45 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.
-- Boot 2fe6ed1fb44f4cb7a4ad3f1042588359 --
apr 15 11:03:05 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
apr 15 11:03:05 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.
apr 16 12:34:34 ASM100 systemd[1]: Stopping A high performance web server and a reverse proxy server...
apr 16 12:34:34 ASM100 systemd[1]: nginx.service: Succeeded.
apr 16 12:34:34 ASM100 systemd[1]: Stopped A high performance web server and a reverse proxy server.
-- Boot 023cc5bbe89f4dcfa8f617e748688391 --
apr 16 12:36:23 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
apr 16 12:36:24 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.
apr 16 17:50:24 ASM100 systemd[1]: Stopping A high performance web server and a reverse proxy server...
apr 16 17:50:24 ASM100 systemd[1]: nginx.service: Succeeded.
apr 16 17:50:24 ASM100 systemd[1]: Stopped A high performance web server and a reverse proxy server.
-- Boot 6c6f13afd7464c9ea54144019a7c51d1 --
apr 16 17:50:43 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
apr 16 17:50:43 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.
apr 21 07:52:08 ASM100 systemd[1]: Stopping A high performance web server and a reverse proxy server...
apr 21 07:52:13 ASM100 systemd[1]: nginx.service: Succeeded.
apr 21 07:52:13 ASM100 systemd[1]: Stopped A high performance web server and a reverse proxy server.
-- Boot ae64959fb3e04579a2e6fdeb919f0cbb --
apr 21 07:52:27 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
apr 21 07:52:27 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.
apr 24 11:20:35 ASM100 systemd[1]: Stopping A high performance web server and a reverse proxy server...
apr 24 11:20:35 ASM100 systemd[1]: nginx.service: Succeeded.
apr 24 11:20:35 ASM100 systemd[1]: Stopped A high performance web server and a reverse proxy server.
-- Boot 19a37b65b232499ca50bfc8bb0d092c7 --
apr 24 11:20:54 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...

asscherhofstede · 2024-05-23T14:54:18Z

maybe there is a another ngix running on port you wanna use.
you can check with: sudo lsof -i:{hereyourport}

im on port 80
and this is my output

COMMAND PID     USER   FD   TYPE     DEVICE SIZE/OFF NODE NAME
nginx   298     root    6u  IPv4 2433896175      0t0  TCP *:http (LISTEN)
nginx   299 www-data    6u  IPv4 2433896175      0t0  TCP *:http (LISTEN)
nginx   300 www-data    6u  IPv4 2433896175      0t0  TCP *:http (LISTEN)
nginx   301 www-data    6u  IPv4 2433896175      0t0  TCP *:http (LISTEN)
nginx   302 www-data    6u  IPv4 2433896175      0t0  TCP *:http (LISTEN)

im comparing my systemctl status nginx.service output with yours but im missing the processes part between docs and main PID.

● nginx.service - A high performance web server and a reverse proxy server
     Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2024-05-21 09:21:30 CEST; 2 days ago
       Docs: man:nginx(8)
    Process: 291 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
    Process: 297 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
   Main PID: 298 (nginx)
     CGroup: /system.slice/nginx.service
             ├─298 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
             ├─299 nginx: worker process
             ├─300 nginx: worker process
             ├─301 nginx: worker process
             └─302 nginx: worker process

mei 21 09:12:18 server systemd[1]: Stopping A high performance web server and a reverse proxy server...
mei 21 09:12:18 server systemd[1]: nginx.service: Succeeded.
mei 21 09:12:18 server systemd[1]: Stopped A high performance web server and a reverse proxy server.
mei 21 09:12:18 server systemd[1]: Starting A high performance web server and a reverse proxy server...
mei 21 09:12:18 server systemd[1]: Started A high performance web server and a reverse proxy server.
mei 21 09:19:03 server systemd[1]: Stopping A high performance web server and a reverse proxy server...
mei 21 09:19:03 server systemd[1]: nginx.service: Succeeded.

mabroens · 2024-05-23T15:15:25Z

this is what i get when excuting these 2 commands

root@ASM100:~# systemctl status nginx.service
● nginx.service - A high performance web server and a reverse proxy server
     Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2024-05-20 11:40:17 CEST; 3 days ago
       Docs: man:nginx(8)
   Main PID: 5948 (nginx)
      Tasks: 5 (limit: 9374)
     Memory: 5.0M
        CPU: 49ms
     CGroup: /system.slice/nginx.service
             ├─5948 "nginx: master process /usr/sbin/nginx -g daemon on; master_process on;"
             ├─5949 "nginx: worker process" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ""
             ├─5950 "nginx: worker process" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ""
             ├─5951 "nginx: worker process" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ""
             └─5952 "nginx: worker process" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ""

mei 20 11:40:17 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
mei 20 11:40:17 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.

root@ASM100:~# sudo lsof -i:80
COMMAND  PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
nginx   5948     root    6u  IPv4  71664      0t0  TCP *:http (LISTEN)
nginx   5949 www-data    6u  IPv4  71664      0t0  TCP *:http (LISTEN)
nginx   5950 www-data    6u  IPv4  71664      0t0  TCP *:http (LISTEN)
nginx   5951 www-data    6u  IPv4  71664      0t0  TCP *:http (LISTEN)
nginx   5952 www-data    6u  IPv4  71664      0t0  TCP *:http (LISTEN)

mabroens · 2024-05-25T15:56:35Z

I have Inventree working again on my ubuntu 22.04 baremetal.

together with @asscherhofstede we had a debug session and found that installing on a new machine (Manual Install ) the out of the box was also not working.
also there we had to uncomment line 88 as stated above.

next i tried copying my files from the 'broken machine' o the new ubuntu 20. i.e.
copied /opt/inventree/data that broke it again.

eventually i compared /etc/inventree/config.yaml between the 2 machines and found that on the 'broken' machine all path settings where modified after the update.

correcting this than it worked on both machines.

so up and running again.
Thanx guys for the support

mabroens · 2024-05-25T15:58:06Z

next step now is to relocate my db and other relevant files to an external machine like dropbox or NAS.
and then remove Inventree from the machine and reisntall ubuntu and inventree again to have a clean machine.

Br Martijn

SchrodingersGat · 2024-05-26T10:33:25Z

Ref: #7336

SchrodingersGat · 2024-05-26T10:41:41Z

@mabroens ok thank you for prodiving that extra information. We can use that to work out our fix for the installer.

(@matmair )

mabroens · 2024-05-26T10:46:01Z

Additionally after i got it working i got the notification:

so i did:
sudo systemctl stop inventree next sudo inventree run invoke update and finally sudo systemctl start inventree
but after migration it mentioned:

InvenTree database migrations completed!
Updating frontend...
Downloading frontend...
fatal: not a git repository (or any of the parent directories): .git
[ERROR] Cannot get current ref via 'git rev-parse HEAD'

even thought this reporting it all seems to be working.

Br Martijn

SchrodingersGat · 2024-05-26T10:52:52Z

@mabroens thanks for adding in that additional detail, I'll make a note of it.

matmair · 2024-05-27T17:56:46Z

Seems like the original issue was resolved - can we close this @mabroens?

mabroens · 2024-05-27T18:00:51Z

yes we can thank you

mabroens added question This is a question setup Relates to the InvenTree setup / installation process triage:not-checked Item was not checked by the core team labels May 16, 2024

SchrodingersGat removed the triage:not-checked Item was not checked by the core team label May 16, 2024

SchrodingersGat added the installer label May 20, 2024

SchrodingersGat mentioned this issue May 22, 2024

502 bad gateway #7304

Closed

6 tasks

SchrodingersGat mentioned this issue May 24, 2024

Bare metal installation using quick script is not working #7323

Closed

6 tasks

SchrodingersGat mentioned this issue May 26, 2024

[Installer] Issue downloading frontend #7338

Open

mabroens closed this as completed May 27, 2024

matmair self-assigned this May 27, 2024

matmair added this to the 0.15.3 milestone May 27, 2024

matmair added bug Identifies a bug which needs to be addressed and removed question This is a question labels May 27, 2024

502 Bad Gateway after ubuntu 20 upgrade Inventree 0.15.1 #7246

502 Bad Gateway after ubuntu 20 upgrade Inventree 0.15.1 #7246

Comments

mabroens commented May 16, 2024

Deployment Method

Describe the problem*

Steps to Reproduce

Relevant log output

shapirus commented May 16, 2024

mabroens commented May 17, 2024

shapirus commented May 17, 2024 • edited

mabroens commented May 17, 2024

mabroens commented May 20, 2024

SchrodingersGat commented May 20, 2024

mabroens commented May 20, 2024

SchrodingersGat commented May 20, 2024

asscherhofstede commented May 21, 2024

asscherhofstede commented May 21, 2024 • edited

SchrodingersGat commented May 21, 2024

mabroens commented May 21, 2024

SchrodingersGat commented May 21, 2024

asscherhofstede commented May 21, 2024 • edited

mabroens commented May 21, 2024

asscherhofstede commented May 21, 2024

mabroens commented May 21, 2024

mabroens commented May 21, 2024

asscherhofstede commented May 22, 2024

mabroens commented May 22, 2024

asscherhofstede commented May 22, 2024

mabroens commented May 22, 2024

asscherhofstede commented May 22, 2024

mabroens commented May 22, 2024

asscherhofstede commented May 22, 2024

mabroens commented May 22, 2024

mabroens commented May 22, 2024

mabroens commented May 22, 2024

mabroens commented May 23, 2024

SchrodingersGat commented May 23, 2024

mabroens commented May 23, 2024

mabroens commented May 23, 2024

SchrodingersGat commented May 23, 2024 • edited

mabroens commented May 23, 2024

asscherhofstede commented May 23, 2024

mabroens commented May 23, 2024

mabroens commented May 25, 2024

mabroens commented May 25, 2024

SchrodingersGat commented May 26, 2024

SchrodingersGat commented May 26, 2024

mabroens commented May 26, 2024

SchrodingersGat commented May 26, 2024

matmair commented May 27, 2024

mabroens commented May 27, 2024

shapirus commented May 17, 2024 •

edited

asscherhofstede commented May 21, 2024 •

edited

asscherhofstede commented May 21, 2024 •

edited

SchrodingersGat commented May 23, 2024 •

edited