crond won't start. Problem with temp directory /run/cron?
Clash Royale CLAN TAG#URR8PPP
A week ago I updated my wife's computer, and after a few days noticed that crond wasn't running. Running crond -d wasn't much useful, so I ran strace crond -d`. This error appears:
openat(AT_FDCWD, "/dev/null", O_RDWR) = 0
dup2(0, 0) = 0
dup2(0, 1) = 1
brk(NULL) = 0x1dab000
brk(0x1dcc000) = 0x1dcc000
getpid() = 1405
mkdir("/run/cron/cron.I23Z7s", 0700) = -1 ENOENT (No such file or directory)
dup(2) = 3
fcntl(3, F_GETFL) = 0x2 (flags O_RDWR)
fstat(3, 0620, st_rdev=makedev(136, 0), ...) = 0
write(3, "mkdtemp: No such file or directo"..., 35mkdtemp: No such file or directory
BTW, OS is Slackware64-current.
Extra info:
I just detected that I can start rc.crond manually (as root), but it doesn't start when rebooting... and it works correctly, executing all the cron tasks.
linux cron slackware
edited Jan 1 at 21:50
Rui F Ribeiro
39.5k1479132
asked Jan 1 at 20:35
jcoppensjcoppens
35517
add a comment |
A week ago I updated my wife's computer, and after a few days noticed that crond wasn't running. Running crond -d wasn't much useful, so I ran strace crond -d`. This error appears:
openat(AT_FDCWD, "/dev/null", O_RDWR) = 0
dup2(0, 0) = 0
dup2(0, 1) = 1
brk(NULL) = 0x1dab000
brk(0x1dcc000) = 0x1dcc000
getpid() = 1405
mkdir("/run/cron/cron.I23Z7s", 0700) = -1 ENOENT (No such file or directory)
dup(2) = 3
fcntl(3, F_GETFL) = 0x2 (flags O_RDWR)
fstat(3, 0620, st_rdev=makedev(136, 0), ...) = 0
write(3, "mkdtemp: No such file or directo"..., 35mkdtemp: No such file or directory
BTW, OS is Slackware64-current.
Extra info:
I just detected that I can start rc.crond manually (as root), but it doesn't start when rebooting... and it works correctly, executing all the cron tasks.
linux cron slackware
edited Jan 1 at 21:50
Rui F Ribeiro
39.5k1479132
asked Jan 1 at 20:35
jcoppensjcoppens
35517
does the directory /run/cron exist and have permissions that allow cron to create temp files?
– Jeff A
Jan 3 at 4:53
It did have permissions, and the directory seems to be generated on boot. But the problem was different, see answer below.
– jcoppens
Jan 3 at 21:19
add a comment |
A week ago I updated my wife's computer, and after a few days noticed that crond wasn't running. Running crond -d wasn't much useful, so I ran strace crond -d`. This error appears:
openat(AT_FDCWD, "/dev/null", O_RDWR) = 0
dup2(0, 0) = 0
dup2(0, 1) = 1
brk(NULL) = 0x1dab000
brk(0x1dcc000) = 0x1dcc000
getpid() = 1405
mkdir("/run/cron/cron.I23Z7s", 0700) = -1 ENOENT (No such file or directory)
dup(2) = 3
fcntl(3, F_GETFL) = 0x2 (flags O_RDWR)
fstat(3, 0620, st_rdev=makedev(136, 0), ...) = 0
write(3, "mkdtemp: No such file or directo"..., 35mkdtemp: No such file or directory
BTW, OS is Slackware64-current.
Extra info:
I just detected that I can start rc.crond manually (as root), but it doesn't start when rebooting... and it works correctly, executing all the cron tasks.
linux cron slackware
edited Jan 1 at 21:50
Rui F Ribeiro
39.5k1479132
asked Jan 1 at 20:35
jcoppensjcoppens
35517
A week ago I updated my wife's computer, and after a few days noticed that crond wasn't running. Running crond -d wasn't much useful, so I ran strace crond -d`. This error appears:
openat(AT_FDCWD, "/dev/null", O_RDWR) = 0
dup2(0, 0) = 0
dup2(0, 1) = 1
brk(NULL) = 0x1dab000
brk(0x1dcc000) = 0x1dcc000
getpid() = 1405
mkdir("/run/cron/cron.I23Z7s", 0700) = -1 ENOENT (No such file or directory)
dup(2) = 3
fcntl(3, F_GETFL) = 0x2 (flags O_RDWR)
fstat(3, 0620, st_rdev=makedev(136, 0), ...) = 0
write(3, "mkdtemp: No such file or directo"..., 35mkdtemp: No such file or directory
BTW, OS is Slackware64-current.
Extra info:
I just detected that I can start rc.crond manually (as root), but it doesn't start when rebooting... and it works correctly, executing all the cron tasks.
linux cron slackware
linux cron slackware
edited Jan 1 at 21:50
Rui F Ribeiro
39.5k1479132
asked Jan 1 at 20:35
jcoppensjcoppens
35517
edited Jan 1 at 21:50
Rui F Ribeiro
39.5k1479132
asked Jan 1 at 20:35
jcoppensjcoppens
35517
edited Jan 1 at 21:50
Rui F Ribeiro
39.5k1479132
edited Jan 1 at 21:50
Rui F Ribeiro
39.5k1479132
edited Jan 1 at 21:50
Rui F Ribeiro
39.5k1479132
39.5k1479132
asked Jan 1 at 20:35
jcoppensjcoppens
35517
asked Jan 1 at 20:35
jcoppensjcoppens
35517
asked Jan 1 at 20:35
jcoppensjcoppens
35517
35517
does the directory /run/cron exist and have permissions that allow cron to create temp files?
– Jeff A
Jan 3 at 4:53
It did have permissions, and the directory seems to be generated on boot. But the problem was different, see answer below.
– jcoppens
Jan 3 at 21:19
add a comment |
does the directory /run/cron exist and have permissions that allow cron to create temp files?
– Jeff A
Jan 3 at 4:53
It did have permissions, and the directory seems to be generated on boot. But the problem was different, see answer below.
– jcoppens
Jan 3 at 21:19
does the directory /run/cron exist and have permissions that allow cron to create temp files?
– Jeff A
Jan 3 at 4:53
does the directory /run/cron exist and have permissions that allow cron to create temp files?
– Jeff A
Jan 3 at 4:53
It did have permissions, and the directory seems to be generated on boot. But the problem was different, see answer below.
– jcoppens
Jan 3 at 21:19
It did have permissions, and the directory seems to be generated on boot. But the problem was different, see answer below.
– jcoppens
Jan 3 at 21:19
add a comment |
1 Answer
1
active
oldest
votes
After some discussion on the ##slackware IRC channel about how this problem could occur, I noticed that there was a difference in the /etc/rc.d/rc.M file in my computer and the one at one of the participants.
Older versions of Slackware seem to manage the crond startup directly, while newer versions do this task indirectly by calling rc.crond start. rc.crond does some extra work. Normally this should have been updated automatically, but, for some reason, it wasn't (the rc.M.new hadn't replaced the original file).
answered Jan 3 at 21:29
jcoppensjcoppens
35517
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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%2funix.stackexchange.com%2fquestions%2f491914%2fcrond-wont-start-problem-with-temp-directory-run-cron%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
After some discussion on the ##slackware IRC channel about how this problem could occur, I noticed that there was a difference in the /etc/rc.d/rc.M file in my computer and the one at one of the participants.
Older versions of Slackware seem to manage the crond startup directly, while newer versions do this task indirectly by calling rc.crond start. rc.crond does some extra work. Normally this should have been updated automatically, but, for some reason, it wasn't (the rc.M.new hadn't replaced the original file).
answered Jan 3 at 21:29
jcoppensjcoppens
35517
add a comment |
After some discussion on the ##slackware IRC channel about how this problem could occur, I noticed that there was a difference in the /etc/rc.d/rc.M file in my computer and the one at one of the participants.
Older versions of Slackware seem to manage the crond startup directly, while newer versions do this task indirectly by calling rc.crond start. rc.crond does some extra work. Normally this should have been updated automatically, but, for some reason, it wasn't (the rc.M.new hadn't replaced the original file).
answered Jan 3 at 21:29
jcoppensjcoppens
35517
add a comment |
After some discussion on the ##slackware IRC channel about how this problem could occur, I noticed that there was a difference in the /etc/rc.d/rc.M file in my computer and the one at one of the participants.
Older versions of Slackware seem to manage the crond startup directly, while newer versions do this task indirectly by calling rc.crond start. rc.crond does some extra work. Normally this should have been updated automatically, but, for some reason, it wasn't (the rc.M.new hadn't replaced the original file).
answered Jan 3 at 21:29
jcoppensjcoppens
35517
After some discussion on the ##slackware IRC channel about how this problem could occur, I noticed that there was a difference in the /etc/rc.d/rc.M file in my computer and the one at one of the participants.
Older versions of Slackware seem to manage the crond startup directly, while newer versions do this task indirectly by calling rc.crond start. rc.crond does some extra work. Normally this should have been updated automatically, but, for some reason, it wasn't (the rc.M.new hadn't replaced the original file).
answered Jan 3 at 21:29
jcoppensjcoppens
35517
answered Jan 3 at 21:29
jcoppensjcoppens
35517
answered Jan 3 at 21:29
jcoppensjcoppens
35517
answered Jan 3 at 21:29
jcoppensjcoppens
35517
35517
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux 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%2funix.stackexchange.com%2fquestions%2f491914%2fcrond-wont-start-problem-with-temp-directory-run-cron%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
does the directory /run/cron exist and have permissions that allow cron to create temp files?
– Jeff A
Jan 3 at 4:53
It did have permissions, and the directory seems to be generated on boot. But the problem was different, see answer below.
– jcoppens
Jan 3 at 21:19