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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.
@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.