I got it to work! With your great help it wasn't that bad, or maybe I'm a better sysadmin than I'm giving myself credit for. ;)
There were two steps, really. After creating the fstab line, I typed sudo systemctl edit memcached.service. I entered this and saved: [Service] KillSignal=SIGUSR1 Then it's a matter of: 0. sudo systemctl daemon-reload 1. stopping and disabling the systemd services for the webserver 2. Stopping and disabling memcached 3. copying the memory_file and memory_file.meta to a safe location on the hard disk 4. rebooting 5. copying the files back to /tmpfs_mount_memcached 6. Starting and enabling memcached with systemctl 7. Starting and enabling the webserver All of these steps I was able to easily automate with Ansible. Really happy about this! Thanks again! torsdag 11. juni 2020 08.53.19 UTC+2 skrev Dormando følgende: > > Absolutely. That's exactly the workflow it's designed for, we just haven't > updated any of the systemd scripts to be more friendly for it. > > Also a caveat; there _was_ a bug fixed relatively recently with the > restart code. I don't know if ubuntu backports these. If you use large > objects (> 512k) there's a chance restart won't work sometimes. Worst case > you can probably file a bug with them to backport the patch or upgrade > memcached. > > Good luck! > > On Wed, 10 Jun 2020, Even Onsager wrote: > > > That's extremely helpful, thank you so much for this! I will look into > it and test on my staging server. I don't think systemd has ever killed or > restarted the process apart from once before I upgraded the RAM, so I'm not > too worried about the daily usage. But even systemd supports custom kill > signals, so it should be possible to set this up? > > > > Anyway, it's the reboots I'm trying to get to work. I never upgrade apt > packages or reboot directly, only with Ansible after kernel upgrades or > similar, so I should be able to disable the systemd services (should > probably temporarily disable the puma webserver service too) and automate a > copy to disk task before the reboot takes place. A good thing with Ansible > is that it can automate reboots and continue with more tasks after reboot > is complete, so it should be ideal for this scenario. I will post back if I > can get it to work, should be interesting for more than me. :) > > > > -- > > > > --- > > You received this message because you are subscribed to the Google > Groups "memcached" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to memc...@googlegroups.com <javascript:>. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/memcached/5ec346ab-6977-4996-b573-9d07dd0d4084o%40googlegroups.com. > > > > > -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/memcached/7a2b1b42-cb51-48f6-b00d-f0a4bbb1be77o%40googlegroups.com.
