memcached systemd service stop timeout

The name of the pictureThe name of the pictureThe name of the pictureClash 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




share|improve this question





















  • 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











  • 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














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




share|improve this question





















  • 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











  • 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












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




share|improve this question













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





share|improve this question












share|improve this question




share|improve this question








edited Jun 13 at 21:06









jasonwryan

46.4k14125174




46.4k14125174









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 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











  • 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
















  • 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











  • 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















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















active

oldest

votes











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',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















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






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














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
































































-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
Read more