Container exiting on signal 7 termination

[spomata]

Regularly after 30-40 mins of being started the container will exit with this trace:

[2023-03-22 10:20:49,709] INFO in renderer: Finished futures [2023-03-22 11:04:43 +0100] [3] [INFO] Worker exiting (pid: 3) [2023-03-22 11:04:43 +0100] [1] [INFO] Handling signal: term [2023-03-22 11:04:43 +0100] [1] [WARNING] Worker with pid 3 was terminated due to signal 7 [2023-03-22 11:04:43 +0100] [1] [INFO] Shutting down: Master

I will try to run in docker to rule out any issue with podman but I thought I could open an issue in case this rang any bell.

[iFargle]

That's fun. Can you enable debug logs?

Seems like signal 7 is SIGBUS? Do you have SELinux or anything like that enabled?

I've only used this on Docker, I have very little experience with Podman outside of one-off containers.

[iFargle]

Also what architecture? I know some of the libraries I'm using here have at least some C++ code. I'm not sure what I've written could cause a memory issue, I'm not doing any direct memory manipulations.

[spomata]

Running with debug enabled, will keep you posted as soon as it crashes again. Architecture is plain amd64, the container is running on an Ubuntu 20.04 VPS somewhere in the cloud.

[spomata]

No extra debug unfortunately, nor in syslog, same output: [2023-03-22 17:02:58 +0100] [1] [INFO] Handling signal: term [2023-03-22 17:02:58 +0100] [3] [INFO] Worker exiting (pid: 3) [2023-03-22 17:02:59 +0100] [1] [WARNING] Worker with pid 3 was terminated due to signal 7 [2023-03-22 17:02:59 +0100] [1] [INFO] Shutting down: Master

I will try with docker and see if it's more stable.

[iFargle]

Any issues with Docker? I haven't seen mine crash yet but I'm on Docker.

[iFargle]

Let me know if you have any more issues!