exit on any fatal after automatic restart at night (docker)

[ZoXx]

Debug mode

• [X] I have enabled debug mode
• [X] I have read checked the Common Issues page

Describe the bug

Good morning everyone,

I have unfortunately always the problem that the Docker (sometimes 2 times a week or sometimes 5 times a week) after the automatic restart by the backup is not restarted but has an error.

As soon as I restart the Docker via Portainer, it runs again without problems, until the next restart in the night.

Can someone help me here?

Reproduction steps

1. 2. 3. ...

Expected behavior

Fresh install and dev instance got the same problem by me

Screenshots

No response

Snipe-IT Version

6.1.2

Operating System

Docker

Web Server

-

PHP Version

8.1

Operating System

No response

Browser

No response

Version

No response

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

No scheduled commands are ready to run.
No scheduled commands are ready to run.
No scheduled commands are ready to run.
No scheduled commands are ready to run.
No scheduled commands are ready to run.
No scheduled commands are ready to run.
2023-07-31 01:04:33,847 WARN received SIGTERM indicating exit request
2023-07-31 01:04:33,853 INFO waiting for exit_on_any_fatal, run_schedule to die
2023-07-31 01:04:34,853 INFO stopped: run_schedule (terminated by SIGTERM)
2023-07-31 01:04:34,855 INFO stopped: exit_on_any_fatal (terminated by SIGTERM)
Module ssl already disabled
Nothing to migrate.
Configuration cache cleared!
Configuration cache cleared!
Configuration cached successfully!
2023-07-31 01:14:45,233 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2023-07-31 01:14:45,246 INFO supervisord started with pid 1
2023-07-31 01:14:46,280 INFO spawned: 'exit_on_any_fatal' with pid 37
2023-07-31 01:14:46,336 INFO spawned: 'apache' with pid 38
2023-07-31 01:14:46,408 INFO spawned: 'run_schedule' with pid 39
2023-07-31 01:14:47,481 INFO success: exit_on_any_fatal entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-31 01:14:47,481 INFO success: apache entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-31 01:14:47,481 INFO success: run_schedule entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using fd17::242:ac11:16. Set the 'ServerName' directive globally to suppress this message
httpd (pid 41) already running
2023-07-31 01:14:49,306 INFO exited: apache (exit status 0; expected)
No scheduled commands are ready to run.
[2023-07-31T03:15:56+02:00] Running scheduled command: '/usr/bin/php8.1' 'artisan' auth:clear-resets > '/dev/null' 2>&1
No scheduled commands are ready to run.
No scheduled commands are ready to run.
No scheduled commands are ready to run.
No scheduled commands are ready to run.

Additional context

No response

[welcome[bot]]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

[snipe]

Hey @jerm - any insights here? This definitely seems like a docker issue, not a Snipe-IT issue, but I'm not sure.

@ZoXx - can you describe your environment a little better? Are you running Kubernetes, or...?

[ZoXx]

Hey @snipe, of course. i'll try to list everything.

It is a unraid system with which the docker are created and managed via portainer.

the rest of the docker containers (about 25) have no problems and run cleanly after the backup. Only the snipe-it docker makes such problems. it is also always the same error message. this I have now for just over 4 months and wanted to finally get to the bottom of the cause.

if it helps, I can also post the settings via portainer.

[snipe]

Thanks for the additional info. Which docker image are you using?

[ZoXx]

Thanks for the additional info. Which docker image are you using? snipe/snipe-it:latest

[snipe]

Thanks for the clarification :) (I ask because we've seen weird stuff from other, unofficial images, but it looks like you're using the real one, so that narrows things down a bit.)

[ZoXx]

No problem, if I can provide more information, please let me know. It would be great if we could find the bug to ensure a bug free docker.

[ZoXx]

Any news here?

[ZoXx]

still no news :(

[uberbrady]

Are there any other logs we can get here? I'm scratching my head on this one. Basically when process 1 (which is supervisord) quits, the container will shut down. We also have a setting where if apache quits, it will tell supervisord to quit. So maybe that's too...finicky?

When the 'restart after backup' thing fires, do you know if that's doing a docker restart? Or something else?

Sorry it's hard for us to track down, we just don't see this happening elsewhere so it's difficult to figure out what's going on.

[ZoXx]

Workaround since one month is a docker restart every morning at 07:00 oclock via script.