[SOLVED] Ceph, systemd and Killmode=none

Hi,

I am receiving the following message when restarting a node (so restarting ceph and osds on the node):

Code:
systemd[1]: /lib/systemd/system/ceph-volume@.service:8: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.

I'm on the latest non-enterprise update.

Is there a way to solve/silence it?

Thank you.
 
it's just a deprecation warning, it will go away once the Ceph units are updated to no longer trigger it, but it's of no concern at the moment.
 
  • Like
Reactions: Urbaman
I'm still seeing this in the syslogs (Nov 2023) so for what it's worth you can silence the error with
Code:
sudo nano /lib/systemd/system/ceph-volume@.service
Locate the line KillMode=none and change it to mixedor control-group. Make this change on all your CEPH nodes. When you're done, don't forget to run the command sudo systemctl daemon-reload.
 
Last edited:
  • Like
Reactions: Abend1
Just checking what the recommendation is in Jan '24 .. do nothing or update ceph-volume@.service? If its update I am assuming its
Code:
killMode=mixed
 
Few months late, but yes, the recommended change is to set KillMode=mixed. Here's an explanation of each mode, from www.freedesktop.org systemd.kill:
  • KillMode=none: No processes in the control group will be killed. This setting is rarely used because it can lead to orphaned processes that remain running after the service is stopped.
  • KillMode=control-group: All processes in the control group of the service will be terminated when the service is stopped. This is aggressive and can sometimes cause issues if there are processes that should not be killed immediately or if there are dependencies that need a more graceful shutdown.
  • KillMode=process: Only the main process of the service will be killed. This is less aggressive but can also leave orphaned child processes.
  • KillMode=mixed: The main process will receive a SIGTERM signal to allow it to terminate gracefully, while all remaining processes in the control group will be terminated with SIGKILL if they do not exit within a timeout. This mode provides a balanced approach, giving the main process a chance to clean up properly while ensuring that any lingering processes are forcibly terminated after the grace period.
 
systemd[1]: /lib/systemd/system/ceph-volume@.service:9: Unknown key 'killMode' in section [Service], ignoring.

Debian12 64Bits

KillMode=process
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!