Grist in Docker (rootless): Sudden "Server grist[25] got signal SIGTERM"

[Sieboldianus]

Describe the current behavior

I am running Grist in Docker (rootless) for about 2 months. Since a few days, at 4 am, I the Docker container receives a SIGTERM. I do not know from where, but it means that the Grist server shuts down and then immediately boots up again (without the Docker container restarting). Afterwards, nginx give a "502 Bad Gateway" when trying to connect to Grist.

grist     | 2024-09-17 16:33:06.902 - warn: Telemetry exceeded the maximum number of pending forwardEvent calls (25). Skipping forwarding of event siteMembership.
grist     | 2024-09-17 16:33:06.902 - warn: Telemetry exceeded the maximum number of pending forwardEvent calls (25). Skipping forwarding of event siteMembership.
grist     | 2024-09-17 16:33:06.902 - info: logMetrics siteMembership progress itemsProcesssed=15, itemsTotal=15, timeMs=10
grist     | 2024-09-17 16:33:07.055 - info: activity docCount=6, orgCount=1, orgInGoodStandingCount=1, userCount=17, userWithLoginCount=13
grist     | 2024-09-17 17:33:07.005 - info: activity docCount=6, orgCount=1, orgInGoodStandingCount=1, userCount=17, userWithLoginCount=13
grist     | 2024-09-17 18:33:06.941 - info: activity docCount=6, orgCount=1, orgInGoodStandingCount=1, userCount=17, userWithLoginCount=13
grist     | 2024-09-17 19:33:06.957 - info: activity docCount=6, orgCount=1, orgInGoodStandingCount=1, userCount=17, userWithLoginCount=13
grist     | 2024-09-17 20:33:06.950 - info: activity docCount=6, orgCount=1, orgInGoodStandingCount=1, userCount=17, userWithLoginCount=13
grist     | 2024-09-17 21:33:06.957 - info: activity docCount=6, orgCount=1, orgInGoodStandingCount=1, userCount=17, userWithLoginCount=13
grist     | 2024-09-17 22:33:06.958 - info: activity docCount=6, orgCount=1, orgInGoodStandingCount=1, userCount=17, userWithLoginCount=13
grist     | 2024-09-17 23:33:06.953 - info: activity docCount=6, orgCount=1, orgInGoodStandingCount=1, userCount=17, userWithLoginCount=13
grist     | 2024-09-18 00:33:06.955 - info: activity docCount=6, orgCount=1, orgInGoodStandingCount=1, userCount=17, userWithLoginCount=13
grist     | 2024-09-18 01:33:06.957 - info: activity docCount=6, orgCount=1, orgInGoodStandingCount=1, userCount=17, userWithLoginCount=13
grist     | 2024-09-18 02:33:06.964 - info: activity docCount=6, orgCount=1, orgInGoodStandingCount=1, userCount=17, userWithLoginCount=13
grist     | 2024-09-18 03:33:06.961 - info: activity docCount=6, orgCount=1, orgInGoodStandingCount=1, userCount=17, userWithLoginCount=13
grist     | 2024-09-18 04:01:33.384 - info: Server grist[25] got signal SIGTERM; cleaning up (2 handlers)
grist     | 2024-09-18 04:01:33.385 - info: UploadSet: cleaning up all 0 uploads in set
grist     | Running Grist as user 1001 with primary group 1001
grist     | 2024-09-18 04:01:56.911 - info: Loading config file from /persist/config.json
grist     | Welcome to Grist.
grist     | In quiet mode, see http://localhost:8080 to use.
grist     | For full logs, re-run with DEBUG=1
grist     | Setting up database...
grist     | Database setup complete.
grist     | 2024-09-18 04:01:58.805 - info: == Grist version is 1.1.18 (commit unknown)
grist     | 2024-09-18 04:01:58.810 - debug: skipping incomplete language ar (set GRIST_OFFER_ALL_LANGUAGES if you want it)
grist     | 2024-09-18 04:01:58.816 - debug: skipping incomplete language ca (set GRIST_OFFER_ALL_LANGUAGES if you want it)
grist     | 2024-09-18 04:01:58.817 - debug: skipping incomplete language cs (set GRIST_OFFER_ALL_LANGUAGES if you want it)
grist     | 2024-09-18 04:01:58.828 - debug: skipping incomplete language fa (set GRIST_OFFER_ALL_LANGUAGES if you want it)
grist     | 2024-09-18 04:01:58.838 - debug: skipping incomplete language nl (set GRIST_OFFER_ALL_LANGUAGES if you want it)
grist     | 2024-09-18 04:01:58.856 - debug: skipping incomplete language th (set GRIST_OFFER_ALL_LANGUAGES if you want it)
grist     | 2024-09-18 04:01:58.856 - debug: skipping incomplete language tr (set GRIST_OFFER_ALL_LANGUAGES if you want it)
grist     | OPError: expected 200 OK, got: 502 Bad Gateway
grist     |     at processResponse (/grist/node_modules/openid-client/lib/helpers/process_response.js:41:11)
grist     |     at Issuer.discover (/grist/node_modules/openid-client/lib/issuer.js:179:18)
grist     |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
grist     |     at async OIDCConfig._initClient (/grist/_build/app/server/lib/OIDCConfig.js:245:24)
grist     |     at async OIDCConfig.initOIDC (/grist/_build/app/server/lib/OIDCConfig.js:155:9)
grist     |     at async OIDCConfig.build (/grist/_build/app/server/lib/OIDCConfig.js:104:9)
grist     |     at async Object.getMiddleware (/grist/_build/app/server/lib/OIDCConfig.js:329:28)
grist     |     at async FlexServer.addLoginMiddleware (/grist/_build/app/server/lib/FlexServer.js:1078:33)
grist     |     at async main (/grist/_build/app/server/mergedServerMain.js:86:5)
grist     |     at async main (/grist/_build/stubs/app/server/server.js:142:20) {
grist     |   error: 'expected 200 OK, got: 502 Bad Gateway'
grist     | }

Steps to reproduce

At the moment, I do not know why there is a SIGTERM.

Describe the expected behavior

Grist keeps running.

Where have you encountered this bug?

• On docs.getgrist.com
• On a self-hosted instance

Instance information (when self-hosting only)

• Grist instance:

  • Version: Version 1.1.18
  • Installation mode: docker rootless on Ubuntu 22.04.5 LTS
  • Architecture: single-worker

• Browser name, version and platforms on which you could reproduce the bug: Firefox

• Link to server log if relevant: in comments above