[BUG] Docker stops after a day, cannot be started

[clucraft]

I've tried deploying this docker multiple times, each time the docker container runs fine and performs as expected with the services enabled, but after a day or so the container stops and can no longer be started again. I have to delete the image, redownload it fresh, and then it works again for another day or so.

The logs of the container aren't showing any error that I see, but I can provide whatever you need to help troubleshoot it.

[thinkst-daniel]

Hi @chaosclarity84,

Thanks for writing in.

Can you provide more details on where you are running the docker container?

Kind regards,
Daniel

[g3rmanaviator]

I am seeing this as well. Root cause appears to be that when stopping the container the twistd.pid file is not cleaned up.
If I manually remove the twistd.pid file I can start the container again no problem.

Logs:

Another twistd server is running, PID 9

This could either be a previously started instance of your application or a
different application entirely. To start a new one, either run it in some other
directory, or use the --pidfile and --logfile parameters to avoid clashes.

Another twistd server is running, PID 9

This could either be a previously started instance of your application or a
different application entirely. To start a new one, either run it in some other
directory, or use the --pidfile and --logfile parameters to avoid clashes.

[github-actions]

This issue is stale because it has been open for 14 days with no activity.

[g3rmanaviator]

Interesting that in the logs we see the following message:

"Removing stale pidfile /opencanary/twistd.pid"

However, the stale pidfile is not actually removed.

[jayjb]

Hi @g3rmanaviator,

Thanks for the information. I'll take a look at this this week.

[jayjb]

Thanks folks, this has been fixed in the latest. I'll look to bump the stable version soon too.

[imTHAI]

@jayjb Are you no longer experiencing the issue? I still am.
Someone else reported the same issue #424, but there has been no follow-up.

[g3rmanaviator]

Same, still having the issue.

[jayjb]

Hi @imTHAI,

Sorry, I thought we had solved the issue (I wasn't seeing it on my side after the changes). Can you share how exactly you are running it? The exact commands and the environment please.