Never ending Cronjob












2















I searched through the whole internet but it seems im am the only one with this problem?



In the Magento (Version 1.7.02) Scheduler Timeline i got a running cronjob that runs since
15.12.2014 till now. Is there any way to delete / stop this job?
Server reboot, deactivation of the job didn't work.






magento-1.7 cron







share|improve this question

























  • what happen if delete the file?

    – Manikandan Arunachalam
    Jan 27 '15 at 9:48













  • no effect on the behaviour ;(

    – Cenzo
    Jan 27 '15 at 11:26
















2















I searched through the whole internet but it seems im am the only one with this problem?



In the Magento (Version 1.7.02) Scheduler Timeline i got a running cronjob that runs since
15.12.2014 till now. Is there any way to delete / stop this job?
Server reboot, deactivation of the job didn't work.






magento-1.7 cron







share|improve this question

























  • what happen if delete the file?

    – Manikandan Arunachalam
    Jan 27 '15 at 9:48













  • no effect on the behaviour ;(

    – Cenzo
    Jan 27 '15 at 11:26














2












2








2








I searched through the whole internet but it seems im am the only one with this problem?



In the Magento (Version 1.7.02) Scheduler Timeline i got a running cronjob that runs since
15.12.2014 till now. Is there any way to delete / stop this job?
Server reboot, deactivation of the job didn't work.






magento-1.7 cron







share|improve this question
















I searched through the whole internet but it seems im am the only one with this problem?



In the Magento (Version 1.7.02) Scheduler Timeline i got a running cronjob that runs since
15.12.2014 till now. Is there any way to delete / stop this job?
Server reboot, deactivation of the job didn't work.






magento-1.7 cron




magento-1.7 cron






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 39 mins ago









Teja Bhagavan Kollepara

2,94841847




2,94841847










asked Jan 27 '15 at 9:45









CenzoCenzo

63211




63211













  • what happen if delete the file?

    – Manikandan Arunachalam
    Jan 27 '15 at 9:48













  • no effect on the behaviour ;(

    – Cenzo
    Jan 27 '15 at 11:26



















  • what happen if delete the file?

    – Manikandan Arunachalam
    Jan 27 '15 at 9:48













  • no effect on the behaviour ;(

    – Cenzo
    Jan 27 '15 at 11:26

















what happen if delete the file?

– Manikandan Arunachalam
Jan 27 '15 at 9:48







what happen if delete the file?

– Manikandan Arunachalam
Jan 27 '15 at 9:48















no effect on the behaviour ;(

– Cenzo
Jan 27 '15 at 11:26





no effect on the behaviour ;(

– Cenzo
Jan 27 '15 at 11:26










2 Answers
2






active

oldest

votes


















3














The job is not really running, the timeline view only visualizes jobs by their "start" and "end" time.
Usually the Cron runner can handle cases of error and set the end time.
But in case of a fatal error this does not happen, the job has ended without setting the state in the database. This happens for example if you exceed the memory limit.



To notice this, you should validate if such errors get into the error log or validate your crontab config, if it not only puts stdout but also error to /dev/null.



You can simple delete this run from the table, it will have no negative effect, and if it had ended would get cleaned anyway after the configured amount of days.






share|improve this answer



















  • 1





    That's a good answer. You can safely delete old cron jobs from the cron_schedule table

    – Mayers
    Jan 27 '15 at 14:55













  • U yea ! Thank you so much for the explanation! It was indeed just a "display error". Now everything looks fine again !

    – Cenzo
    Jan 27 '15 at 15:32



















0














if you want to stop the cron job programmatically then you can get the process id of CRON job when it start executing at very beginning of the script by getmypid and then save it in database with date and time. Then you have to make a cron job that should run after your threshold time, which will check if your script is still running then you kill the process by posix_kill






share|improve this answer



















  • 1





    Thanks for your answer but my job is already running since 15.12. so i have no process id

    – Cenzo
    Jan 27 '15 at 14:37











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f53467%2fnever-ending-cronjob%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









3














The job is not really running, the timeline view only visualizes jobs by their "start" and "end" time.
Usually the Cron runner can handle cases of error and set the end time.
But in case of a fatal error this does not happen, the job has ended without setting the state in the database. This happens for example if you exceed the memory limit.



To notice this, you should validate if such errors get into the error log or validate your crontab config, if it not only puts stdout but also error to /dev/null.



You can simple delete this run from the table, it will have no negative effect, and if it had ended would get cleaned anyway after the configured amount of days.






share|improve this answer



















  • 1





    That's a good answer. You can safely delete old cron jobs from the cron_schedule table

    – Mayers
    Jan 27 '15 at 14:55













  • U yea ! Thank you so much for the explanation! It was indeed just a "display error". Now everything looks fine again !

    – Cenzo
    Jan 27 '15 at 15:32
















3














The job is not really running, the timeline view only visualizes jobs by their "start" and "end" time.
Usually the Cron runner can handle cases of error and set the end time.
But in case of a fatal error this does not happen, the job has ended without setting the state in the database. This happens for example if you exceed the memory limit.



To notice this, you should validate if such errors get into the error log or validate your crontab config, if it not only puts stdout but also error to /dev/null.



You can simple delete this run from the table, it will have no negative effect, and if it had ended would get cleaned anyway after the configured amount of days.






share|improve this answer



















  • 1





    That's a good answer. You can safely delete old cron jobs from the cron_schedule table

    – Mayers
    Jan 27 '15 at 14:55













  • U yea ! Thank you so much for the explanation! It was indeed just a "display error". Now everything looks fine again !

    – Cenzo
    Jan 27 '15 at 15:32














3












3








3







The job is not really running, the timeline view only visualizes jobs by their "start" and "end" time.
Usually the Cron runner can handle cases of error and set the end time.
But in case of a fatal error this does not happen, the job has ended without setting the state in the database. This happens for example if you exceed the memory limit.



To notice this, you should validate if such errors get into the error log or validate your crontab config, if it not only puts stdout but also error to /dev/null.



You can simple delete this run from the table, it will have no negative effect, and if it had ended would get cleaned anyway after the configured amount of days.






share|improve this answer













The job is not really running, the timeline view only visualizes jobs by their "start" and "end" time.
Usually the Cron runner can handle cases of error and set the end time.
But in case of a fatal error this does not happen, the job has ended without setting the state in the database. This happens for example if you exceed the memory limit.



To notice this, you should validate if such errors get into the error log or validate your crontab config, if it not only puts stdout but also error to /dev/null.



You can simple delete this run from the table, it will have no negative effect, and if it had ended would get cleaned anyway after the configured amount of days.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 27 '15 at 14:52









FlyingmanaFlyingmana

5,13132062




5,13132062








  • 1





    That's a good answer. You can safely delete old cron jobs from the cron_schedule table

    – Mayers
    Jan 27 '15 at 14:55













  • U yea ! Thank you so much for the explanation! It was indeed just a "display error". Now everything looks fine again !

    – Cenzo
    Jan 27 '15 at 15:32














  • 1





    That's a good answer. You can safely delete old cron jobs from the cron_schedule table

    – Mayers
    Jan 27 '15 at 14:55













  • U yea ! Thank you so much for the explanation! It was indeed just a "display error". Now everything looks fine again !

    – Cenzo
    Jan 27 '15 at 15:32








1




1





That's a good answer. You can safely delete old cron jobs from the cron_schedule table

– Mayers
Jan 27 '15 at 14:55







That's a good answer. You can safely delete old cron jobs from the cron_schedule table

– Mayers
Jan 27 '15 at 14:55















U yea ! Thank you so much for the explanation! It was indeed just a "display error". Now everything looks fine again !

– Cenzo
Jan 27 '15 at 15:32





U yea ! Thank you so much for the explanation! It was indeed just a "display error". Now everything looks fine again !

– Cenzo
Jan 27 '15 at 15:32













0














if you want to stop the cron job programmatically then you can get the process id of CRON job when it start executing at very beginning of the script by getmypid and then save it in database with date and time. Then you have to make a cron job that should run after your threshold time, which will check if your script is still running then you kill the process by posix_kill






share|improve this answer



















  • 1





    Thanks for your answer but my job is already running since 15.12. so i have no process id

    – Cenzo
    Jan 27 '15 at 14:37
















0














if you want to stop the cron job programmatically then you can get the process id of CRON job when it start executing at very beginning of the script by getmypid and then save it in database with date and time. Then you have to make a cron job that should run after your threshold time, which will check if your script is still running then you kill the process by posix_kill






share|improve this answer



















  • 1





    Thanks for your answer but my job is already running since 15.12. so i have no process id

    – Cenzo
    Jan 27 '15 at 14:37














0












0








0







if you want to stop the cron job programmatically then you can get the process id of CRON job when it start executing at very beginning of the script by getmypid and then save it in database with date and time. Then you have to make a cron job that should run after your threshold time, which will check if your script is still running then you kill the process by posix_kill






share|improve this answer













if you want to stop the cron job programmatically then you can get the process id of CRON job when it start executing at very beginning of the script by getmypid and then save it in database with date and time. Then you have to make a cron job that should run after your threshold time, which will check if your script is still running then you kill the process by posix_kill







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 27 '15 at 13:33









easymoden00beasymoden00b

56721747




56721747








  • 1





    Thanks for your answer but my job is already running since 15.12. so i have no process id

    – Cenzo
    Jan 27 '15 at 14:37














  • 1





    Thanks for your answer but my job is already running since 15.12. so i have no process id

    – Cenzo
    Jan 27 '15 at 14:37








1




1





Thanks for your answer but my job is already running since 15.12. so i have no process id

– Cenzo
Jan 27 '15 at 14:37





Thanks for your answer but my job is already running since 15.12. so i have no process id

– Cenzo
Jan 27 '15 at 14:37


















draft saved

draft discarded




















































Thanks for contributing an answer to Magento Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f53467%2fnever-ending-cronjob%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Magento 2 controller redirect on button click in phtml file

Image
0 I want to redirect customer using controller when button is clicked in one of my phtml files. So far I got, controller: public function execute(){ return $this->addToCart(); } public function addToCart(){ // some logic $this->_redirect('checkout/cart/index'); } The above is working fine (redirecting) when you access the controller via URL (www.mydomain.com/batchorder/index/addtocart). And here is my .phtml file: $("#addToCart").click(function(){ let controllerUrl = "<?php echo $block-getUrl('batchorder/index/addtocart'); ?>" $.post(controllerUrl, { "products": JSON.stringify(sideCart.SideCartProducts) }) The post request returns my logic as it should, however, it is not redirecting. Anyone can help? ...
Read more

Polycentropodidae

Image
Polycentropodidae Plectrocnemia conspersa Siyentipiko nga pagklasipika Ginhadi-an: Animalia Phylum: Arthropoda Ubosphylum: Hexapoda Klase: Insecta Orden: Trichoptera Labawbanay: Hydropsychoidea Banay: Polycentropodidae Binomial nga ngaran Polycentropodidae An Polycentropodidae [1] in uska familia han Insecta. An Polycentropodidae in nahilalakip ha familia nga Hydropsychoidea, ordo nga Trichoptera, classis nga Insecta, punoan nga Arthropoda, ngan regnum nga Animalia. [1] An familia nga Polycentropodidae in naglalakip hin 660 ka mga species, sumala ha Catalogue of Life [1] . An kladograma hini sumala ha Catalogue of Life [1] : Hydropsychoidea   Polycentropodidae  Adectophylax Antillopsyche Cernotina Cyrnellus Cyrnodes Cyrnopsis Cyrnus Eodipseudopsis Eoneureclipsis Holocentropus Kambaitipsyche Neucentropus ...
Read more