I cannot kill crond - trying to stop cron service
up vote
1
down vote
favorite
This is frustrating, I try:
service crond status
And get this:
Redirecting to /bin/systemctl status crond.service
crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled)
Active: active (running) since Thu 2015-06-25 07:44:35 UTC; 1 months 21 days ago
Main PID: 2557 (crond)
CGroup: /system.slice/crond.service
└─2557 /usr/sbin/crond -n
Aug 14 21:18:37 li958-202.members.linode.com crond[2557]: 2015-08-14 21:18:37 1ZQMLV-0004ER-HX User 0 set for local_delivery transport is on the neve...ers list
Aug 14 21:18:37 li958-202.members.linode.com crond[2557]: 2015-08-14 21:18:37 1ZQMN3-0004ST-Nr User 0 set for local_delivery transport is on the neve...ers list
Aug 15 21:18:19 li958-202.members.linode.com crond[2557]: 2015-08-15 21:18:19 1ZQip4-0005iq-BH User 0 set for local_delivery transport is on the neve...ers list
Aug 15 21:18:19 li958-202.members.linode.com crond[2557]: 2015-08-15 21:18:19 1ZQiqJ-0005va-CF User 0 set for local_delivery transport is on the neve...ers list
Aug 16 00:35:01 li958-202.members.linode.com crond[2557]: (CRON) OPENDIR FAILED (/var/spool/cron): No such file or directory
Aug 16 01:49:57 li958-202.members.linode.com systemd[1]: Started Command Scheduler.
Aug 16 01:50:09 li958-202.members.linode.com systemd[1]: Started Command Scheduler.
Aug 16 02:08:01 li958-202.members.linode.com crond[2557]: (CRON) INFO (running with inotify support)
Aug 16 02:09:01 li958-202.members.linode.com crond[2557]: (CRON) INFO (running with inotify support)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Hint: Some lines were ellipsized, use -l to show in full.
Then I have tried all these per searching on SO and elsewhere:
kill -1 2557
kill -HUP 2557
service crond stop
NOTHING works. Can anyone help with this?
cron kill start-stop-daemon
asked Aug 16 '15 at 2:16
Oliver Williams
3842513
add a comment |
up vote
1
down vote
favorite
This is frustrating, I try:
service crond status
And get this:
Redirecting to /bin/systemctl status crond.service
crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled)
Active: active (running) since Thu 2015-06-25 07:44:35 UTC; 1 months 21 days ago
Main PID: 2557 (crond)
CGroup: /system.slice/crond.service
└─2557 /usr/sbin/crond -n
Aug 14 21:18:37 li958-202.members.linode.com crond[2557]: 2015-08-14 21:18:37 1ZQMLV-0004ER-HX User 0 set for local_delivery transport is on the neve...ers list
Aug 14 21:18:37 li958-202.members.linode.com crond[2557]: 2015-08-14 21:18:37 1ZQMN3-0004ST-Nr User 0 set for local_delivery transport is on the neve...ers list
Aug 15 21:18:19 li958-202.members.linode.com crond[2557]: 2015-08-15 21:18:19 1ZQip4-0005iq-BH User 0 set for local_delivery transport is on the neve...ers list
Aug 15 21:18:19 li958-202.members.linode.com crond[2557]: 2015-08-15 21:18:19 1ZQiqJ-0005va-CF User 0 set for local_delivery transport is on the neve...ers list
Aug 16 00:35:01 li958-202.members.linode.com crond[2557]: (CRON) OPENDIR FAILED (/var/spool/cron): No such file or directory
Aug 16 01:49:57 li958-202.members.linode.com systemd[1]: Started Command Scheduler.
Aug 16 01:50:09 li958-202.members.linode.com systemd[1]: Started Command Scheduler.
Aug 16 02:08:01 li958-202.members.linode.com crond[2557]: (CRON) INFO (running with inotify support)
Aug 16 02:09:01 li958-202.members.linode.com crond[2557]: (CRON) INFO (running with inotify support)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Hint: Some lines were ellipsized, use -l to show in full.
Then I have tried all these per searching on SO and elsewhere:
kill -1 2557
kill -HUP 2557
service crond stop
NOTHING works. Can anyone help with this?
cron kill start-stop-daemon
asked Aug 16 '15 at 2:16
Oliver Williams
3842513
After you useservice crond stopwhat does the logs say?
– neuron
Aug 16 '15 at 8:09
I do not know where the logs are located on my machine. I tried:grep CRON /var/log/messages- no success. Where is cron logging?
– Oliver Williams
Aug 16 '15 at 21:41
Another alternative is kill -15 2557 and only resort to kill -9 2557 if that failed.
– rreck
Aug 17 '15 at 20:52
Is there a real reason for actually wanting to stop the cron daemon, ever?
– Kusalananda
Jul 11 at 12:50
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
This is frustrating, I try:
service crond status
And get this:
Redirecting to /bin/systemctl status crond.service
crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled)
Active: active (running) since Thu 2015-06-25 07:44:35 UTC; 1 months 21 days ago
Main PID: 2557 (crond)
CGroup: /system.slice/crond.service
└─2557 /usr/sbin/crond -n
Aug 14 21:18:37 li958-202.members.linode.com crond[2557]: 2015-08-14 21:18:37 1ZQMLV-0004ER-HX User 0 set for local_delivery transport is on the neve...ers list
Aug 14 21:18:37 li958-202.members.linode.com crond[2557]: 2015-08-14 21:18:37 1ZQMN3-0004ST-Nr User 0 set for local_delivery transport is on the neve...ers list
Aug 15 21:18:19 li958-202.members.linode.com crond[2557]: 2015-08-15 21:18:19 1ZQip4-0005iq-BH User 0 set for local_delivery transport is on the neve...ers list
Aug 15 21:18:19 li958-202.members.linode.com crond[2557]: 2015-08-15 21:18:19 1ZQiqJ-0005va-CF User 0 set for local_delivery transport is on the neve...ers list
Aug 16 00:35:01 li958-202.members.linode.com crond[2557]: (CRON) OPENDIR FAILED (/var/spool/cron): No such file or directory
Aug 16 01:49:57 li958-202.members.linode.com systemd[1]: Started Command Scheduler.
Aug 16 01:50:09 li958-202.members.linode.com systemd[1]: Started Command Scheduler.
Aug 16 02:08:01 li958-202.members.linode.com crond[2557]: (CRON) INFO (running with inotify support)
Aug 16 02:09:01 li958-202.members.linode.com crond[2557]: (CRON) INFO (running with inotify support)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Hint: Some lines were ellipsized, use -l to show in full.
Then I have tried all these per searching on SO and elsewhere:
kill -1 2557
kill -HUP 2557
service crond stop
NOTHING works. Can anyone help with this?
cron kill start-stop-daemon
asked Aug 16 '15 at 2:16
Oliver Williams
3842513
This is frustrating, I try:
service crond status
And get this:
Redirecting to /bin/systemctl status crond.service
crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled)
Active: active (running) since Thu 2015-06-25 07:44:35 UTC; 1 months 21 days ago
Main PID: 2557 (crond)
CGroup: /system.slice/crond.service
└─2557 /usr/sbin/crond -n
Aug 14 21:18:37 li958-202.members.linode.com crond[2557]: 2015-08-14 21:18:37 1ZQMLV-0004ER-HX User 0 set for local_delivery transport is on the neve...ers list
Aug 14 21:18:37 li958-202.members.linode.com crond[2557]: 2015-08-14 21:18:37 1ZQMN3-0004ST-Nr User 0 set for local_delivery transport is on the neve...ers list
Aug 15 21:18:19 li958-202.members.linode.com crond[2557]: 2015-08-15 21:18:19 1ZQip4-0005iq-BH User 0 set for local_delivery transport is on the neve...ers list
Aug 15 21:18:19 li958-202.members.linode.com crond[2557]: 2015-08-15 21:18:19 1ZQiqJ-0005va-CF User 0 set for local_delivery transport is on the neve...ers list
Aug 16 00:35:01 li958-202.members.linode.com crond[2557]: (CRON) OPENDIR FAILED (/var/spool/cron): No such file or directory
Aug 16 01:49:57 li958-202.members.linode.com systemd[1]: Started Command Scheduler.
Aug 16 01:50:09 li958-202.members.linode.com systemd[1]: Started Command Scheduler.
Aug 16 02:08:01 li958-202.members.linode.com crond[2557]: (CRON) INFO (running with inotify support)
Aug 16 02:09:01 li958-202.members.linode.com crond[2557]: (CRON) INFO (running with inotify support)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Hint: Some lines were ellipsized, use -l to show in full.
Then I have tried all these per searching on SO and elsewhere:
kill -1 2557
kill -HUP 2557
service crond stop
NOTHING works. Can anyone help with this?
cron kill start-stop-daemon
cron kill start-stop-daemon
asked Aug 16 '15 at 2:16
Oliver Williams
3842513
asked Aug 16 '15 at 2:16
Oliver Williams
3842513
asked Aug 16 '15 at 2:16
Oliver Williams
3842513
asked Aug 16 '15 at 2:16
Oliver Williams
3842513
asked Aug 16 '15 at 2:16
Oliver Williams
3842513
3842513
After you useservice crond stopwhat does the logs say?
– neuron
Aug 16 '15 at 8:09
I do not know where the logs are located on my machine. I tried:grep CRON /var/log/messages- no success. Where is cron logging?
– Oliver Williams
Aug 16 '15 at 21:41
Another alternative is kill -15 2557 and only resort to kill -9 2557 if that failed.
– rreck
Aug 17 '15 at 20:52
Is there a real reason for actually wanting to stop the cron daemon, ever?
– Kusalananda
Jul 11 at 12:50
add a comment |
After you useservice crond stopwhat does the logs say?
– neuron
Aug 16 '15 at 8:09
I do not know where the logs are located on my machine. I tried:grep CRON /var/log/messages- no success. Where is cron logging?
– Oliver Williams
Aug 16 '15 at 21:41
Another alternative is kill -15 2557 and only resort to kill -9 2557 if that failed.
– rreck
Aug 17 '15 at 20:52
Is there a real reason for actually wanting to stop the cron daemon, ever?
– Kusalananda
Jul 11 at 12:50
After you use
service crond stop what does the logs say?– neuron
Aug 16 '15 at 8:09
After you use
service crond stop what does the logs say?– neuron
Aug 16 '15 at 8:09
I do not know where the logs are located on my machine. I tried:
grep CRON /var/log/messages - no success. Where is cron logging?– Oliver Williams
Aug 16 '15 at 21:41
I do not know where the logs are located on my machine. I tried:
grep CRON /var/log/messages - no success. Where is cron logging?– Oliver Williams
Aug 16 '15 at 21:41
Another alternative is kill -15 2557 and only resort to kill -9 2557 if that failed.
– rreck
Aug 17 '15 at 20:52
Another alternative is kill -15 2557 and only resort to kill -9 2557 if that failed.
– rreck
Aug 17 '15 at 20:52
Is there a real reason for actually wanting to stop the cron daemon, ever?
– Kusalananda
Jul 11 at 12:50
Is there a real reason for actually wanting to stop the cron daemon, ever?
– Kusalananda
Jul 11 at 12:50
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
kill -1 is a command that will send a SIGHUP signal, meaning all processes with a pid greater than 1 are signaled.
What you need is kill -9 2557. The -9 argument sends a SIGKILL signal to the desired process which ensures that it is killed.
Other alternatives if your system has the programs installed:
pkill crond
killall crond
answered Aug 17 '15 at 17:24
Peschke
2,165923
kill -1sendsSIGHUP- it doesn't do any lookup of users.
– DarkHeart
Aug 18 '15 at 3:02
@DarkHeart, you are right. I was reading something on the kill AIX man page and I read the wrong entry. I am editing it now.
– Peschke
Aug 18 '15 at 4:15
You are right about-9but still not quite there on the first statement. kill will only send signals to listed processes.
– DarkHeart
Aug 19 '15 at 0:05
kill sends TERM by default, not HUP.
– Kusalananda
May 7 at 8:03
add a comment |
up vote
0
down vote
According to the first line of the output you get ("redirecting to..."), you're using systemd, so many of the old SysV commands will not work.
Use systemctl to manage systemd services.
The command you need to issue to stop cron, would be: systemctl stop crond.service.
If you want to dsable it, do: systemctl disable crond.service.
For futher information on how to manage systemd units, see man systemctl.
answered Apr 2 at 15:15
Mioriin
1,694512
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
kill -1 is a command that will send a SIGHUP signal, meaning all processes with a pid greater than 1 are signaled.
What you need is kill -9 2557. The -9 argument sends a SIGKILL signal to the desired process which ensures that it is killed.
Other alternatives if your system has the programs installed:
pkill crond
killall crond
answered Aug 17 '15 at 17:24
Peschke
2,165923
kill -1sendsSIGHUP- it doesn't do any lookup of users.
– DarkHeart
Aug 18 '15 at 3:02
@DarkHeart, you are right. I was reading something on the kill AIX man page and I read the wrong entry. I am editing it now.
– Peschke
Aug 18 '15 at 4:15
You are right about-9but still not quite there on the first statement. kill will only send signals to listed processes.
– DarkHeart
Aug 19 '15 at 0:05
kill sends TERM by default, not HUP.
– Kusalananda
May 7 at 8:03
add a comment |
up vote
0
down vote
kill -1 is a command that will send a SIGHUP signal, meaning all processes with a pid greater than 1 are signaled.
What you need is kill -9 2557. The -9 argument sends a SIGKILL signal to the desired process which ensures that it is killed.
Other alternatives if your system has the programs installed:
pkill crond
killall crond
answered Aug 17 '15 at 17:24
Peschke
2,165923
kill -1sendsSIGHUP- it doesn't do any lookup of users.
– DarkHeart
Aug 18 '15 at 3:02
@DarkHeart, you are right. I was reading something on the kill AIX man page and I read the wrong entry. I am editing it now.
– Peschke
Aug 18 '15 at 4:15
You are right about-9but still not quite there on the first statement. kill will only send signals to listed processes.
– DarkHeart
Aug 19 '15 at 0:05
kill sends TERM by default, not HUP.
– Kusalananda
May 7 at 8:03
add a comment |
up vote
0
down vote
up vote
0
down vote
kill -1 is a command that will send a SIGHUP signal, meaning all processes with a pid greater than 1 are signaled.
What you need is kill -9 2557. The -9 argument sends a SIGKILL signal to the desired process which ensures that it is killed.
Other alternatives if your system has the programs installed:
pkill crond
killall crond
answered Aug 17 '15 at 17:24
Peschke
2,165923
kill -1 is a command that will send a SIGHUP signal, meaning all processes with a pid greater than 1 are signaled.
What you need is kill -9 2557. The -9 argument sends a SIGKILL signal to the desired process which ensures that it is killed.
Other alternatives if your system has the programs installed:
pkill crond
killall crond
answered Aug 17 '15 at 17:24
Peschke
2,165923
edited Aug 18 '15 at 4:16
answered Aug 17 '15 at 17:24
Peschke
2,165923
answered Aug 17 '15 at 17:24
Peschke
2,165923
answered Aug 17 '15 at 17:24
Peschke
2,165923
2,165923
kill -1sendsSIGHUP- it doesn't do any lookup of users.
– DarkHeart
Aug 18 '15 at 3:02
@DarkHeart, you are right. I was reading something on the kill AIX man page and I read the wrong entry. I am editing it now.
– Peschke
Aug 18 '15 at 4:15
You are right about-9but still not quite there on the first statement. kill will only send signals to listed processes.
– DarkHeart
Aug 19 '15 at 0:05
kill sends TERM by default, not HUP.
– Kusalananda
May 7 at 8:03
add a comment |
kill -1sendsSIGHUP- it doesn't do any lookup of users.
– DarkHeart
Aug 18 '15 at 3:02
@DarkHeart, you are right. I was reading something on the kill AIX man page and I read the wrong entry. I am editing it now.
– Peschke
Aug 18 '15 at 4:15
You are right about-9but still not quite there on the first statement. kill will only send signals to listed processes.
– DarkHeart
Aug 19 '15 at 0:05
kill sends TERM by default, not HUP.
– Kusalananda
May 7 at 8:03
kill -1 sends SIGHUP - it doesn't do any lookup of users.– DarkHeart
Aug 18 '15 at 3:02
kill -1 sends SIGHUP - it doesn't do any lookup of users.– DarkHeart
Aug 18 '15 at 3:02
@DarkHeart, you are right. I was reading something on the kill AIX man page and I read the wrong entry. I am editing it now.
– Peschke
Aug 18 '15 at 4:15
@DarkHeart, you are right. I was reading something on the kill AIX man page and I read the wrong entry. I am editing it now.
– Peschke
Aug 18 '15 at 4:15
You are right about
-9 but still not quite there on the first statement. kill will only send signals to listed processes.– DarkHeart
Aug 19 '15 at 0:05
You are right about
-9 but still not quite there on the first statement. kill will only send signals to listed processes.– DarkHeart
Aug 19 '15 at 0:05
kill sends TERM by default, not HUP.
– Kusalananda
May 7 at 8:03
kill sends TERM by default, not HUP.
– Kusalananda
May 7 at 8:03
add a comment |
up vote
0
down vote
According to the first line of the output you get ("redirecting to..."), you're using systemd, so many of the old SysV commands will not work.
Use systemctl to manage systemd services.
The command you need to issue to stop cron, would be: systemctl stop crond.service.
If you want to dsable it, do: systemctl disable crond.service.
For futher information on how to manage systemd units, see man systemctl.
answered Apr 2 at 15:15
Mioriin
1,694512
add a comment |
up vote
0
down vote
According to the first line of the output you get ("redirecting to..."), you're using systemd, so many of the old SysV commands will not work.
Use systemctl to manage systemd services.
The command you need to issue to stop cron, would be: systemctl stop crond.service.
If you want to dsable it, do: systemctl disable crond.service.
For futher information on how to manage systemd units, see man systemctl.
answered Apr 2 at 15:15
Mioriin
1,694512
add a comment |
up vote
0
down vote
up vote
0
down vote
According to the first line of the output you get ("redirecting to..."), you're using systemd, so many of the old SysV commands will not work.
Use systemctl to manage systemd services.
The command you need to issue to stop cron, would be: systemctl stop crond.service.
If you want to dsable it, do: systemctl disable crond.service.
For futher information on how to manage systemd units, see man systemctl.
answered Apr 2 at 15:15
Mioriin
1,694512
According to the first line of the output you get ("redirecting to..."), you're using systemd, so many of the old SysV commands will not work.
Use systemctl to manage systemd services.
The command you need to issue to stop cron, would be: systemctl stop crond.service.
If you want to dsable it, do: systemctl disable crond.service.
For futher information on how to manage systemd units, see man systemctl.
answered Apr 2 at 15:15
Mioriin
1,694512
answered Apr 2 at 15:15
Mioriin
1,694512
answered Apr 2 at 15:15
Mioriin
1,694512
answered Apr 2 at 15:15
Mioriin
1,694512
1,694512
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f223458%2fi-cannot-kill-crond-trying-to-stop-cron-service%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
After you use
service crond stopwhat does the logs say?– neuron
Aug 16 '15 at 8:09
I do not know where the logs are located on my machine. I tried:
grep CRON /var/log/messages- no success. Where is cron logging?– Oliver Williams
Aug 16 '15 at 21:41
Another alternative is kill -15 2557 and only resort to kill -9 2557 if that failed.
– rreck
Aug 17 '15 at 20:52
Is there a real reason for actually wanting to stop the cron daemon, ever?
– Kusalananda
Jul 11 at 12:50