memcached systemd service stop timeout
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I'm using Arch Linux and I noticed that since I installed memcached the system takes much longer to shut down, I checked and verified that this service was indeed the one which was causing it, because it keeps trying to stop it until it timeouts after one minute and a half.If I try to stop the service while the system is up the same happens, and this appears in the journal:
jun 11 13:54:27 Gawain systemd[1]: Stopping Memcached Daemon...
jun 11 13:55:57 Gawain systemd[1]: memcached.service: State 'stop-sigterm' timed out. Killing.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Killing process 5372 (memcached) with signal SIGKILL.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Killing process 5379 (n/a) with signal SIGKILL.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Killing process 5380 (memcached) with signal SIGKILL.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Main process exited, code=killed, status=31/SYS
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Failed with result 'timeout'.
jun 11 13:55:57 Gawain systemd[1]: Stopped Memcached Daemon.
systemd memcached
edited Jun 13 at 21:06
jasonwryan
46.4k14125174
asked Jun 13 at 18:44
user2859982
90110
add a comment |Â
up vote
0
down vote
favorite
I'm using Arch Linux and I noticed that since I installed memcached the system takes much longer to shut down, I checked and verified that this service was indeed the one which was causing it, because it keeps trying to stop it until it timeouts after one minute and a half.If I try to stop the service while the system is up the same happens, and this appears in the journal:
jun 11 13:54:27 Gawain systemd[1]: Stopping Memcached Daemon...
jun 11 13:55:57 Gawain systemd[1]: memcached.service: State 'stop-sigterm' timed out. Killing.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Killing process 5372 (memcached) with signal SIGKILL.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Killing process 5379 (n/a) with signal SIGKILL.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Killing process 5380 (memcached) with signal SIGKILL.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Main process exited, code=killed, status=31/SYS
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Failed with result 'timeout'.
jun 11 13:55:57 Gawain systemd[1]: Stopped Memcached Daemon.
systemd memcached
edited Jun 13 at 21:06
jasonwryan
46.4k14125174
asked Jun 13 at 18:44
user2859982
90110
There may be something wrong with your systemd unit file for memcached, the posted logs say the regular stop timed out so systemd had to go with the fallbackSIGKILL. Could you post any associated systemd unit files? I would think something is wrong with theExecStoporKillSignalsetting, in that it does not actually stop your memcached service.
– GracefulRestart
Jun 13 at 21:58
This is the unit file: pastebin.com/LJZQRpsf
– user2859982
Jun 13 at 22:02
With no specifiedExecStoporKillSignal, the default action of systemd is to send aSIGTERMto the process on stop. I was unable to test the-o modernoption, but when runningmemcachedwith the rest of yourExecStartcommand,memcachedshutdown very quickly onSIGTERM.
– GracefulRestart
Jun 13 at 22:43
In my case the memcached process stays in <defunct> state after SIGTERM, and the same happens with systemctl until it is removed from the process table I guess. It happens both with and without-o modern
– user2859982
Jun 13 at 23:24
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm using Arch Linux and I noticed that since I installed memcached the system takes much longer to shut down, I checked and verified that this service was indeed the one which was causing it, because it keeps trying to stop it until it timeouts after one minute and a half.If I try to stop the service while the system is up the same happens, and this appears in the journal:
jun 11 13:54:27 Gawain systemd[1]: Stopping Memcached Daemon...
jun 11 13:55:57 Gawain systemd[1]: memcached.service: State 'stop-sigterm' timed out. Killing.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Killing process 5372 (memcached) with signal SIGKILL.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Killing process 5379 (n/a) with signal SIGKILL.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Killing process 5380 (memcached) with signal SIGKILL.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Main process exited, code=killed, status=31/SYS
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Failed with result 'timeout'.
jun 11 13:55:57 Gawain systemd[1]: Stopped Memcached Daemon.
systemd memcached
edited Jun 13 at 21:06
jasonwryan
46.4k14125174
asked Jun 13 at 18:44
user2859982
90110
I'm using Arch Linux and I noticed that since I installed memcached the system takes much longer to shut down, I checked and verified that this service was indeed the one which was causing it, because it keeps trying to stop it until it timeouts after one minute and a half.If I try to stop the service while the system is up the same happens, and this appears in the journal:
jun 11 13:54:27 Gawain systemd[1]: Stopping Memcached Daemon...
jun 11 13:55:57 Gawain systemd[1]: memcached.service: State 'stop-sigterm' timed out. Killing.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Killing process 5372 (memcached) with signal SIGKILL.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Killing process 5379 (n/a) with signal SIGKILL.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Killing process 5380 (memcached) with signal SIGKILL.
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Main process exited, code=killed, status=31/SYS
jun 11 13:55:57 Gawain systemd[1]: memcached.service: Failed with result 'timeout'.
jun 11 13:55:57 Gawain systemd[1]: Stopped Memcached Daemon.
systemd memcached
edited Jun 13 at 21:06
jasonwryan
46.4k14125174
asked Jun 13 at 18:44
user2859982
90110
edited Jun 13 at 21:06
jasonwryan
46.4k14125174
edited Jun 13 at 21:06
jasonwryan
46.4k14125174
edited Jun 13 at 21:06
jasonwryan
46.4k14125174
46.4k14125174
asked Jun 13 at 18:44
user2859982
90110
asked Jun 13 at 18:44
user2859982
90110
asked Jun 13 at 18:44
user2859982
90110
90110
There may be something wrong with your systemd unit file for memcached, the posted logs say the regular stop timed out so systemd had to go with the fallbackSIGKILL. Could you post any associated systemd unit files? I would think something is wrong with theExecStoporKillSignalsetting, in that it does not actually stop your memcached service.
– GracefulRestart
Jun 13 at 21:58
This is the unit file: pastebin.com/LJZQRpsf
– user2859982
Jun 13 at 22:02
With no specifiedExecStoporKillSignal, the default action of systemd is to send aSIGTERMto the process on stop. I was unable to test the-o modernoption, but when runningmemcachedwith the rest of yourExecStartcommand,memcachedshutdown very quickly onSIGTERM.
– GracefulRestart
Jun 13 at 22:43
In my case the memcached process stays in <defunct> state after SIGTERM, and the same happens with systemctl until it is removed from the process table I guess. It happens both with and without-o modern
– user2859982
Jun 13 at 23:24
add a comment |Â
There may be something wrong with your systemd unit file for memcached, the posted logs say the regular stop timed out so systemd had to go with the fallbackSIGKILL. Could you post any associated systemd unit files? I would think something is wrong with theExecStoporKillSignalsetting, in that it does not actually stop your memcached service.
– GracefulRestart
Jun 13 at 21:58
This is the unit file: pastebin.com/LJZQRpsf
– user2859982
Jun 13 at 22:02
With no specifiedExecStoporKillSignal, the default action of systemd is to send aSIGTERMto the process on stop. I was unable to test the-o modernoption, but when runningmemcachedwith the rest of yourExecStartcommand,memcachedshutdown very quickly onSIGTERM.
– GracefulRestart
Jun 13 at 22:43
In my case the memcached process stays in <defunct> state after SIGTERM, and the same happens with systemctl until it is removed from the process table I guess. It happens both with and without-o modern
– user2859982
Jun 13 at 23:24
There may be something wrong with your systemd unit file for memcached, the posted logs say the regular stop timed out so systemd had to go with the fallback
SIGKILL. Could you post any associated systemd unit files? I would think something is wrong with the ExecStop or KillSignal setting, in that it does not actually stop your memcached service.– GracefulRestart
Jun 13 at 21:58
There may be something wrong with your systemd unit file for memcached, the posted logs say the regular stop timed out so systemd had to go with the fallback
SIGKILL. Could you post any associated systemd unit files? I would think something is wrong with the ExecStop or KillSignal setting, in that it does not actually stop your memcached service.– GracefulRestart
Jun 13 at 21:58
This is the unit file: pastebin.com/LJZQRpsf
– user2859982
Jun 13 at 22:02
This is the unit file: pastebin.com/LJZQRpsf
– user2859982
Jun 13 at 22:02
With no specified
ExecStop or KillSignal, the default action of systemd is to send a SIGTERM to the process on stop. I was unable to test the -o modern option, but when running memcached with the rest of your ExecStart command, memcached shutdown very quickly on SIGTERM.– GracefulRestart
Jun 13 at 22:43
With no specified
ExecStop or KillSignal, the default action of systemd is to send a SIGTERM to the process on stop. I was unable to test the -o modern option, but when running memcached with the rest of your ExecStart command, memcached shutdown very quickly on SIGTERM.– GracefulRestart
Jun 13 at 22:43
In my case the memcached process stays in <defunct> state after SIGTERM, and the same happens with systemctl until it is removed from the process table I guess. It happens both with and without
-o modern– user2859982
Jun 13 at 23:24
In my case the memcached process stays in <defunct> state after SIGTERM, and the same happens with systemctl until it is removed from the process table I guess. It happens both with and without
-o modern– user2859982
Jun 13 at 23:24
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f449632%2fmemcached-systemd-service-stop-timeout%23new-answer', 'question_page');
);
Post as a guest
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
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
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
There may be something wrong with your systemd unit file for memcached, the posted logs say the regular stop timed out so systemd had to go with the fallback
SIGKILL. Could you post any associated systemd unit files? I would think something is wrong with theExecStoporKillSignalsetting, in that it does not actually stop your memcached service.– GracefulRestart
Jun 13 at 21:58
This is the unit file: pastebin.com/LJZQRpsf
– user2859982
Jun 13 at 22:02
With no specified
ExecStoporKillSignal, the default action of systemd is to send aSIGTERMto the process on stop. I was unable to test the-o modernoption, but when runningmemcachedwith the rest of yourExecStartcommand,memcachedshutdown very quickly onSIGTERM.– GracefulRestart
Jun 13 at 22:43
In my case the memcached process stays in <defunct> state after SIGTERM, and the same happens with systemctl until it is removed from the process table I guess. It happens both with and without
-o modern– user2859982
Jun 13 at 23:24