Cron service won't start in 16.04
0
Noticed my cron jobs weren't running (not sure for how long, maybe since I upgraded to 16.04 two weeks ago), and I can't get the service to start.
root@wormhole:~# systemctl start cron.service
Job for cron.service failed because the control process exited with error code. See "systemctl status cron.service" and "journalctl -xe" for details.
root@wormhole:~# systemctl status cron.service
● cron.service
Loaded: loaded (/etc/init.d/cron; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2019-02-20 23:02:57 EST; 6s ago
Docs: man:systemd-sysv-generator(8)
Process: 8340 ExecStart=/etc/init.d/cron start (code=exited, status=1/FAILURE)
Feb 20 23:02:57 wormhole cron[8340]: Rather than invoking init scripts through /etc/init.d, use the service(8)
Feb 20 23:02:57 wormhole cron[8340]: utility, e.g. service cron start
Feb 20 23:02:57 wormhole cron[8340]: initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
Feb 20 23:02:57 wormhole cron[8340]: Since the script you are attempting to invoke has been converted to an
Feb 20 23:02:57 wormhole cron[8340]: Upstart job, you may also use the start(8) utility, e.g. start cron
Feb 20 23:02:57 wormhole cron[8340]: start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
Feb 20 23:02:57 wormhole systemd[1]: cron.service: Control process exited, code=exited status=1
Feb 20 23:02:57 wormhole systemd[1]: Failed to start cron.service.
Feb 20 23:02:57 wormhole systemd[1]: cron.service: Unit entered failed state.
Feb 20 23:02:57 wormhole systemd[1]: cron.service: Failed with result 'exit-code'.
16.04 cron
asked 13 mins ago
DanDan
1063
add a comment |
0
Noticed my cron jobs weren't running (not sure for how long, maybe since I upgraded to 16.04 two weeks ago), and I can't get the service to start.
root@wormhole:~# systemctl start cron.service
Job for cron.service failed because the control process exited with error code. See "systemctl status cron.service" and "journalctl -xe" for details.
root@wormhole:~# systemctl status cron.service
● cron.service
Loaded: loaded (/etc/init.d/cron; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2019-02-20 23:02:57 EST; 6s ago
Docs: man:systemd-sysv-generator(8)
Process: 8340 ExecStart=/etc/init.d/cron start (code=exited, status=1/FAILURE)
Feb 20 23:02:57 wormhole cron[8340]: Rather than invoking init scripts through /etc/init.d, use the service(8)
Feb 20 23:02:57 wormhole cron[8340]: utility, e.g. service cron start
Feb 20 23:02:57 wormhole cron[8340]: initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
Feb 20 23:02:57 wormhole cron[8340]: Since the script you are attempting to invoke has been converted to an
Feb 20 23:02:57 wormhole cron[8340]: Upstart job, you may also use the start(8) utility, e.g. start cron
Feb 20 23:02:57 wormhole cron[8340]: start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
Feb 20 23:02:57 wormhole systemd[1]: cron.service: Control process exited, code=exited status=1
Feb 20 23:02:57 wormhole systemd[1]: Failed to start cron.service.
Feb 20 23:02:57 wormhole systemd[1]: cron.service: Unit entered failed state.
Feb 20 23:02:57 wormhole systemd[1]: cron.service: Failed with result 'exit-code'.
16.04 cron
asked 13 mins ago
DanDan
1063
The error messages seem to indicate that cron was attempting to communicate with Upstart, which was replaced by systemd in 16.04. Did your upgrade from 14.04 to 16.04, by chance, have any errors?
– user535733
4 mins ago
@user535733 Yep sure did. Had to boot into a liveCD and re-installinitto get it to boot after the upgrade
– Dan
4 secs ago
add a comment |
0
0
0
Noticed my cron jobs weren't running (not sure for how long, maybe since I upgraded to 16.04 two weeks ago), and I can't get the service to start.
root@wormhole:~# systemctl start cron.service
Job for cron.service failed because the control process exited with error code. See "systemctl status cron.service" and "journalctl -xe" for details.
root@wormhole:~# systemctl status cron.service
● cron.service
Loaded: loaded (/etc/init.d/cron; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2019-02-20 23:02:57 EST; 6s ago
Docs: man:systemd-sysv-generator(8)
Process: 8340 ExecStart=/etc/init.d/cron start (code=exited, status=1/FAILURE)
Feb 20 23:02:57 wormhole cron[8340]: Rather than invoking init scripts through /etc/init.d, use the service(8)
Feb 20 23:02:57 wormhole cron[8340]: utility, e.g. service cron start
Feb 20 23:02:57 wormhole cron[8340]: initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
Feb 20 23:02:57 wormhole cron[8340]: Since the script you are attempting to invoke has been converted to an
Feb 20 23:02:57 wormhole cron[8340]: Upstart job, you may also use the start(8) utility, e.g. start cron
Feb 20 23:02:57 wormhole cron[8340]: start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
Feb 20 23:02:57 wormhole systemd[1]: cron.service: Control process exited, code=exited status=1
Feb 20 23:02:57 wormhole systemd[1]: Failed to start cron.service.
Feb 20 23:02:57 wormhole systemd[1]: cron.service: Unit entered failed state.
Feb 20 23:02:57 wormhole systemd[1]: cron.service: Failed with result 'exit-code'.
16.04 cron
asked 13 mins ago
DanDan
1063
Noticed my cron jobs weren't running (not sure for how long, maybe since I upgraded to 16.04 two weeks ago), and I can't get the service to start.
root@wormhole:~# systemctl start cron.service
Job for cron.service failed because the control process exited with error code. See "systemctl status cron.service" and "journalctl -xe" for details.
root@wormhole:~# systemctl status cron.service
● cron.service
Loaded: loaded (/etc/init.d/cron; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2019-02-20 23:02:57 EST; 6s ago
Docs: man:systemd-sysv-generator(8)
Process: 8340 ExecStart=/etc/init.d/cron start (code=exited, status=1/FAILURE)
Feb 20 23:02:57 wormhole cron[8340]: Rather than invoking init scripts through /etc/init.d, use the service(8)
Feb 20 23:02:57 wormhole cron[8340]: utility, e.g. service cron start
Feb 20 23:02:57 wormhole cron[8340]: initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
Feb 20 23:02:57 wormhole cron[8340]: Since the script you are attempting to invoke has been converted to an
Feb 20 23:02:57 wormhole cron[8340]: Upstart job, you may also use the start(8) utility, e.g. start cron
Feb 20 23:02:57 wormhole cron[8340]: start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
Feb 20 23:02:57 wormhole systemd[1]: cron.service: Control process exited, code=exited status=1
Feb 20 23:02:57 wormhole systemd[1]: Failed to start cron.service.
Feb 20 23:02:57 wormhole systemd[1]: cron.service: Unit entered failed state.
Feb 20 23:02:57 wormhole systemd[1]: cron.service: Failed with result 'exit-code'.
16.04 cron
16.04 cron
asked 13 mins ago
DanDan
1063
asked 13 mins ago
DanDan
1063
asked 13 mins ago
DanDan
1063
asked 13 mins ago
DanDan
1063
asked 13 mins ago
DanDan
1063
1063
The error messages seem to indicate that cron was attempting to communicate with Upstart, which was replaced by systemd in 16.04. Did your upgrade from 14.04 to 16.04, by chance, have any errors?
– user535733
4 mins ago
@user535733 Yep sure did. Had to boot into a liveCD and re-installinitto get it to boot after the upgrade
– Dan
4 secs ago
add a comment |
The error messages seem to indicate that cron was attempting to communicate with Upstart, which was replaced by systemd in 16.04. Did your upgrade from 14.04 to 16.04, by chance, have any errors?
– user535733
4 mins ago
@user535733 Yep sure did. Had to boot into a liveCD and re-installinitto get it to boot after the upgrade
– Dan
4 secs ago
The error messages seem to indicate that cron was attempting to communicate with Upstart, which was replaced by systemd in 16.04. Did your upgrade from 14.04 to 16.04, by chance, have any errors?
– user535733
4 mins ago
The error messages seem to indicate that cron was attempting to communicate with Upstart, which was replaced by systemd in 16.04. Did your upgrade from 14.04 to 16.04, by chance, have any errors?
– user535733
4 mins ago
@user535733 Yep sure did. Had to boot into a liveCD and re-install
init to get it to boot after the upgrade– Dan
4 secs ago
@user535733 Yep sure did. Had to boot into a liveCD and re-install
init to get it to boot after the upgrade– Dan
4 secs ago
add a comment |
0
active
oldest
votes
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
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%2faskubuntu.com%2fquestions%2f1120004%2fcron-service-wont-start-in-16-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
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%2faskubuntu.com%2fquestions%2f1120004%2fcron-service-wont-start-in-16-04%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
The error messages seem to indicate that cron was attempting to communicate with Upstart, which was replaced by systemd in 16.04. Did your upgrade from 14.04 to 16.04, by chance, have any errors?
– user535733
4 mins ago
@user535733 Yep sure did. Had to boot into a liveCD and re-install
initto get it to boot after the upgrade– Dan
4 secs ago