PID file prevents Cronicle from starting

bluet / docker-cronicle-docker

Scheduling dockerized Cronicle cron jobs run in docker container.

MIT License

105 stars 26 forks source link

Closed Tin-Joy59 closed 2 years ago

Tin-Joy59 commented 2 years ago

Whenever Cronicle exists improperly, the PID file remains in the logs directory and prevents from subsequent startup.

I noticed there has been an issue with it already but I experience this on the latest version too.

On start, old PID files are not removed.

Could you help me solve the issue or circumvent it?

bluet commented 2 years ago

@TinJoy59 is this related to #23 ?

bluet commented 2 years ago

I've pushed the updated 0.9.9, please help on testing it and see if the issue persists. Thanks.

Tin-Joy59 commented 2 years ago

Yes, thank you. The PID files is now removed upon start.