Installation

UF 9.x migration creates by itsself a Systemd Unit File!

verbal_666
Builder

As in object.
Migration UF from 8.x to 9.x creates by itsself a Systemd Unit File!
I do not want it, in first "restart" action, and not having to do manually a "disable boot-start" after restart.

First restart after deploying the new version (9.0.6),

[DFS] Performing migration.
[DFS] Finished migration.
[Peer-apps] Performing migration.
[Peer-apps] Finished migration.
Creating unit file...
Important: splunk will start under systemd as user: root
The unit file has been created.

 

Loaded: loaded (/usr/lib/systemd/system/SplunkForwarder.service; enabled; vendor preset: disabled)

 

Is there a way in "restart" action to prevent the creation of Systemd Unit File?
I'm under Centos-Stream.
Thanks.

Labels (4)
0 Karma
Get Updates on the Splunk Community!

3 Ways to Make OpenTelemetry Even Better

My role as an Observability Specialist at Splunk provides me with the opportunity to work with customers of ...

What's New in Splunk Cloud Platform 9.2.2406?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.2.2406 with many ...

Enterprise Security Content Update (ESCU) | New Releases

In August, the Splunk Threat Research Team had 3 releases of new security content via the Enterprise Security ...