Crono process getting killed once started #61

Closed
opened 2025-12-29 00:22:06 +01:00 by adam · 1 comment
Owner

Originally created by @RaghavPratap on GitHub (Dec 3, 2019).

Crono process automatically getting killed after it get started. There is no memory issue which I have already checked. We do see that pid is added and when we grep the process then can see the process id.

ps -ef | grep crono

But within a second it get killed and keep repeating whenever we restarted.

Originally created by @RaghavPratap on GitHub (Dec 3, 2019). Crono process automatically getting killed after it get started. There is no memory issue which I have already checked. We do see that pid is added and when we grep the process then can see the process id. ps -ef | grep crono But within a second it get killed and keep repeating whenever we restarted.
adam closed this issue 2025-12-29 00:22:07 +01:00
Author
Owner

@RaghavPratap commented on GitHub (Dec 3, 2019):

I have found the root cause in my crono_jobs table. I saw the primary key was missing on the table when I restored my database.

@RaghavPratap commented on GitHub (Dec 3, 2019): I have found the root cause in my crono_jobs table. I saw the primary key was missing on the table when I restored my database.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/crono#61