Some services fail to start (unexpected SIGKILL)

[JosXa]

First time trying out this HA plugin, and I'm seeing

s6-rc: info: service init-paperless successfully started
s6-rc: info: service paperless: starting
s6-rc: info: service paperless successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Paperless-ngx docker container starting...
Installing languages...
Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]
Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:4 http://deb.debian.org/debian bookworm/main amd64 Packages [8788 kB]
Get:5 http://deb.debian.org/debian bookworm-updates/main amd64 Packages [13.8 kB]
Get:6 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages [169 kB]
Fetched 9225 kB in 4s (2397 kB/s)
Reading package lists...
Package tesseract-ocr-eng already installed!
Package tesseract-ocr-deu already installed!
Creating directory scratch directory /tmp/paperless
Adjusting permissions of paperless files. This may take a while.
Waiting for Redis...
Connected to Redis broker.
Apply database migrations...
Operations to perform:
  Apply all migrations: account, admin, auditlog, auth, authtoken, contenttypes, django_celery_results, documents, guardian, paperless, paperless_mail, sessions, socialaccount
Running migrations:
  No migrations to apply.
Running Django checks
System check identified no issues (0 silenced).
Did not create superuser, a user josxa already exists
Executing /usr/local/bin/paperless_cmd.sh
2024-07-29 22:54:07,378 INFO Set uid to user 0 succeeded
2024-07-29 22:54:07,398 INFO supervisord started with pid 736
2024-07-29 22:54:08,403 INFO spawned: 'gunicorn' with pid 1312
2024-07-29 22:54:08,420 INFO spawned: 'gunicorn-ingress' with pid 1313
2024-07-29 22:54:08,439 INFO spawned: 'celery' with pid 1314
2024-07-29 22:54:08,443 INFO spawned: 'celery-beat' with pid 1315
2024-07-29 22:54:08,454 INFO spawned: 'consumer' with pid 1316
2024-07-29 22:54:08,472 INFO spawned: 'celery-flower' with pid 1317
Checking if we should start flower...
2024-07-29 22:54:08,571 INFO success: celery-flower entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
Not starting flower
2024-07-29 22:54:09,581 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-29 22:54:09,582 INFO success: gunicorn-ingress entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-29 22:54:09,583 INFO success: celery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-29 22:54:09,583 INFO success: celery-beat entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-29 22:54:09,584 INFO success: consumer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-29 22:54:09,585 INFO exited: celery-flower (exit status 0; expected)
[22:54:22] INFO: Starting NGinx....
celery beat v5.4.0 (opalescent) is starting.
2024-07-29 22:54:36,008 WARN exited: gunicorn-ingress (terminated by SIGKILL; not expected)
2024-07-29 22:54:36,091 INFO spawned: 'gunicorn-ingress' with pid 1534
2024-07-29 22:54:37,138 INFO success: gunicorn-ingress entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-29 22:54:53,349 WARN exited: gunicorn (terminated by SIGKILL; not expected)
2024-07-29 22:54:53,445 INFO spawned: 'gunicorn' with pid 1593
2024-07-29 22:54:54,492 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-29 22:55:00,472 WARN exited: consumer (terminated by SIGKILL; not expected)
2024-07-29 22:55:00,577 INFO spawned: 'consumer' with pid 1618
2024-07-29 22:55:01,630 INFO success: consumer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-29 22:55:22,132 WARN exited: celery (terminated by SIGKILL; not expected)
2024-07-29 22:55:23,146 INFO spawned: 'celery' with pid 1711
2024-07-29 22:55:24,163 INFO success: celery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-29 22:55:35,728 WARN exited: celery-beat (terminated by SIGKILL; not expected)
2024-07-29 22:55:35,876 INFO spawned: 'celery-beat' with pid 1738
2024-07-29 22:55:36,884 INFO success: celery-beat entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

gunicorn and celery appear to never come up properly and get caught in a failure loop. Is there any way to debug why they're failing? I have HA running in supervised mode on a VM.

My settings feel fairly standard:

[BenoitAnastay]

I never tested this add-on outside HA OS it's maybe an OS dependent error, there's also some updates I haven't released yet, I'll check if everything works well and push a new release

[BenoitAnastay]

Can you give futher information about your environnement ? OS version, supervisor installation method, anything you may think is relevent, please

[JosXa]

Alright so I'm running the thing on an Ubuntu machine within VirtualBox and also using the HA operating system install. Version is 2.05 with these HA versions:

Core
2024.1.1
Supervisor
2024.08.0
Operating System
11.5
Frontend
20240104.0

[JosXa]

Oh, looking at the VirtualBox logs I'm actually seeing OOM errors. Let me see if I can assign some more and report back

[JosXa]

Yup, that was it. 2GB were getting tight ;) Sorry about that!