KillMode=none Issue

Since the Commvault Services are controlled using commands, I’m not entirely sure if a KillMode is required to be set.

Commands: https://documentation.commvault.com/11.24/expert/8546_commands_to_control_services_on_unix_clients.html

Let’s see what other community members have to add here.

Best Regards,

Michael

Hi @MichaelCapon ,

Thank you.

Yeah, let’s let other community members to reply.

Rgds,

Kamil

@Kamil W , I’m marking this as solved since we didn’t get any more replies, but if you need further exploration here, I can undo it and we can investigate.

Hi @Mike Struening ,

Sorry for my late reply. I was waiting for any response from the Customer.

Here’s the message I got from the Customer yesterday:

KillMode was set automatically by commvault installer, we didn’t change it. I sent you alert from log, where system says that this setting is not recommended and will deprecate in future. I just want to understand how to deal with it, maybe
you could recommend which mode to choose?

The Customer is getting the following alert:

-------------------- message from log /var/log/warn ---------

systemd[1]1: /etc/systemd/system/commvault.Instance001.service:14: 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.

------------------------------------------

Rgds,

Kamil

No apology need @Kamil W !

I unmarked the prior Best Answer.

For this one, I would get a support case created since development is likely going to need to provide input.

Hi @Mike Struening ,

Thanks for your reply. 

Yes, I’m gonna open a support ticket ASAP. Once I get any information, I’ll let you know, how it goes.

Rgds,

Kamil

Here you go @Mike Struening ,

https://ma.commvault.com/Case/Details/220121-147

Let’s see what support says.

Rgds,

Kamil