Cron service fails to start












1















I have an Ubuntu 14.04 and I am trying to start cron service without success. I always get this after running service cron start:



Job for cron.service failed because the control process exited with error code.



systemctl status cron.service says that the cron service is loaded but failed:



cron.service
Loaded: loaded (/etc/init.d/cron; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-06-15 09:06:19 AWST; 6min ago
Docs: man:systemd-sysv-generator(8)
Process: 22707 ExecStart=/etc/init.d/cron start (code=exited, status=1/FAILURE)

cron[22707]: Rather than invoking init scripts through /etc/init.d, use the service(8)
cron[22707]: utility, e.g. service cron start
cron[22707]: initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
cron[22707]: Since the script you are attempting to invoke has been converted to an
cron[22707]: Upstart job, you may also use the start(8) utility, e.g. start cron
cron[22707]: start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
systemd[1]: cron.service: Control process exited, code=exited status=1
systemd[1]: Failed to start cron.service.
systemd[1]: cron.service: Unit entered failed state.
systemd[1]: cron.service: Failed with result 'exit-code'.


Any hint on how to make cron service to successfully start?










share|improve this question




















  • 1





    14.04 shipped with Upstart instead of systemd, so those systemd messages seem curious.

    – user535733
    Jun 15 '18 at 3:08
















1















I have an Ubuntu 14.04 and I am trying to start cron service without success. I always get this after running service cron start:



Job for cron.service failed because the control process exited with error code.



systemctl status cron.service says that the cron service is loaded but failed:



cron.service
Loaded: loaded (/etc/init.d/cron; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-06-15 09:06:19 AWST; 6min ago
Docs: man:systemd-sysv-generator(8)
Process: 22707 ExecStart=/etc/init.d/cron start (code=exited, status=1/FAILURE)

cron[22707]: Rather than invoking init scripts through /etc/init.d, use the service(8)
cron[22707]: utility, e.g. service cron start
cron[22707]: initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
cron[22707]: Since the script you are attempting to invoke has been converted to an
cron[22707]: Upstart job, you may also use the start(8) utility, e.g. start cron
cron[22707]: start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
systemd[1]: cron.service: Control process exited, code=exited status=1
systemd[1]: Failed to start cron.service.
systemd[1]: cron.service: Unit entered failed state.
systemd[1]: cron.service: Failed with result 'exit-code'.


Any hint on how to make cron service to successfully start?










share|improve this question




















  • 1





    14.04 shipped with Upstart instead of systemd, so those systemd messages seem curious.

    – user535733
    Jun 15 '18 at 3:08














1












1








1


1






I have an Ubuntu 14.04 and I am trying to start cron service without success. I always get this after running service cron start:



Job for cron.service failed because the control process exited with error code.



systemctl status cron.service says that the cron service is loaded but failed:



cron.service
Loaded: loaded (/etc/init.d/cron; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-06-15 09:06:19 AWST; 6min ago
Docs: man:systemd-sysv-generator(8)
Process: 22707 ExecStart=/etc/init.d/cron start (code=exited, status=1/FAILURE)

cron[22707]: Rather than invoking init scripts through /etc/init.d, use the service(8)
cron[22707]: utility, e.g. service cron start
cron[22707]: initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
cron[22707]: Since the script you are attempting to invoke has been converted to an
cron[22707]: Upstart job, you may also use the start(8) utility, e.g. start cron
cron[22707]: start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
systemd[1]: cron.service: Control process exited, code=exited status=1
systemd[1]: Failed to start cron.service.
systemd[1]: cron.service: Unit entered failed state.
systemd[1]: cron.service: Failed with result 'exit-code'.


Any hint on how to make cron service to successfully start?










share|improve this question
















I have an Ubuntu 14.04 and I am trying to start cron service without success. I always get this after running service cron start:



Job for cron.service failed because the control process exited with error code.



systemctl status cron.service says that the cron service is loaded but failed:



cron.service
Loaded: loaded (/etc/init.d/cron; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-06-15 09:06:19 AWST; 6min ago
Docs: man:systemd-sysv-generator(8)
Process: 22707 ExecStart=/etc/init.d/cron start (code=exited, status=1/FAILURE)

cron[22707]: Rather than invoking init scripts through /etc/init.d, use the service(8)
cron[22707]: utility, e.g. service cron start
cron[22707]: initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
cron[22707]: Since the script you are attempting to invoke has been converted to an
cron[22707]: Upstart job, you may also use the start(8) utility, e.g. start cron
cron[22707]: start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
systemd[1]: cron.service: Control process exited, code=exited status=1
systemd[1]: Failed to start cron.service.
systemd[1]: cron.service: Unit entered failed state.
systemd[1]: cron.service: Failed with result 'exit-code'.


Any hint on how to make cron service to successfully start?







server scripts cron services






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 15 '18 at 1:28







farielvolador

















asked Jun 15 '18 at 1:22









farielvoladorfarielvolador

62




62








  • 1





    14.04 shipped with Upstart instead of systemd, so those systemd messages seem curious.

    – user535733
    Jun 15 '18 at 3:08














  • 1





    14.04 shipped with Upstart instead of systemd, so those systemd messages seem curious.

    – user535733
    Jun 15 '18 at 3:08








1




1





14.04 shipped with Upstart instead of systemd, so those systemd messages seem curious.

– user535733
Jun 15 '18 at 3:08





14.04 shipped with Upstart instead of systemd, so those systemd messages seem curious.

– user535733
Jun 15 '18 at 3:08










1 Answer
1






active

oldest

votes


















-1














I encountered similar issue, and this is what I was seeing



 systemctl status crond.service
● crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-02-07 13:34:38 EST; 2min 37s ago
Process: 31470 ExecStart=/usr/sbin/crond -n $CRONDARGS (code=exited, status=1/FAILURE)
Main PID: 31470 (code=exited, status=1/FAILURE)


What I did to resolve this by checking my cron log. I am running in rhel, and my log is at /var/log/cron, my issue was due to this
...(CRON) DEATH (can't lock /var/run/crond.pid, other pid may be 31364): Resource temporarily unavailable



so I just did



pkill -f crond


then



systemctl start crond.service 


then it's back to normal



systemctl status crond.service
● crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-02-07 13:37:19 EST; 1s ago
Main PID: 31490 (crond)
CGroup: /system.slice/crond.service
└─31490 /usr/sbin/crond -n





share|improve this answer










New contributor




JCAA is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    This doesn't seem to deal with the underlying issue. Just killing things is not a solution.

    – Ken Sharp
    yesterday











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2faskubuntu.com%2fquestions%2f1046720%2fcron-service-fails-to-start%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









-1














I encountered similar issue, and this is what I was seeing



 systemctl status crond.service
● crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-02-07 13:34:38 EST; 2min 37s ago
Process: 31470 ExecStart=/usr/sbin/crond -n $CRONDARGS (code=exited, status=1/FAILURE)
Main PID: 31470 (code=exited, status=1/FAILURE)


What I did to resolve this by checking my cron log. I am running in rhel, and my log is at /var/log/cron, my issue was due to this
...(CRON) DEATH (can't lock /var/run/crond.pid, other pid may be 31364): Resource temporarily unavailable



so I just did



pkill -f crond


then



systemctl start crond.service 


then it's back to normal



systemctl status crond.service
● crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-02-07 13:37:19 EST; 1s ago
Main PID: 31490 (crond)
CGroup: /system.slice/crond.service
└─31490 /usr/sbin/crond -n





share|improve this answer










New contributor




JCAA is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    This doesn't seem to deal with the underlying issue. Just killing things is not a solution.

    – Ken Sharp
    yesterday
















-1














I encountered similar issue, and this is what I was seeing



 systemctl status crond.service
● crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-02-07 13:34:38 EST; 2min 37s ago
Process: 31470 ExecStart=/usr/sbin/crond -n $CRONDARGS (code=exited, status=1/FAILURE)
Main PID: 31470 (code=exited, status=1/FAILURE)


What I did to resolve this by checking my cron log. I am running in rhel, and my log is at /var/log/cron, my issue was due to this
...(CRON) DEATH (can't lock /var/run/crond.pid, other pid may be 31364): Resource temporarily unavailable



so I just did



pkill -f crond


then



systemctl start crond.service 


then it's back to normal



systemctl status crond.service
● crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-02-07 13:37:19 EST; 1s ago
Main PID: 31490 (crond)
CGroup: /system.slice/crond.service
└─31490 /usr/sbin/crond -n





share|improve this answer










New contributor




JCAA is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    This doesn't seem to deal with the underlying issue. Just killing things is not a solution.

    – Ken Sharp
    yesterday














-1












-1








-1







I encountered similar issue, and this is what I was seeing



 systemctl status crond.service
● crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-02-07 13:34:38 EST; 2min 37s ago
Process: 31470 ExecStart=/usr/sbin/crond -n $CRONDARGS (code=exited, status=1/FAILURE)
Main PID: 31470 (code=exited, status=1/FAILURE)


What I did to resolve this by checking my cron log. I am running in rhel, and my log is at /var/log/cron, my issue was due to this
...(CRON) DEATH (can't lock /var/run/crond.pid, other pid may be 31364): Resource temporarily unavailable



so I just did



pkill -f crond


then



systemctl start crond.service 


then it's back to normal



systemctl status crond.service
● crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-02-07 13:37:19 EST; 1s ago
Main PID: 31490 (crond)
CGroup: /system.slice/crond.service
└─31490 /usr/sbin/crond -n





share|improve this answer










New contributor




JCAA is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.










I encountered similar issue, and this is what I was seeing



 systemctl status crond.service
● crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-02-07 13:34:38 EST; 2min 37s ago
Process: 31470 ExecStart=/usr/sbin/crond -n $CRONDARGS (code=exited, status=1/FAILURE)
Main PID: 31470 (code=exited, status=1/FAILURE)


What I did to resolve this by checking my cron log. I am running in rhel, and my log is at /var/log/cron, my issue was due to this
...(CRON) DEATH (can't lock /var/run/crond.pid, other pid may be 31364): Resource temporarily unavailable



so I just did



pkill -f crond


then



systemctl start crond.service 


then it's back to normal



systemctl status crond.service
● crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-02-07 13:37:19 EST; 1s ago
Main PID: 31490 (crond)
CGroup: /system.slice/crond.service
└─31490 /usr/sbin/crond -n






share|improve this answer










New contributor




JCAA is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this answer



share|improve this answer








edited yesterday









mature

1,8871724




1,8871724






New contributor




JCAA is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









answered yesterday









JCAAJCAA

1




1




New contributor




JCAA is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





JCAA is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






JCAA is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 1





    This doesn't seem to deal with the underlying issue. Just killing things is not a solution.

    – Ken Sharp
    yesterday














  • 1





    This doesn't seem to deal with the underlying issue. Just killing things is not a solution.

    – Ken Sharp
    yesterday








1




1





This doesn't seem to deal with the underlying issue. Just killing things is not a solution.

– Ken Sharp
yesterday





This doesn't seem to deal with the underlying issue. Just killing things is not a solution.

– Ken Sharp
yesterday


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • 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%2faskubuntu.com%2fquestions%2f1046720%2fcron-service-fails-to-start%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

數位音樂下載

格利澤436b

When can things happen in Etherscan, such as the picture below?