Former images broken?

[CWollinger]

Issue Summary
Unable to start former docker images

Environment

• OS: Linux

• API version: 8.5.0

• Deployment: Docker

• For self-hosted, WSGI environment: nginx/uwsgi

• Database: Postgres

To Reproduce
Start docker-compose example with version 8.5.0

version: '2.1'
services:
  web:
    image: alerta/alerta-web:8.5.0
    ports:
      - "3000:8080"
    depends_on:
      - db
    environment:
      - DEBUG=1  # remove this line to turn DEBUG off
      - DATABASE_URL=postgres://postgres:postgres@db:5432/monitoring
      - AUTH_REQUIRED=True
      - ADMIN_USERS=admin@alerta.io,devops@alerta.io #default password: alerta
      - ADMIN_KEY=demo-key
      - PLUGINS=reject,blackout,normalise,enhance
    restart: always
  db:
    image: postgres
    volumes:
      - ./pg-data:/var/lib/postgresql/data
    environment:
      POSTGRES_DB: monitoring
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: postgres
    restart: always

Expected behavior
Alerta works like before

Additional context
Problem with uwsgi:

thunder lock: disabled (you can enable it with --thunder-lock)

2021-12-03 13:04:22,277 DEBG 'uwsgi' stdout output:
Listen queue size is greater than the system max net.core.somaxconn (128).

2021-12-03 13:04:22,277 DEBG fd 13 closed, stopped monitoring <POutputDispatcher at 140253855731440 for <Subprocess at 140253855851080 with name uwsgi in state STARTING> (stdout)>
2021-12-03 13:04:22,277 INFO exited: uwsgi (exit status 1; not expected)
2021-12-03 13:04:22,277 DEBG received SIGCLD indicating a child quit

[satterly]

I just tried 8.5.0 and it worked for me. The error you are seeing was introduced in #309 and in version 8.6.2. It was fixed in #344 and in version 8.6.4. I have no idea why you are seeing it in your setup. Are you sure you aren't setting uWSGI listen to something above "128"?

[CWollinger]

Using the docker-compose file from above. Without changing some configs in my setup.
I switched to the older 8.5.0 image (build 4 month ago) and it works.
Can you describe the changes in the image since then?

[satterly]

v8.5.0...v8.6.4

[CWollinger]

Tried with new version 8.6.4, too.
Problem only appears in combination with alertmanager. uwsgi crashes:

2021-12-07 07:33:22,209 DEBG 'uwsgi' stdout output:
worker 1 lifetime reached, it was running for 31 second(s)
worker 2 lifetime reached, it was running for 31 second(s)
worker 3 lifetime reached, it was running for 31 second(s)
worker 4 lifetime reached, it was running for 31 second(s)
worker 5 lifetime reached, it was running for 31 second(s)

[satterly]

That's a feature not a bug ...

docker-alerta/config/templates/app/uwsgi.ini.j2

Line 9 in bee0a4d

max-worker-lifetime = 30

See. https://uwsgi-docs.readthedocs.io/en/latest/Options.html#max-worker-lifetime

[CWollinger]

Hi Nick,

this was related to an own alerta plugin which was in conflict with the uwsgi master.
Thank you for the support, to lead my to the correct config location.

Regards
CWollinger