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!

Splunk Decoded: Service Maps vs Service Analyzer Tree View vs Flow Maps

It’s Monday morning, and your phone is buzzing with alert escalations – your customer-facing portal is running ...

What’s New in Splunk Observability – September 2025

What's NewWe are excited to announce the latest enhancements to Splunk Observability, designed to help ITOps ...

Fun with Regular Expression - multiples of nine

Fun with Regular Expression - multiples of nineThis challenge was first posted on Slack #regex channel ...