Closed siperwrx closed 1 year ago
@siperwrx, the SIGTERM signal is a generic signal used to cause program termination. Something must be stopping the container. Are there any other logs anywhere?
No, that's all I could find.
On Wed, Jan 18, 2023 at 9:44 PM realies @.***> wrote:
@siperwrx https://github.com/siperwrx, the SIGTERM signal is a generic signal used to cause program termination. Something must be stopping the container. Are there any other logs anywhere?
— Reply to this email directly, view it on GitHub https://github.com/realies/soulseek-docker/issues/64#issuecomment-1396468277, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADGEREBAUSY3GPDTEADZHMLWTDIE5ANCNFSM6AAAAAAT7PAG6Q . You are receiving this because you were mentioned.Message ID: @.***>
I would need more to be able to make any assumptions.
Hi there, I'm running Soulseek in Docker on my Synology and every day or so, I get the following error message: Docker container soulseek stopped unexpectedly. Go to Docker for more information.
In the container log, I see this: INFO stopped: soulseek (terminated by SIGTERM)
Any ideas how to prevent this?