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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Analytics Workspace removal in Splunk 10.6

In Splunk Cloud Platform and Splunk Enterprise 10.6, Analytics Workspace is removed from product and no longer ...

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...