Never ending Cronjob
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
edited 5 mins ago
Teja Bhagavan Kollepara
2,94841847
asked Jan 27 '15 at 9:45
CenzoCenzo
63211
add a comment |
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
edited 5 mins ago
Teja Bhagavan Kollepara
2,94841847
asked Jan 27 '15 at 9:45
CenzoCenzo
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
add a comment |
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
edited 5 mins ago
Teja Bhagavan Kollepara
2,94841847
asked Jan 27 '15 at 9:45
CenzoCenzo
63211
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
edited 5 mins ago
Teja Bhagavan Kollepara
2,94841847
asked Jan 27 '15 at 9:45
CenzoCenzo
63211
edited 5 mins ago
Teja Bhagavan Kollepara
2,94841847
asked Jan 27 '15 at 9:45
CenzoCenzo
63211
edited 5 mins ago
Teja Bhagavan Kollepara
2,94841847
edited 5 mins ago
Teja Bhagavan Kollepara
2,94841847
edited 5 mins ago
Teja Bhagavan Kollepara
2,94841847
2,94841847
asked Jan 27 '15 at 9:45
CenzoCenzo
63211
asked Jan 27 '15 at 9:45
CenzoCenzo
63211
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
add a comment |
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
add a comment |
2 Answers
2
active
oldest
votes
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.
answered Jan 27 '15 at 14:52
FlyingmanaFlyingmana
5,13132062
1
That's a good answer. You can safely delete old cron jobs from thecron_scheduletable
– 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
add a comment |
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
answered Jan 27 '15 at 13:33
easymoden00beasymoden00b
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
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
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.
answered Jan 27 '15 at 14:52
FlyingmanaFlyingmana
5,13132062
1
That's a good answer. You can safely delete old cron jobs from thecron_scheduletable
– 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
add a comment |
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.
answered Jan 27 '15 at 14:52
FlyingmanaFlyingmana
5,13132062
1
That's a good answer. You can safely delete old cron jobs from thecron_scheduletable
– 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
add a comment |
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.
answered Jan 27 '15 at 14:52
FlyingmanaFlyingmana
5,13132062
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.
answered Jan 27 '15 at 14:52
FlyingmanaFlyingmana
5,13132062
answered Jan 27 '15 at 14:52
FlyingmanaFlyingmana
5,13132062
answered Jan 27 '15 at 14:52
FlyingmanaFlyingmana
5,13132062
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 thecron_scheduletable
– 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
add a comment |
1
That's a good answer. You can safely delete old cron jobs from thecron_scheduletable
– 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
add a comment |
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
answered Jan 27 '15 at 13:33
easymoden00beasymoden00b
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
add a comment |
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
answered Jan 27 '15 at 13:33
easymoden00beasymoden00b
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
add a comment |
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
answered Jan 27 '15 at 13:33
easymoden00beasymoden00b
56721747
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
answered Jan 27 '15 at 13:33
easymoden00beasymoden00b
56721747
answered Jan 27 '15 at 13:33
easymoden00beasymoden00b
56721747
answered Jan 27 '15 at 13:33
easymoden00beasymoden00b
56721747
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
add a comment |
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
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
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